Payload-based selection
The request is classified before a provider is considered. Data class, modality, jurisdiction, context length and tool use determine eligibility. Price then orders only the providers that policy has already approved.
Account enquiries
Jurisdiction-enforced inference
Request jurisdiction
If your data has to stay in the country it came from, whether because a regulator requires it, a contract says so, or a customer asked, then where it is stored and where it is processed are your problem, not your vendor's. AI is one more place that data travels. Most AI platforms are built for the United States first. Everywhere else is an afterthought.
Menu Items handles East Asia. It is the routing layer for teams whose AI data has to stay in Japan, Korea, Singapore, Malaysia, Hong Kong, Taiwan or China.
With this service, your AI traffic goes to the right provider for the right request:
- Requests carrying personal information are served locally, in full compliance with the law.
- Requests carrying no personal data can be served from anywhere, so they go to the best model at the lowest price.
The menu of options for where to do your AI work expands every month. The law is the law, and we are here to help you stay compliant while managing what inference costs.
Region data describes documented law and observed provider infrastructure. It is not legal advice. Residency obligations vary by workload and data class.
Decision record
req_01JQ…- Jurisdiction
- CN · PIPL
- Payload class
- regulated
- 01
data_class = health_record
CN resident endpoints only
In regioncn-beijing
- 02
model = deepseek-v4-pro
2 endpoints pass policy
In regioncn-beijing
- 03
candidate = ap-southeast-1
Excluded, outside jurisdiction
Refused - 04
candidate = zai/glm-5.3
Excluded, region undisclosed
Refused - 05
selected
deepseek-v4-pro via cn-beijing
In regioncn-beijing
Only endpoints inside the jurisdiction were eligible, so price never selected an endpoint outside the requested jurisdiction.
Every response includes the decision record. It shows that policy was applied before price ranked the result.
- 44
- Model endpoints catalogued
- 18
- Providers, including cross-border deployments
- 18
- Entries whose serving region is unpublished
- 404
- Failure mode when no in-region endpoint exists
Region and rate stated per entry
Unpublished by provider
Never a cross-border fallback
Enforced jurisdictions
JP
Japan
APPI · consent for third-country transfer
KR
South Korea
PIPA · consent for cross-border transfer
SG
Singapore
PDPA · transfer limitation and contract
MY
Malaysia
PDPA · comparable protection before transfer
HK
Hong Kong
PDPO · due diligence for overseas access
TW
Taiwan
PDPA · international transfer restrictions
CN
China
PIPL · cross-border transfer rules
Menu Items covers Japan, South Korea, Singapore, Malaysia, Hong Kong, Taiwan and China.
01
What it does
Four routing decisions
First the router classifies and constrains the request. It selects an endpoint only when the eligible set is non-empty.
Jurisdiction enforcement
Region is declared at the key, workspace or call. Providers outside it leave the candidate set.
Forty-four endpoints, eighteen providers
Each entry gives its context window, rate, modalities and serving regions. It also records entries for which the provider publishes no region.
Refusal behaviour
If no eligible provider can serve the request, it fails with the constraint that emptied the candidate set. The boundary is never widened to keep a request alive.
02
Payload routing
Candidate sets by routing order
Optimising before filtering produces a different outcome from filtering before optimisation. This ordering can produce an undocumented transfer for the request.
Example price-first routing
- Cheapest endpoint is chosen first
- Jurisdiction constraint discovered afterwards
- Retry to an eligible endpoint counts as a transfer
- Selection log records a provider, not a reason
- Ineligible providers are removed from the set
- Price ranks only what policy already approved
- No cross-border retry path exists to take
- Selection log records the policy that applied
03
Catalogue
Catalogue coverage and gaps
Fields marked Unverified are unpublished by the provider.
| Model | Provider | Context | Input, per 1M | Regions | Residency |
|---|---|---|---|---|---|
| DeepSeek V4 Pro | DeepSeek | 1M | $0.3 | CN · cn-beijing | In region |
| DeepSeek V4.1 Flash | DeepSeek | 1M | $0.3 | CN · cn-beijing | In region |
| Qwen3.8-Max | Alibaba Qwen | 1M | $2.00 | ap-southeast-1 · ap-east-1 | Unguaranteed |
| Qwen3.8-Flash | Alibaba Qwen | 1M | $0.15 | ap-southeast-1 · ap-east-1 | Unguaranteed |
| Qwen3.7-Plus | Alibaba Qwen | 1M | 0.40 (0-256K input); 1.20 (256K-1M input) | ap-southeast-1 · ap-east-1 | Unguaranteed |
| Kimi K3 | Moonshot AI (Kimi) | 1.05M | $3.00 | cn-beijing · cn-hongkong | In region |
The featured tier starts with current China-based labs. The focus tier includes cross-border deployments, where the same model has a different legal position depending on the serving provider.
04
Solutions
Workload coverage
A single-endpoint review misses calls added by retrieval, media processing and agent loops.
05
Objections
Questions from buyers
“We already route through a gateway.”
“Our model provider already offers a regional endpoint.”
“We don't send personal data to models.”
“Fail-closed will break our product.”
“Nobody can verify a serving region anyway.”
“We could build this ourselves.”
06
Notes
Notes for reviewers
2 Oct 2026Routing
Request jurisdiction and provider selection
The decision record identifies the serving provider, country and policy permitting that location.
28 Sep 2026Compliance
What Singapore's PDPA requires before a prompt crosses the border
The obligation is contractual rather than approval-based, and a signed clause does not guarantee residency.
24 Sep 2026Market
Why US in-region routing doesn't help an East Asian bank
Chinese models served from American data centres address a different processing-location requirement from East Asian in-region workloads.
07
Getting started
Signup process
You give us an email address
The form stores your email address, and nothing else. It does not create an account, take a card or issue a key automatically.
We review the account request
We review the jurisdiction you name and reply by email with coverage and a region guide.
You point an existing client at us
The endpoint is OpenAI-compatible. An editor plugin, framework or script needs a new base URL, not a change to its logic.
You state a jurisdiction once
You declare the region at the key. Every request made with that key inherits the boundary, including tool calls that reviewers often miss.
Start
Account enquiries
Accounts are billed from the first token and include a region guide for the jurisdiction you name.