EU region

Point your clients at the EU hosts

AgentMail runs a separate deployment in the EU that serves the same API on its own hosts:

Every endpoint path, parameter, and response shape is identical across regions, so everything else in these docs applies unchanged.

API keys carry their region in the prefix, am_eu_ for EU keys and am_us_ for US keys. Here is how each surface targets the EU region:

# once for the session
export AGENTMAIL_BASE_URL="https://api.agentmail.eu"
agentmail inboxes list

# or per command
agentmail --base-url "https://api.agentmail.eu" inboxes list

Region selection works differently on each surface:

• The TypeScript client reads the key’s prefix and picks the region itself, so the no-argument constructor works in either region. Pass environment only when you want to pin it.
• The Python client takes the region through environment, and the option covers WebSocket connections too, so EU_PROD points both at the EU hosts.
• The Go SDK reads the same AGENTMAIL_BASE_URL variable as the CLI.

A key authenticates only in its own region.

Keep your data in the EU

The EU deployment runs on its own infrastructure, where mail that moves through it is processed and stored along with your inboxes, drafts, webhooks, and API keys.

The region is a property of your organization:

• An organization lives in exactly one region, and all of its data stays in that region’s deployment.
• Every API key the organization issues starts with its region’s prefix, which is how a key can tell your client where to connect.

The EU region is part of enterprise agreements. Contact support@agentmail.cc to set up an organization there.

Next Steps