Karnataka land-record provider scorecard

The most practical ready-now design is a two-lane workflow, not an immediate Surepass replacement:

1. API lane: continue Surepass for the states and lookup types it supports today.
2. Official-portal lane: use the existing Bhoomi handoff for Karnataka, where an analyst solves the captcha and the result is captured against the report.
3. Pilot lane: test one enterprise property-data vendor against the same Karnataka cases before routing live work to it.
4. Document lane: use OCR/document extraction as an accelerator for uploaded RTC, EC, sale deeds, search receipts and certified copies. OCR output must never be presented as an official live-record lookup.

The named enterprise vendors below are qualification targets, not confirmed coverage claims. Each vendor must demonstrate the exact Karnataka workflow and provide written coverage, SLA, pricing, retention and evidence terms.

Run the same cases against each provider so the result is comparable. Do not send live personal data until the vendor’s data-processing and retention terms are approved.

Score each item 0–2: 0 = absent, 1 = partial/manual, 2 = demonstrated and documented.

Suggested gate: at least 80/100, with no score below 1 for Karnataka coverage, evidence or audit trail.

1. Which Karnataka services are live today: Bhoomi RTC/Pahani, mutation, Kaveri 2.0 EC, SRO search, certified copies and registration verification?
2. Which districts, taluks, hoblis and villages are covered? Provide the coverage date and known exclusions.
3. Is the result sourced from an official government portal, an authorized data feed, a partner, or a document submitted by the customer?
4. Does each result include an official document, transaction/reference number, source URL, retrieval timestamp and raw response?
5. How are captcha, OTP, portal downtime, pending mutation and no-record cases handled?
6. Can the same request be retried safely? What is the idempotency key and refund policy?
7. Are Kannada names and legacy/current district spellings supported?
8. Is there a sandbox with representative Karnataka data, or only a sales demo?
9. What are API limits, SLA, support hours, incident communication and escalation contacts?
10. What data is stored, for how long, in which region, and how can NE Advisors delete it?
11. Can the vendor provide an audit export suitable for a bank-facing legal report?
12. Can the vendor contractually commit to the exact record types and states being purchased?

After a candidate passes the pilot, place it behind a small provider adapter. The live report, cache, credit and payment behavior should remain provider-neutral.

Land-record request
  -> state + record type router
      -> Surepass API
      -> qualified Karnataka provider API
      -> official portal / manual handoff
  -> normalized result
      -> evidence attachment + source metadata
      -> 24-hour provider-aware cache
      -> credit / payment policy
      -> report PART-IX / PART-X section

• Masked input values
• Provider and endpoint/workflow used
• Request and completion timestamps
• Raw response or portal capture
• Official document/reference number, if present
• Normalized fields shown to the analyst
• Pass/fail reason and reviewer initials
• Price consumed and refund outcome
• Whether the result was appended to a test report