The questions for a first technical call, with an example Singapore customer filled in. Answers set the routing plan.
Customer
Discovery notes
Every text model that can serve the workload under the residency policy, priced on the stated volume. Pick a row for the request config, code and a solution brief.
| Model | Cheapest compliant provider | $/M in, out | Monthly | Providers | Uptime 1d | Context |
|---|
Paste a customer's request body or curl. The desk reads the model's live endpoints, applies the provider preferences the way the docs describe, and shows who can serve it, who is excluded and why, and what the customer will see.
Request
Findings
Run a simulation.
Endpoints
| Provider | First pick | $/M in, out | Datacenters | ZDR | Uptime 1d | Excluded because |
|---|
Error decoder
Send for real with your own key (optional)
Goes from this browser straight to openrouter.ai. The key stays in this tab's memory and is never sent to this site's server. Costs whatever the call costs on your account.
Handoff note for US Support
Run a simulation first.
What OpenRouter can promise an Asia Pacific buyer about where prompts go, from provider-declared metadata. In-region routing covers the EU and the US; in APAC the tools are provider pinning, ZDR and guardrails.
Endpoints by declared datacenter location
What to tell an APAC buyer
Changes since the bundled snapshot
Provider registry
| Provider | HQ | Datacenters | Models | Endpoints | ZDR endpoints | Slug |
|---|
Every number on the homework page, recomputed from OpenRouter's API in this browser, plus live probes of the API behaviour the desk depends on. If OpenRouter changes, this tab says which line of the page is now out of date.
Homework numbers
| Claim | On the page | Now | Status | Evidence |
|---|