Business verification (KYB)
Udyam, TAN, TIN, shop licence and director checks.
Verify an MSME by its Udyam number, directly or with an OTP to the enterprise's registered mobile, and get its units, address, NIC codes and certificate link. Check a TAN or a state TIN, a shop and establishment registration in seven states, and a director's company associations by DIN from the MCA record.
- APIs
- 7 you can call
- Consent
- Bound to every read
- Audit
- Every call in a hash-chained log
APIs in Business verification (KYB)
Every API shares the same key, error format and audit log. Each one is switched on for your account separately.
Udyam (MSME) verification
Enterprise name, type, units, official address and NIC codes for a Udyam registration number, with the certificate PDF link.
POST /v1/business/udyamReferenceUdyam by OTP: send
Sends an OTP to the enterprise's registered mobile and returns the request_id.
POST /v1/business/udyam/otpReferenceUdyam by OTP: verify
Submits the OTP with the request_id from the send call and returns the registration.
POST /v1/business/udyam/otp/verifyReferenceTAN verification
Deductor details for a tax deduction account number (TAN).
POST /v1/business/tanReferenceTIN lookup
Dealer details for an 11-digit state TIN.
POST /v1/business/tinReferenceShop and establishment
Registration details from the state record. States: Rajasthan, Uttar Pradesh, West Bengal, Jharkhand, Maharashtra (category required), Karnataka, Delhi.
POST /v1/business/shop-establishmentReferenceDirector search by DIN
Director details and company associations from the MCA record for an 8-digit DIN.
POST /v1/business/directorReference
What teams use it for
Use cases for each Business verification (KYB) check. See how they combine with other products on the use cases page.
Enterprise name, type, address and activity codes for a Udyam registration.
- Verify an MSME before a business loan or credit line.
- Onboard suppliers who claim MSME status.
- Check the enterprise type and activity against what the business told you.
Fetches the Udyam registration after an OTP to the enterprise’s registered mobile.
- Prove the person onboarding controls the enterprise.
- Get the registration when the customer does not have the Udyam number to hand.
Deductor details for a tax deduction account number.
- Check the TAN of an employer or business customer.
- Validate the deductor on Form 16 or TDS certificates during income checks.
Dealer details for an 11-digit state TIN.
- Verify distributors and traders that registered under a state TIN.
- Check older invoices and trade records that carry a TIN.
Registration details from the state shop and establishment record.
- Verify small shops that have no company or GST registration.
- Confirm a merchant’s trading name and address before accepting payments for them.
- Business loan checks for retailers and service businesses.
Director details and company links from the MCA record.
- Confirm a director’s identity and companies during business onboarding.
- Check promoters and directors before a business loan.
- Spot directors linked to many companies, a common sign of shell entities.
How you get Business verification (KYB)
From a new account to a live call in four steps.
Create your account
Sign up with your work email and create an app and its key. No API is active on a new account.
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.
Make your first call
Once the API is activated, send the sample request to /v1/business/udyam with your key and read back the JSON.
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 udyam (msme) verification
The main call for this product. Use your own key once this API is switched on for your account.
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 Business verification (KYB) call takes minutes, not days.
Integration guide
The quickstart covers keys, auth, idempotency, the error envelope, and paise money units. The catalog documents every Business verification (KYB) 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.
{
"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 the Grappi Business verification (KYB) API into my app. Endpoints: - POST /v1/business/udyam (Udyam (MSME) verification) - POST /v1/business/udyam/otp (Udyam by OTP: send) - POST /v1/business/udyam/otp/verify (Udyam by OTP: verify) - POST /v1/business/tan (TAN verification) - POST /v1/business/tin (TIN lookup) - POST /v1/business/shop-establishment (Shop and establishment) - POST /v1/business/director (Director search by DIN) 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.