Outcome 01
KYC at the volume the insurer actually sees
PAN, Aadhaar, address proof, salary slip — every artefact OCR'd, cross-checked, tamper-flagged, and PII-redacted at the parquet boundary.
For life and general insurers
Onboarding that scales with policy volume — without paying a human reviewer for every easy case.
Document KYC under the UIDAI mask, forgery detection on scanned proofs, identity cross-checks with a Courtroom-signed bundle — and a sub-processor posture that satisfies IRDAI and DPDP at once.
Illustrative: a life insurer could process policy applications at scale with VLM-driven extraction and a forgery flag on every scan once the documents-KYC endpoint is wired.
Marketing claim
PAN + 12-digit Aadhaar redaction on every transcript and frame-OCR row before parquet write (UIDAI mandate, defense-in-depth).
The three outcomes a partner buys
What you actually get.
- Outcome 02
Forgery and alteration flagged with reason codes
PCA-PSI on the embedding space catches the four common patterns: copy-paste, font swap, photo-of-screen, repeated stamps. The reason set is returned alongside the score.
- Outcome 03
An audit chain IRDAI can verify from outside
Every extraction, every override, every Courtroom verdict — HMAC-chained, replayable years later, exportable on regulator request.
Integration · Day 1 → Day 90
Curl in five minutes.
- Day 101
Sandbox keys provisioned. Once the documents-KYC endpoint is wired, the insurer's KYC team POSTs the first document bundle through it and reads the extraction response.
- Day 702
Documents-KYC wired against the insurer's intake. The UIDAI 8-digit Aadhaar mask is applied at the parquet boundary; the original artefact is deleted after the configured retention window.
- Day 3003
Forgery flags routed to the insurer's human-review queue. Confidence bands published; low-confidence items auto-route to a second pass.
- Day 9004
Production cutover. The compliance team has replayed every flagged case and the four forgery patterns are signed off as live reason codes.
Models powering this vertical
Specialised models, one envelope.
Compliance · for the regulator's question list
Written into the architecture.
- IRDAI · onboarding and KYC guidelines
PII redaction enforced at the parquet boundary; the insurer's underwriter sees the masked artefact and the originals are deleted within the configured retention window.
- UIDAI · 8-digit Aadhaar masking
8-digit Aadhaar mask is fail-closed at the parquet write — the document VLM never returns the unmasked identifier downstream.
- DPDP §§11–14 · data-principal rights
Erasure and correction are wired self-serve on the consumer surface and as API endpoints on the partner surface. The insurer can request a hard-delete on a closed policy.
- DPDP §6 · purpose limitation
Consent is captured per policy application; secondary use (analytics, model training) is gated behind separate opt-in flags the insurer surfaces in its own form.
A typical week
What the integration feels like once live.
Monday morning
Weekend applications roll in; the extraction report names the cases where confidence fell below the band and were routed to the human-review queue.
Tuesday afternoon
A drift signal on the document VLM PCA fires through the self-healing observatory. The proposed retrain lands in the KYC ops queue.
Thursday standup
A new forgery pattern (photo-of-screen on a glossy printout) is captured in the feedback loop. The reason-code catalogue is reviewed and one is added.
Friday closeout
Compliance pulls the week's slice and replays every forgery flag. The chain verifies end-to-end; the IRDAI weekly attestation is filed.
See it as a story
Related user journeys.
Partner FAQ
The straight answers.
How long does an integration take?
Most partners go from sandbox keys to a shadow-mode production wire in seven days. Full cutover lands by Day 30–90 depending on which product lines you light up and how many sit on your side of the integration.
What does pricing look like?
Per-call usage on the live endpoints, with a transparent cost-budget meter and WARN + STOP thresholds you control. The /developers page has the public price card; volume discussions happen on the partnerships call.
How is the audit trail structured?
Every model output, every override, every webhook delivery — HMAC-chained and signed. Each row links to the prior HMAC, so a tampered row breaks the chain at verification time. The chain is exportable on request.
Who handles compliance with our regulator?
You do — Mukodi is your data processor under DPDP §8 and your IT-outsourcing vendor under the RBI master direction. We furnish the artefacts (DPA, audit chain, retention attestation) that satisfy your filings.
What happens if a model drifts or misbehaves?
Drift fires through the self-healing observatory and a retrain proposal lands in your review queue. Production rollout is gated behind your TOTP approval; rollbacks are one click and a 6-hour cooldown.
Can we keep our own model in the loop?
Yes. The Mukodi verdict can run in shadow alongside your model, with both scores delivered to your underwriter or SOC operator. Overrides flow back into the feedback loop and ship as labels to the next training cycle.
Hire the house · Insurers
Ready to talk?
Sandbox keys are free. The integration call is a single thirty- minute slot. Production cutover lands by Day 30–90 depending on which product lines you light up.