Regions

Run requests in the EU: the EU base URL, the region setting, and what EU requests cost.

Eevo runs requests in two regions: global and the EU. A request that runs in the EU is processed on Eevo's servers in the EU only, and is never sent to another region.

The EU is available once your organization has bought credit, or has credit on its balance. On free decisions alone, a request for the EU answers 402 insufficient_credit and the EU settings cannot be chosen: add credit on Billing in the console.

Choose the EU per request

Call the API on https://eu.eevo.io instead of https://eevo.io. Everything else stays the same: paths, keys, bodies and answers. For example, https://eu.eevo.io/api/v1/decisions.

Choose a region for your organization

On Data controls in the Eevo console, an admin chooses where your organization's requests run: from the API, the API playground and connectors (Claude, ChatGPT and other MCP clients) alike.

Under Only EU, a request that asks for another region is refused with 400 invalid_request.

Decisions you ask for by email, billed to your organization, follow the setting like the API playground: Eevo's own model calls run in the region the setting picks. The email assistant's other steps, reading your email and writing the reply, do not run in a chosen region.

Pricing

A request that runs in the EU by the table above, through the EU base URL or the region setting, costs $2.75 per 1M input tokens instead of $2.50, in both modes (Models, pricing and limits).

When the EU is busy

A request for the EU waits for the EU's servers and is never answered from another region. If none can take it, it answers 503 region_unavailable with a Retry-After header; nothing is charged. Retry after the Retry-After seconds.