Step 01
Step 1
Sign up on the partner portal; get a sandbox key in minutes.
DeveloperB2Bpartial· marketing-claim · b2b-credit-risk-shap
B2B API + Python / Java / Node SDKs.
Score credit risk, verify documents, parse SMS — from any backend, in three SDK languages.
The problem
Why this exists.
Indian fintechs and lenders need credit-risk, fraud, and KYC building-blocks that ship with explainability and an Indian-data evaluation set.
We expose the platform as one API surface with auto-generated SDKs so partners do not write yet another OAuth client.
How it works · 3 steps
From input to outcome.
- Step 02
Step 2
Call the REST API directly today. Python / Java / Node SDKs are generated from the same OpenAPI spec and arrive with our first registry release — no package is published to pip, npm, or Maven yet, so treat any same-named package as not ours.
- Step 03
Step 3
Move to production with TOTP-gated key issuance and a usage dashboard.
Under the hood
The models and routes behind it.
Models called
API routes
- POST /api/v1/b2b
Compliance posture
- Every consequential output passes through the Courtroom under courtroom-replayable-audits.
- TOTP gate on key rotation, usage policy changes, and partner-level pause.
- DPDP §8 — partner-collected user data is governed by the data-processor agreement signed at onboarding.
What it's not
Our APIs are explainable building blocks, not turnkey lending decisions. Partners own the lending decision and the regulator-facing record.
Related · features & stories