EU Routing

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.

EU routing with Requesty: an encrypted request enters the EU router in Frankfurt and is routed to EU-hosted models in AWS, Azure, and GCP regions, with all processing, storage, and inference staying within the EU. — Your request enters in Frankfurt, stays in the EU, and reaches EU-hosted models across AWS, Azure, and GCP.

Try regional routing in the Playground or configure allowed regions for your organization.

Using the EU endpoint alone only guarantees that Requesty’s processing stays in the EU. To ensure your data never leaves the EU, you must also use an EU model (e.g. bedrock/claude-sonnet-4-5-v2@eu-central-1 or vertex/gemini-3.5-flash@eu). If you use a global model like anthropic/claude-sonnet-4-5-20250514, your request will be forwarded outside the EU for inference.

How It Works

There are two layers to consider for EU data residency:

Layer	What it covers	How to enable
Requesty Processing	Request routing, logging, caching, analytics, all in EU	Use `router.eu.requesty.ai` as your base URL
Model Inference	Where the AI model actually runs	Approve 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 must use an EU region model (see below).

EU Endpoint

Protocol	EU Endpoint
OpenAI-compatible	`https://router.eu.requesty.ai/v1`
Anthropic-compatible	`https://router.eu.requesty.ai`

Same API key, same request format, same features. Just swap the base URL.

Select a region in the Playground

The Playground can send requests through the Global, EU, US, or AP Requesty router. Use the Router endpoint selector beside the model selector before sending a request. The selected endpoint applies to:

Single-model chat
Chat comparison
Image generation
Image comparison

The selector follows your organization’s allowed-region policy. If an admin restricts serving regions in Compliance, the Playground only offers those regional endpoints and removes Global. For example, an EU-only organization sees only EU.

The Playground selector controls where Requesty processes the request. It does not control where the model provider runs inference. Select an appropriately hosted model as well when you need end-to-end regional data residency.

Quick Start

OpenAI SDK (Python)
OpenAI SDK (TypeScript)
Anthropic SDK
cURL

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="bedrock/claude-sonnet-4-5-v2@eu-central-1",  # EU model
    messages=[{"role": "user", "content": "Hello from Europe!"}]
)

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

import OpenAI from 'openai';

const client = new OpenAI({
    apiKey: 'YOUR_REQUESTY_API_KEY',
    baseURL: 'https://router.eu.requesty.ai/v1',  // EU endpoint
});

const response = await client.chat.completions.create({
    model: 'bedrock/claude-sonnet-4-5-v2@eu-central-1',  // EU model
    messages: [{ role: 'user', content: 'Hello from Europe!' }],
});

console.log(response.choices[0].message);

import anthropic

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

message = client.messages.create(
    model="bedrock/claude-sonnet-4-5-v2@eu-central-1",  # EU model
    max_tokens=1024,
    messages=[{"role": "user", "content": "Hello from Europe!"}]
)

print(message.content[0].text)

curl https://router.eu.requesty.ai/v1/chat/completions \
  -H "Authorization: Bearer YOUR_REQUESTY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "bedrock/claude-sonnet-4-5-v2@eu-central-1",
    "messages": [{"role": "user", "content": "Hello from Europe!"}]
  }'

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:

Open the Model Library

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

Filter by EU Regions

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

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, Llama, Mistral)
Google Vertex: Models with @eu suffix (e.g. vertex/gemini-3.5-flash@eu, vertex/gemini-3.1-flash-lite@eu)
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.

Enforce EU routing for the organization

Switching a client or the Playground to EU is a per-request choice. To require all organization traffic to use the EU endpoint, restrict the organization’s allowed Requesty regions:

Open Compliance

Go to Compliance. You must be an organization admin.

Edit the serving region

In the Requesty policy table, select Edit beside Serving region.

Restrict the organization to EU

Select Restrict regions, choose EU, and select Save regions.

The change takes effect immediately. Requests through the global, US, or AP endpoint are rejected, and the Playground only offers EU. Every user and API key must use https://router.eu.requesty.ai. Combine organization-wide EU enforcement with EU-only approved models for a complete guarantee covering both Requesty processing and 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:

Priority	Model	Retries
1st	`bedrock/claude-sonnet-4-5-v2@eu-central-1`	2 retries
2nd	`bedrock/claude-sonnet-4-5-v2@eu-west-1`	2 retries
3rd	`bedrock/claude-3-5-haiku@eu-central-1`	1 retry

EU Load Balancing

Distribute across EU regions with a Load Balancing Policy:

Model	Weight
`bedrock/claude-sonnet-4-5-v2@eu-central-1`	50%
`bedrock/claude-sonnet-4-5-v2@eu-west-1`	50%

Regional Endpoints

All endpoints accept the same API key and request format:

Region	Endpoint
Global	`https://router.requesty.ai/v1`
EU (Frankfurt)	`https://router.eu.requesty.ai/v1`
US	`https://router.us.requesty.ai/v1`
AP	`https://router.ap.requesty.ai/v1`

For Anthropic-compatible requests, use the same host without /v1, for example https://router.ap.requesty.ai.

Compliance Summary

Requirement	How Requesty Covers It
GDPR Data Residency	EU endpoint processes and stores all data in Frankfurt (AWS `eu-central-1`)
EU Only Model Inference	Approve only EU region models in the Model Library
Organization Wide EU Enforcement	Allow only EU under Serving region on the Compliance page
PII Protection	Enable Guardrails for automatic PII detection and masking
Access Control	Use RBAC to restrict who can change model approvals
Audit Trail	Full request logging via Usage Analytics
Data Minimization	Use Request Metadata to tag and track data flows

Getting Started

LLM Gateway

Model Capabilities

Analytics & Monitoring

Access Control

Organization

MCP Gateway

How It Works

EU Endpoint

Select a region in the Playground

Quick Start

Approve EU Only Models

Enforce EU routing for the organization

Use with AI Coding Tools

Claude Code

Cline / Roo Code

Combine with Routing Policies

EU Failover Policy

EU Load Balancing

Regional Endpoints

Compliance Summary

​How It Works

​EU Endpoint

​Select a region in the Playground

​Quick Start

​Approve EU Only Models

​Enforce EU routing for the organization

​Use with AI Coding Tools

​Claude Code

​Cline / Roo Code

​Combine with Routing Policies

​EU Failover Policy

​EU Load Balancing

​Regional Endpoints

​Compliance Summary

How It Works

EU Endpoint

Select a region in the Playground

Quick Start

Approve EU Only Models

Enforce EU routing for the organization

Use with AI Coding Tools

Claude Code

Cline / Roo Code

Combine with Routing Policies

EU Failover Policy

EU Load Balancing

Regional Endpoints

Compliance Summary