Skip to main content

Regions and privacy

API endpoints​

All endpoints serve the same API and work with the same API key.

EndpointOpenAI-compatible clientsClaude Code and Anthropic clients
Global (default)https://api.stdcmpt.com/v1https://api.stdcmpt.com
EUhttps://eu.stdcmpt.com/v1https://eu.stdcmpt.com
UShttps://us.stdcmpt.com/v1https://us.stdcmpt.com

To use the US endpoint, change the base URL in your client:

client = OpenAI(
    base_url="https://us.stdcmpt.com/v1",
    api_key=os.environ["STANDARDCOMPUTE_API_KEY"],
)

For Claude Code, set ANTHROPIC_BASE_URL=https://us.stdcmpt.com.

Compliance rules​

Compliance rules are opt-in. Keys without a rule use standard routing: requests can run at any provider worldwide, under each provider's own terms. To restrict where requests run, use Compliance in the dashboard.

Choosing a region​

In Compliance, choose where your data can go:

  • Anywhere: no restriction. This is the default.
  • Europe: requests only run at provider endpoints in Europe.
  • United States: requests only run at provider endpoints in the United States.

You can also allow both Europe and the United States. The dashboard shows how many models and providers are available for your choice before you save. Changes apply to new requests.

Who a rule applies to​

  • Personal keys: set one rule for your own keys.
  • Company: a company admin sets a rule that covers every company key, including keys created later.
  • Team or single key: an admin can narrow the company rule for a team or one key, but never widen it.

Personal keys and company keys have separate rules.

What a restricted key does​

When a key is under a Europe or United States rule:

  • Requests only go to approved, exact provider endpoints in the allowed regions. That includes provider fallbacks and the classifier that picks a model for smart routing.
  • Response storage is turned off.
  • There is no fallback outside the rule. A request that can't be served in your regions fails with 400 and code data_policy_restriction; it is never sent elsewhere, and no prompt reaches a provider.
  • Models with no approved endpoint in your regions are skipped. If none of the models you selected has one, requests fail until you change your models or your regions.
  • Requests must be stateless. previous_response_id, conversation, background, plugins, presets and server-side tools are rejected; client-side function tools work as usual.

Restricting regions can exclude some models and lower-cost providers, so your compute budget may go less far. Your plan price stays the same.

Zero data retention (ZDR) is a separate setting on your account.

A rule controls where model providers run inference. It is not end-to-end data residency: the Standard Compute gateway and its upstream router can process traffic outside the selected regions, and a provider's zero data retention terms can still allow temporary prompt caching.

Your data​

Standard Compute does not read or analyze prompt content. See the privacy policy and data privacy overview.