KYC and Identity

Passport, voter ID, mobile and bank checks on one contract.

Verify a passport by file number and date of birth, and a voter ID by EPIC number. Prove a person holds a mobile number with an OTP against the telco record, or check it silently and against DoT's revoked-number list. Penny-drop a bank account, or run a reverse penny drop where the holder reports a random amount back. ICSI membership and electricity-bill proof of address sit on the same contract.

APIs
12 you can call, 6 more on request
Consent
Bound to every read
Audit
Every call in a hash-chained log

APIs in KYC and Identity

Every API shares the same key, error format and audit log. Each one is switched on for your account separately.

Available on request

We set these checks up for your account. Subscribe to the one you need and we will have it ready for you.

What teams use it for

Use cases for each KYC and Identity check. See how they combine with other products on the use cases page.

  • Confirms an account exists and returns the name the bank holds for it.

    • Check a borrower’s account before disbursing a loan or a refund.
    • Verify payout accounts for sellers, drivers and gig workers before the first transfer.
    • Match the account holder’s name with the name on the customer’s ID.
  • Credits a small amount that the account holder reports back, proving they control the account.

    • Prove the customer controls the account, not just that it exists.
    • Set up a payout or auto-debit account with stronger proof than a name match.
    • Confirm a changed bank account before releasing money to it.
  • Bank and branch details for an IFSC.

    • Validate IFSC codes as customers type their bank details.
    • Fill in the bank and branch name automatically.
    • Catch a mistyped code before a payment or account check fails.
  • Checks a passport file number and date of birth against the passport record.

    • Verify customers who give a passport as their ID, including NRIs.
    • Confirm identity during employee background checks.
    • Travel, visa and foreign exchange services that must confirm the traveller.
  • Checks an EPIC number against the electoral record.

    • Accept voter ID as an officially valid document in customer KYC.
    • Verify customers who have no passport, common in rural and semi-urban areas.
    • Background checks for field staff and delivery partners.
  • Proves the person holds the number and returns the subscriber details on record.

    • Prove at sign-up that the customer holds the number they gave.
    • Compare the subscriber details held by the telecom operator with the customer’s ID.
    • Re-confirm the number before changing payout or contact details.
  • Checks a number against the telecom operator’s record without sending an OTP.

    • Verify a number where an OTP would interrupt the customer, such as at checkout.
    • Add a quiet second check on the number behind a high-value action.
  • Whether a number is on the Department of Telecommunications revocation list, with its fraud risk indicator.

    • Stop sign-ups and payouts on numbers that have been revoked.
    • Flag numbers marked for financial fraud risk before lending or onboarding.
    • Re-check numbers on file before an OTP is sent for a sensitive action.
  • Checks ACS or FCS membership against the ICSI register.

    • Verify the company secretary who certifies documents for a business you onboard.
    • Hiring checks for company secretary roles.
    • Professional marketplaces and directories that list company secretaries.
  • Consumer name, address and latest bill from the electricity board.

    • Confirm a customer’s current address from the board’s record.
    • Verify a shop or business premises during merchant onboarding.
    • Address checks for rentals and home loans.
  • Whether a person already has a record in the central KYC registry.

    • Find out if a customer was already verified by another regulated entity.
    • Shorten onboarding for customers who already have a central KYC record.
  • Whether a mobile number is linked to a UPI account.

    • Check a number before setting up UPI payouts or collections.
    • Use as a signal that the number belongs to an active banking customer.
  • Whether a mobile number is registered on WhatsApp.

    • Check a customer can be reached on WhatsApp before sending service messages.
    • Use as one signal that a mobile number is in active use.
  • Gas bill lookup

    On request

    A gas connection’s details as proof of address.

    • Accept a gas connection as proof of address.
    • Verify the address of customers who have no electricity bill in their name.
  • Whether an email address exists and can receive mail, with disposable addresses flagged.

    • Block disposable and non-existent email addresses at sign-up.
    • Keep contact details clean for statements and notices.
  • Roughly how long a mobile number has been in use.

    • Treat brand-new numbers with more caution in fraud and credit checks.
    • Add the age of the number as a signal in risk scores.

How you get KYC and Identity

From a new account to a live call in four steps.

  1. Create your account

    Sign up with your work email and create an app and its key. No API is active on a new account.

  2. Pay and subscribe

    Add money to your wallet, then subscribe to this API in Dashboard → API access. We switch it on for your account after your payment.

  3. Make your first call

    Once the API is activated, send the sample request to /v1/verify/passport with your key and read back the JSON.

  4. Go live

    Use a live key in production. Every call is checked against the APIs activated for you, drawn from your prepaid wallet, and recorded in a hash-chained audit trail.

Call verify passport

The main call for this product. Use your own key once this API is switched on for your account.

POST /v1/verify/passport
curl -X POST https://grappi.ai/v1/verify/passport \
-H "Authorization: Bearer $GRAPPI_API_KEY" \
-H "content-type: application/json" \
-d '{"file_number":"BO1065000012345","dob":"1990-08-17"}'

Developer ready

Docs, MCP, and a prompt that does the work

Every product ships with an integration guide, an MCP server for AI agents, and a ready-to-paste prompt, so your first KYC and Identity call takes minutes, not days.

Integration guide

The quickstart covers keys, auth, idempotency, the error envelope, and paise money units. The catalog documents every KYC and Identity endpoint with a live sample you can run from the playground.

MCP server for AI agents

grappi-mcp exposes the API as agent tools over the same gateway, so every tool call keeps auth, consent, metering, and audit. Drop this into your MCP client config.

mcp.json
{
  "mcpServers": {
    "grappi": {
      "command": "npx",
      "args": ["grappi-mcp"],
      "env": {
        "GRAPPI_API_BASE": "https://grappi.ai",
        "GRAPPI_API_KEY": "your-api-key"
      }
    }
  }
}

Prompt-ready integration

Paste this into your coding assistant or agent. It carries the real contract rules, so the generated client matches the gateway on the first try.

integrate-kyc-identity.prompt
Integrate the Grappi KYC and Identity API into my app.

Endpoints:
- POST /v1/verify/bank-account (Penny-drop bank account)
- GET /v1/lookup/ifsc (IFSC lookup)
- POST /v1/verify/passport (Verify passport)
- POST /v1/verify/voter-id (Verify voter ID)
- POST /v1/verify/mobile/otp (Mobile ownership: send OTP)
- POST /v1/verify/mobile/otp/verify (Mobile ownership: verify OTP)
- POST /v1/verify/mobile/silent (Silent mobile check)
- POST /v1/verify/mobile/mnrl (Revoked-number check (MNRL))
- POST /v1/verify/icsi-membership (ICSI membership)
- POST /v1/verify/electricity-bill (Electricity bill (proof of address))
- POST /v1/verify/bank-account/dynamic (Reverse penny drop: send amount)
- POST /v1/verify/bank-account/dynamic/confirm (Reverse penny drop: confirm amount)

Contract rules: send the key as a Bearer token in the Authorization header, treat all money as integer paise (100 paise is one rupee), send an Idempotency-Key on every POST, and branch on the error envelope error.code (handle 402 insufficient_balance, 403 api_not_activated, 403 consent_required, 422 validation_failed, 429 rate_limited, 503 api_unavailable).

Write a small typed client for these endpoints plus one worked call, with validation and error handling, in my project's language.

Questions

How do I start?

Create an account and add money to your wallet. Then subscribe to this API in your dashboard and we switch it on for your account.

What comes with every API?

Auth, idempotency, consent and metering hooks, a unified error envelope, and a hash-chained audit trail, identical across every API on the platform.

What do I need to go live?

Subscribe to the API in your dashboard and we switch it on for your account after your payment. The request and reply format is the same in test and in production.

Is this compliant for regulated use?

Reads are consent-bound and DPDP and RBI-AA aligned. Every call lands in a hash-chained audit trail, and every API is switched on for your account individually.