Questions, answered directly

Most checks return in one to two seconds. The variation comes from the upstream source rather than from our infrastructure, so we publish per-endpoint latency rather than a single marketing number, and we show live figures on the status page.

No. Accounts start pay-as-you-go with no minimum commitment and no notice period. Volume pricing is available when it saves you money, and it is something you opt into rather than something you sign up for by default.

Six, across two families. Vehicle: RC verification, chassis-to-RC lookup, and driving licence verification. Identity: Aadhaar verification, PAN verification, and Aadhaar–PAN link status. One account and one API key cover all of them.

The input. RC verification starts from a registration number, which is what you normally have. Chassis-to-RC starts from the number stamped into the vehicle frame, which is what you fall back to when the plate is missing, damaged, or doesn't match what you were told.

Yes. The batch endpoint accepts bulk submissions and returns a structured report, and the synchronous API is rate-limited per account rather than capped. If you have a seasonal spike coming, tell us and we will raise limits ahead of it rather than after you hit them.

Consent reference and purpose are required request parameters on identity endpoints — a call without them is rejected rather than queued. Full identifiers are never echoed back in responses or written to logs. Retention is configurable per account, and the default is the shortest period that still supports your audit obligations.

A shared channel with the engineers who maintain the endpoints you are calling. During integration you will be talking to someone who can read your request payload and tell you what is wrong with it, which is usually faster than a ticket queue.

Yes. The sandbox returns realistic payloads — including the failure cases, which are the ones worth building against. Moving to production is a key swap; no re-integration, no second contract.