Channel reach · Platform thesis

One engine. Four channel faces.

Neha's tied-agent app is one of four faces on the same platform. Same Capability APIs power partner banks, POSPs and brokers, and embedded SDKs at clinics, pharmacies, wellness apps. Hover a channel to see which APIs it consumes — or hover an API to see which channels use it.

How the engine fans out
interactive
Capability APIs (six engines)
Tip: hover any channel or API. Click a channel to see the dedicated surface — Banca, POSP, or the Embedded SDK playground.
Capability APIs

Six engines, every channel consumes the same

Sub-second SLAs. The unglamorous rigor that wins channel partners.

quote.v399.97%
p95 latency
184ms
underwrite.v299.93%
p95 latency
412ms
claim.v399.95%
p95 latency
256ms
renew.v199.99%
p95 latency
120ms
service.v299.92%
p95 latency
198ms
network.v199.98%
p95 latency
76ms
Aggregators

The reliability layer

Sub-second integration SLAs. Webhook reliability. Transparent commissions.

Live partner integration status
Real-time, last 5 minutes
PolicyBazaar
Production · 8,400 policies/mo
Live
Coverfox
Production · 2,100 policies/mo
Live
InsuranceDekho
Production · 1,300 policies/mo
Live
Acko Aggregator
Pilot integration
Pilot

Why the channel surface is one product, not five

Tied agent + banca + POSP + embedded — they all consume the same Capability APIs, the same policy DSL, the same fraud scoring, the same NHCX exchange. When we ship a new ML model for underwriting, every channel benefits the same day. When a regulator issues a new circular, we patch one DSL and every channel is compliant.

That leverage is the entire reason for the platform thesis.