Frequently asked questions

You declare it at the key, workspace or individual call, in that order of precedence. The caller's network location is ignored: a request can originate anywhere, while the obligation follows the data.

The exact returned text is No endpoints found supporting your data region (CN).. The request fails immediately. It is never retried against a provider outside the jurisdiction because that provider was not a candidate

Yes. Most teams put regulated workloads on a key or workspace with a jurisdiction and leave the rest unbound. Unbound requests use price and latency for routing, with no residency claim attached.

For jurisdiction-bound requests, yes. Selection stays within endpoints whose recorded region satisfies that jurisdiction, and the selected endpoint is recorded. A provider that publishes no serving region is treated as ineligible.

Menu Items cannot make you compliant. It enforces the routing rules you configure and records what it did. That record is the evidence layer. Filing obligations, consent and impact assessments remain yours.

The site records documented law and observed infrastructure, with dates and sources. It does not provide legal advice.

For each request, you get a record with the jurisdiction decision, the policy used, the selected provider and the serving region. You can export it.

Cache partitions follow jurisdiction. A prefix cached in one jurisdiction stays there and cannot pull work across a boundary. We measure and publish the hit-rate cost.

Nothing beyond tokens. Every tier includes enforcement, refusal semantics and residency records.

No. Traffic on your provider keys goes through the same policy layer and carries no token markup. You pay for routing, while the provider contract remains yours.

Rates are dated. Provider rates move, and the rate card moves with them.

No. Menu Items routes to providers that run the compute. A model without an endpoint inside your jurisdiction cannot be served there.

Menu Items exposes an OpenAI-compatible chat completions endpoint. Existing clients, frameworks and editor plugins keep their logic and change only the base URL.

Retries stay within providers that pass the same policy. Under load the eligible set can shrink, but it cannot widen past a border. Capacity is planned as headroom inside the region.

Media stages, including transcription, OCR and captioning, use the same jurisdiction decision as the originating request. If the selected model cannot serve a modality in-region, the request is refused rather than downgraded to a global endpoint.