Platform engineering
The endpoint shape, retry behaviour and cache semantics. Whether it drops into an existing client.
Workload and jurisdiction walkthrough
A walkthrough is a working session. We take a request from your stack, show what the router does with it, and identify where coverage does not yet exist for your jurisdiction.
- 45
- Minutes
- 1
- Workload, described by you
- 0
- Slides about our funding
- Coverage
- Gaps reviewed in the session
Working session
01
Session steps
Four steps
You describe one request
Describe what it contains, the model you want, and the jurisdiction it must stay inside. Bring a real request example.
We run the decision with you
We review payload signals, the eligibility gate, the ranked candidate set, and the recorded reason using your workload.
We show the refusals
If your jurisdiction has no eligible endpoint for the model, we show the refusal in the session.
You get a written summary
The candidate sets, coverage gaps, and residency posture we can support in writing. You can use it whether or not you proceed.
Enterprise procurement, security questionnaires, and residency attestations are handled after the walkthrough.
02
For more than one attendee
What attendees usually need
Compliance and risk
The refusal semantics in writing, the residency record format, and where our claims stop.
Finance
Per-token rates, what enforcement costs in hit rate, and how bring-your-own-key is treated.
If a session is not right yet
Start