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:| 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 need to approve only EU-region models (see below).
EU Endpoint
| Protocol | EU Endpoint |
|---|---|
| OpenAI-compatible | https://router.eu.requesty.ai/v1 |
| Anthropic-compatible | https://router.eu.requesty.ai |
Quick Start
- OpenAI SDK (Python)
- OpenAI SDK (TypeScript)
- Anthropic SDK
- cURL
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.

- AWS Bedrock: Models with
@eu-central-1,@eu-west-1,@eu-north-1suffixes (Claude, Kimi, Llama, Mistral) - Google: Models with
@europe-west1,@europe-west4,@europe-central2suffixes (Gemini) - Azure: Models with
@francecentral,@swedencentralsuffixes - Mistral: Hosted in EU by default
Use with AI Coding Tools
Claude Code
Cline / Roo Code
In your VS Code settings, set the API base URL to: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:EU Load Balancing
Distribute across EU regions with a Load Balancing Policy:Other Regional Endpoints
Requesty also offers regional endpoints outside the EU:| Region | Endpoint |
|---|---|
| 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
| 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 |
| PII Protection | Enable Guardrails for automatic PII detection and redaction |
| 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 |