Is there an EU-hosted LLM API for coding agents like Claude Code?
Yes. Standard Compute can restrict an API key, a team or a whole company to Europe, and every request then runs at a provider endpoint in Europe, across 13 models including Claude Opus 5.5, Claude Sonnet 5.5 and GPT-5.6. Our account database is in Frankfurt. Requests still pass through our gateway and OpenRouter, which can process them outside the EU, so the restriction sets where inference runs.
Models that run in Europe
13 models have a European endpoint. A Europe-only key can't use the rest of the catalogue. Where each provider is based and what it keeps is in the provider directory.
| Model | Provider endpoints in Europe |
|---|---|
| Claude Opus 5.5 | Google Vertex AI (Europe) · Amazon Bedrock (Ireland) |
| Claude Opus 5 | Google Vertex AI (Europe) · Amazon Bedrock (Ireland) |
| Claude Haiku 5.5 | Google Vertex AI (Europe) |
| Claude Sonnet 5.5 | Google Vertex AI (Europe) |
| Claude Sonnet 5 | Google Vertex AI (Europe) · Amazon Bedrock (Ireland) |
| GPT-5.6 Luna | Microsoft Azure (EU Data Zone) |
| GPT-5.6 Terra | Microsoft Azure (EU Data Zone) |
| GPT-5.6 Sol | Microsoft Azure (EU Data Zone) |
| Gemini 3.5 Flash-Lite | Google Vertex AI (Europe) |
| GLM 5.2 | Inceptron (EU/EEA) · Mistral (EU) |
| GLM 5.3 | Inceptron (EU/EEA) |
| GLM 5.3 Flash | Inceptron (EU/EEA) |
| DeepSeek V4 Flash 0731 | Inceptron (EU/EEA) |
From the endpoint list the gateway enforces, reviewed 2026-10-13. Regions are named as each provider names them: Azure's EU Data Zone keeps processing in EU member states, Bedrock runs in eu-west-1 (Ireland), and Inceptron states that it processes everything in the EU/EEA. Gemini 2.5 Pro and Flash also have European routes but close to new selections on October 20.
How to restrict a key, team or company to Europe
The rule lives on the key, so nothing changes in your agent. Keep the base URL https://api.stdcmpt.com/v1, or for Claude Code set ANTHROPIC_BASE_URL to https://api.stdcmpt.com.
- Personal keys: open Compliance in the dashboard sidebar, choose Europe, click Save and confirm with Restrict to Europe. The confirmation lists any of your selected models that would stop working.
- Company keys: an admin sets the company rule on the company's Compliance page. Every current and future company key follows it.
- Teams and single keys can narrow the company rule, never widen it. A key's own rule is under Compliance in its panel in People & keys.
What happens to each request
- It goes only to the European endpoints listed for its model. Failover stays inside that list, with no fallback to another model.
- Smart routing (model standardcompute) picks among the European models, and the classifier that picks also runs at a European endpoint.
- A model with no European endpoint fails with HTTP 400: "No prompt was sent to a provider."
- It asks the provider for zero data retention and no training, and turns off response storage. The provider's own policy is what applies.
- It must be stateless. Stored response chains, background jobs, plugins and server-side tools such as provider-hosted web search are rejected; your agent's own function tools work.
What this does not guarantee
- These are provider inference location controls. Our gateway and OpenRouter can process traffic outside the selected regions; this is not end-to-end data residency.
- Account, security, billing and usage metadata are kept to run the service, and a provider's zero data retention terms can still allow temporary prompt caches.
- End-to-end zero data retention across all routing infrastructure has not yet been confirmed.
- Certifications such as SOC 2 vary by provider.
- The plan price stays the same, but Europe-only can exclude low-cost providers and use your compute budget faster.
Facts for procurement
| Question | Answer |
|---|---|
| Account data | Supabase on AWS eu-central-1 (Frankfurt): email, encrypted API keys, plan and usage counters |
| Prompts and responses | Not stored or logged by us. They pass through our routing layer in memory |
| Sub-processors | Supabase, Stripe, OpenRouter and the model providers above. Details on data and privacy |
| Governing law | Norwegian law, courts of Oslo. Norway is in the EEA, where GDPR applies |
| Change history | Compliance changes are recorded in the company's Audit log |
| Invoices | Company checkout runs on Stripe, asks for your billing address and lets you add a VAT or tax ID. Paid subscription invoices are emailed with a PDF link, and admins see them under Billing |
| Price | A company account is free. Plans start at $19 a month per person; business plans start at $499 a month. Prices are in USD |
Where Standard Compute fits
Create a company, set Compliance to Europe once, and every key your team creates follows it. Claude Code, Codex CLI, OpenCode and other agents connect through the same API.
FAQ
Is Standard Compute a GDPR compliant LLM API for coding agents?
GDPR compliance depends on how your company processes personal data, so no API can promise it for you. Standard Compute keeps its account database in Frankfurt, does not store or log prompts and responses, operates under Norwegian law inside the EEA, and can restrict a key so inference runs at European provider endpoints. Include the routing layer in your assessment, since it can process requests outside the EU.
Can Claude Code use a Europe-only key?
Yes. Set ANTHROPIC_BASE_URL to https://api.stdcmpt.com and use the restricted key. Claude Opus 5.5, Sonnet 5.5 and Haiku 5.5 run on Google Vertex AI or Amazon Bedrock in Europe. Claude Fable models have no European endpoint, and Claude Code's server-side web search is rejected because it is a provider-hosted tool.
Does any of my code leave the EU?
It can, in transit. Inference runs at a European provider endpoint, but our gateway and OpenRouter sit in front of it and can process the request outside the EU. We don't store or log prompt content.
What happens if my agent asks for a model with no European endpoint?
The request fails with HTTP 400 before any prompt is sent to a provider, and it is never routed outside Europe. This applies to GPT-6 Astra, Claude Fable 5.1, Kimi K3 and DeepSeek V4 Pro, among others. Use a model from the table or smart routing.
Can one team be Europe-only while the rest of the company is not?
Yes. Leave the company rule at Anywhere and set Europe on that team or on single keys. If the company rule is Europe, teams and keys can't widen it.
Does the Europe restriction cost more?
The plan price stays the same. European endpoints are sometimes more expensive than the cheapest global provider, so the same monthly compute budget can run out sooner.