RAXI doesn't build ambulances or underwrite risk. It builds the orchestration layer that connects the players who already do — Detection through Data Authority, end to end.
A crash has to reach RAXI before RAXI can do anything about it. Rather than depend on a single channel, Detection layers three inputs so a gap in one is covered by another.
Fleet telematics send event-triggered webhooks the moment a sudden deceleration or rollover is registered — no need for anyone to make a call. Where telematics coverage is thin, SMS and USSD citizen reporting (*XXX*1#) let bystanders report what they see. A lightweight panic button gives riders themselves a third channel.
The target is under 5 seconds from impact to RAXI's receipt of a telematics event — the interval that determines whether "Golden Hour" trauma care is even possible.
A bike falling over in a parking lot looks like a crash to a G-force sensor. Triage is what stops that from becoming an unnecessary ambulance dispatch — and what stops a real crash from being dismissed as one.
An NLP parser extracts location, severity keywords, vehicle type, and victim count from unstructured SMS reports. In parallel, a multi-signal validation protocol runs: an automated callback to the rider, a check on whether GPS shows the bike stationary, and a check for corroborating citizen reports from nearby. Dispatch proceeds only when the signals agree.
This is RAXI's central innovation. Standard insurance "Letters of Undertaking" are issued manually, during office hours, with physical signatures — useless for a 3 a.m. crash. RAXI replaces that with a real-time digital guarantee.
Within seconds of a validated crash, RAXI queries the insurer's API to confirm the rider's coverage, generates a cryptographically signed GOP code, and registers it against the insurer's pre-approved cover pool. The hospital verifies the code by USSD or API and admits the patient — without a cash deposit.
RAXI sits between the insurer (who holds the risk capital) and the hospital (who delivers care) as a Third-Party Administrator, not as an insurer itself.
RAXI does not recruit or own ambulances. It integrates with Rescue.co's existing network via API — the same infrastructure that already powers emergency response for Bolt and Uber.
Once a crash is validated, RAXI calls the Rescue.co API with incident location, severity, and the newly issued GOP code. The nearest available unit is dispatched, ETA is tracked, and the receiving hospital is notified — with the GOP code attached — before the ambulance arrives, so the ER can prepare.
Kenyan road-crash data currently stops at one of two points: the police report at the scene, or the hospital admission record. Neither tracks what happens after — whether a victim recovered, was disabled, or died days later of complications attributed to something other than the original injury.
RAXI follows every dispatched case for 30 days through SMS check-ins and, where possible, hospital discharge records. Where a delayed death is suspected, RAXI can cross-reference against death certificates to correctly attribute it as a road traffic fatality — data Kenya's official statistics currently miss.
The resulting anonymized dataset is designed to be published as an open data standard, so other health-tech and county systems can adopt the same schema.