For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
ModelsChatRankingsDocs
DocsAPI ReferenceClient SDKsAgent SDKCookbookChangelog
DocsAPI ReferenceClient SDKsAgent SDKCookbookChangelog
  • Overview
    • Quickstart
    • Principles
    • Models
    • Stripe Projects
    • FAQ
    • Report Feedback
  • Models & Routing
    • Model Fallbacks
    • Provider Selection
    • Auto Exacto
    • Private Models
  • Features
    • Workspaces
    • Presets
    • Response Caching
    • Tool Calling
    • Structured Outputs
    • Message Transforms
    • Zero Completion Insurance
    • ZDR
    • App Attribution
    • Service Tiers
    • Sovereign AI
    • Router Metadata
    • Input & Output Logging
LogoLogo
ModelsChatRankingsDocs
On this page
  • Why Sovereign AI Matters
  • Regulatory Compliance
  • Data Residency and Privacy
  • How OpenRouter Enables Sovereign AI
  • EU In-Region Routing
  • Zero Data Retention (ZDR)
  • Data Collection Controls
  • Building a Sovereign AI Stack with OpenRouter
  • Getting Started
Features

Sovereign AI

Keep AI workloads within national and regional boundaries
Was this page helpful?
Previous

Router Metadata

Surface routing decisions on every response with a single opt-in header

Next
Built with

Sovereign AI refers to a nation’s or region’s ability to develop, deploy, and control artificial intelligence systems within its own borders, using local infrastructure and under local regulatory frameworks. As AI becomes critical infrastructure, governments and enterprises increasingly require that AI workloads — including the data they process — remain within specific geographic and jurisdictional boundaries.

OpenRouter offers fully in-region routing in the EU for enterprise customers. Contact our enterprise team to enable it for your account.

Why Sovereign AI Matters

Sovereign AI is driven by two converging forces:

Regulatory Compliance

Regulations like the EU AI Act, GDPR, and sector-specific rules (healthcare, finance, defense) impose strict requirements on where data can be processed and stored. Organizations operating across jurisdictions need infrastructure that respects these boundaries.

Data Residency and Privacy

Sensitive data — whether personal, financial, or classified — may not legally or ethically leave a particular jurisdiction. Sovereign AI ensures that prompts and completions are processed entirely within a designated region, with no cross-border data transfers.

How OpenRouter Enables Sovereign AI

OpenRouter provides several features that enable sovereign AI deployments today, allowing enterprises to maintain control over where their AI workloads are processed.

EU In-Region Routing

For enterprise customers, OpenRouter supports EU in-region routing. When enabled, your requests are guaranteed to only be decrypted within the designated region, and are only routed to providers operating in that region. This means prompts and completions are processed entirely within the European Union — they never leave the EU at any point in the request lifecycle.

To use EU in-region routing, send API requests through the EU-specific base URL:

https://eu.openrouter.ai
1import { OpenRouter } from '@openrouter/sdk';
2
3const openRouter = new OpenRouter({
4 apiKey: '<OPENROUTER_API_KEY>',
5 serverURL: 'https://eu.openrouter.ai/api/v1',
6});
7
8const completion = await openRouter.chat.send({
9 model: 'meta-llama/llama-3.3-70b-instruct',
10 messages: [{ role: 'user', content: 'Hello' }],
11 stream: false,
12});
EU-only models list

To see which models are available for EU in-region routing, you can:

  • Call /api/v1/models through the EU domain to get the full list programmatically
  • Browse EU-eligible models on the models page using the In-Region Routing filter

EU in-region routing is available for enterprise customers by request. Contact our enterprise team to enable it for your account.

Zero Data Retention (ZDR)

Zero Data Retention ensures that providers do not store your prompts or responses. This is a key component of sovereign AI, as it guarantees that no data persists outside your control after a request completes.

ZDR can be enforced per model group (Anthropic, OpenAI, Google, and non-frontier) in your privacy settings, via guardrails, or per-request:

1{
2 "model": "meta-llama/llama-3.3-70b-instruct",
3 "messages": [{ "role": "user", "content": "Hello" }],
4 "provider": {
5 "zdr": true
6 }
7}

Data Collection Controls

Control whether providers can collect your data with the data_collection parameter:

1{
2 "provider": {
3 "data_collection": "deny"
4 }
5}

When set to "deny", your requests are only routed to providers that do not collect user data. This can also be configured as an account-wide default in your privacy settings.

Building a Sovereign AI Stack with OpenRouter

Combining these features, you can build a fully sovereign AI deployment:

  1. Enable EU in-region routing to keep all data within the EU
  2. Enforce ZDR to prevent any data retention by providers
  3. Deny data collection to prevent training on your data

This gives you a single API with unified billing while maintaining full control over data residency, privacy, and compliance — without the complexity of managing relationships with individual providers in each region.

Getting Started

Sovereign AI features are available to all OpenRouter users, with EU in-region routing available for enterprise customers. To get started:

  • Create an API key and start using provider routing to control where your requests are processed
  • Enable ZDR and data collection controls for privacy compliance
  • Contact our enterprise team to enable EU in-region routing and discuss additional sovereign AI requirements

For a complete enterprise setup guide, see the Enterprise Quickstart.