Skip to main content
Route your AI traffic through Requesty’s EU infrastructure in Frankfurt, Germany (AWS eu-central-1). All processing and storage by Requesty stays in the EU. Combine with EU-only approved models for full end-to-end data residency.

How It Works

There are two layers to consider for EU data residency:
LayerWhat it coversHow to enable
Requesty ProcessingRequest routing, logging, caching, analytics — all in EUUse router.eu.requesty.ai as your base URL
Model InferenceWhere the AI model actually runsApprove only EU-region models via the Model Library
Using the EU endpoint guarantees that Requesty’s processing and storage stays in the EU. To also guarantee that model inference stays in the EU, you need to approve only EU-region models (see below).

EU Endpoint

ProtocolEU Endpoint
OpenAI-compatiblehttps://router.eu.requesty.ai/v1
Anthropic-compatiblehttps://router.eu.requesty.ai
Same API key, same request format, same features — just swap the base URL.

Quick Start

import openai

client = openai.OpenAI(
    api_key="YOUR_REQUESTY_API_KEY",
    base_url="https://router.eu.requesty.ai/v1",  # EU endpoint
)

response = client.chat.completions.create(
    model="anthropic/claude-sonnet-4-5-20250514",
    messages=[{"role": "user", "content": "Hello from Europe!"}]
)

print(response.choices[0].message.content)

Approve EU-Only Models

By default, the EU endpoint can route to any model — including models hosted outside the EU. The Requesty processing stays in the EU, but the model inference might not. To guarantee that both Requesty processing and model inference stay in the EU, restrict your organization to EU-region models only:
1

Open the Model Library

Go to Model Library and switch to Table view for the best overview.
2

Filter by EU Regions

Click the Regions filter and select EU regions: EU, FRANCECENTRAL, SWEDENCENTRAL, or any other European region.
3

Select and Approve

Select all the EU models you want to allow, then click Add Selected to Approved Models. This restricts your organization to only use these models.
Filter and approve EU-only models in the Model Library The Model Library shows you all available EU models with their provider, pricing, context window, and capabilities (Vision, Reasoning, Tools, Cache). EU-region models include:
  • AWS Bedrock: Models with @eu-central-1, @eu-west-1, @eu-north-1 suffixes (Claude, Kimi, Llama, Mistral)
  • Google: Models with @europe-west1, @europe-west4, @europe-central2 suffixes (Gemini)
  • Azure: Models with @francecentral, @swedencentral suffixes
  • Mistral: Hosted in EU by default
If you enable Approved Models with only EU-region models, any request using a non-approved model will be rejected. This is by design — it ensures no data leaves the EU for model inference.

Use with AI Coding Tools

Claude Code

export ANTHROPIC_BASE_URL=https://router.eu.requesty.ai
export ANTHROPIC_API_KEY=YOUR_REQUESTY_API_KEY
claude

Cline / Roo Code

In your VS Code settings, set the API base URL to:
https://router.eu.requesty.ai/v1
See the Cline or Roo Code integration guides for full setup.

Combine with Routing Policies

EU routing works with all Requesty features. Create routing policies that stay entirely within EU infrastructure:

EU Failover Policy

Create a Fallback Policy across EU regions:
Policy: eu-claude
├─ bedrock/claude-sonnet-4-5-v2@eu-central-1 (2 retries)
├─ bedrock/claude-sonnet-4-5-v2@eu-west-1 (2 retries)
└─ bedrock/claude-3-5-haiku@eu-central-1 (1 retry)

EU Load Balancing

Distribute across EU regions with a Load Balancing Policy:
Policy: eu-balanced
├─ bedrock/claude-sonnet-4-5-v2@eu-central-1: 50%
└─ bedrock/claude-sonnet-4-5-v2@eu-west-1: 50%

Other Regional Endpoints

Requesty also offers regional endpoints outside the EU:
RegionEndpoint
EU (Frankfurt)https://router.eu.requesty.ai/v1
US (Global)https://router.requesty.ai/v1
All regional endpoints use the same API key. No additional configuration needed — just change the base URL.

Compliance Summary

RequirementHow Requesty Covers It
GDPR Data ResidencyEU endpoint processes and stores all data in Frankfurt (AWS eu-central-1)
EU-Only Model InferenceApprove only EU-region models in the Model Library
PII ProtectionEnable Guardrails for automatic PII detection and redaction
Access ControlUse RBAC to restrict who can change model approvals
Audit TrailFull request logging via Usage Analytics
Data MinimizationUse Request Metadata to tag and track data flows
Last modified on April 8, 2026