Skip to main content
Wafer Serverless runs in two regions: a US edge at pass.wafer.ai and an EU edge at pass-eu.wafer.ai. Customers who need EU data residency point their SDK at the EU hostname; everyone else uses the default US endpoint.

​
Endpoints

RegionOpenAI-compatibleAnthropic-compatible
US (default)https://pass.wafer.ai/v1https://pass.wafer.ai
EUhttps://pass-eu.wafer.ai/v1https://pass-eu.wafer.ai
Both regions speak the same OpenAI- and Anthropic-compatible APIs. The only thing that changes is the hostname.

​
Authentication

The same wfr_… Serverless API key works against both regions — there’s no separate “EU key” to provision. Auth, billing, quotas, and your account-level credit balance are shared across regions. This means switching regions is a one-line config change: 
# US (default)
export ANTHROPIC_BASE_URL=https://pass.wafer.ai

# EU
export ANTHROPIC_BASE_URL=https://pass-eu.wafer.ai

​
Available Models in EU

The EU edge currently serves a curated subset of the catalog:
ModelNotes
GLM-5.1202K context, reasoning, ZDR
Qwen3.5-397B-A17B262K context, vision, reasoning, ZDR
Any other model ID (e.g. Kimi-K2.6, MiniMax-M3, deepseek-v4-pro) returns model_not_found when sent to pass-eu.wafer.ai. Call GET https://pass-eu.wafer.ai/v1/models for live availability.

​
Data Residency

All inference on pass-eu.wafer.ai runs on EU-resident workers. Prompts, completions, and any expanded file frames stay within EU infrastructure for the duration of the request. Zero Data Retention applies the same way it does on the US edge: send Wafer-ZDR: required to enforce no request-body retention. On the EU edge, ZDR is the default for the listed models — the header is still accepted for client-side certainty.

​
What’s Not Shared Across Regions

A few things are scoped to the region you uploaded to or operated against:
  • Files: a file uploaded to pass.wafer.ai/v1/files is not visible from pass-eu.wafer.ai. Re-upload to the EU edge if you need it there.
  • Metrics: the Serverless Metrics API and the dashboard /usage view aggregate per-region. To see EU traffic, query the EU host the same way you query the US host.
  • Request IDs: x-request-id values are unique per region.
Everything else — your account, your credits, your keys, your plan — is account-global and works identically against either edge.

​
Errors

If you hit a model that isn’t deployed in EU, you get the standard model_not_found with the live model list for the region: 
{
  "error": {
    "type": "invalid_request_error",
    "code": "model_not_found",
    "message": "Model 'Kimi-K2.6' is not available on pass-eu.wafer.ai. Available models: GLM-5.1, Qwen3.5-397B-A17B."
  }
}
See the Error Reference for the full envelope and SDK examples.