Consumer credit report by PAN.
Credit Bureau
Pull a consumer credit report by PAN with the bureau score, account list, and enquiry history. The call fires a consumer alert, so this is a regulated rail that needs an approved access request before a key can hold it.
Endpoints
Every endpoint shares auth, idempotency, consent and metering hooks, a unified error envelope, and a hash-chained audit trail.
Bureau score + accounts + enquiries (fires consumer alert).
How it works
From signup to a live Credit Bureau call in four steps.
Create a free account
Sign up and get a prefunded sandbox key in seconds. No card required.
Unlock the rail
File an access request from the dashboard. The scope is released after admin approval.
Make your first call
Send the sample request to /v1/credit/consumer-report with your sandbox key and read back live JSON.
Go live
Swap the sandbox key for a live key. Every call is metered, itemized, and audit-chained.
Call consumer credit report
The flagship call for this rail. Swap the sandbox key for your own and you are live.
Developer ready
Docs, MCP, and a prompt that does the work
Every rail ships with an integration guide, an MCP server for AI agents, and a ready-to-paste prompt, so your first Credit Bureau call takes minutes, not days.
Integration guide
The quickstart covers keys, auth, idempotency, the error envelope, and paise money units. The catalog documents every Credit Bureau 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://api.grappi.in",
"GRAPPI_API_KEY": "sk_sandbox_••••"
}
}
}
}Prompt-ready integration
Paste this into Claude, Cursor, or any coding agent. It carries the real contract rules, so the generated client matches the gateway on the first try.
Integrate the Grappi Credit Bureau API into my app. Endpoints: - POST /v1/credit/consumer-report (Consumer credit report) Contract rules: send the key as the x-api-key header, treat all money as integer paise (₹1.00 = 100), send an Idempotency-Key on every POST, and branch on the error envelope error.code (handle 402 insufficient_balance, 403 consent_required, 422 validation_failed, 429 rate_limited). Write a small typed client for these endpoints plus one worked call, with validation and error handling, in my project's language.
Frequently asked questions
Can I try it for free?
Yes. Signing up creates a sandbox key, so you can call this rail immediately without a card. Sandbox calls run against test data, not production.
What comes with every endpoint?
Auth, idempotency, consent and metering hooks, a unified error envelope, and a hash-chained audit trail — identical across every rail on the platform.
What do I need to go live?
License plus admin approval. Released after an approved access request. Once live, the same key and the same contract carry over from sandbox.
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 regulated rails stay locked until an access request is approved.
Related products
Other rails on the regulated tier.
Get started
Start building with Credit Bureau
Create a free sandbox account, get a prefunded key, and call Credit Bureau on the same contract as every other rail.
- Instant sandbox key, no card required
- One key works across every rail
- Open rails are live the moment you sign up