EU routing

cn2.ai enforces strict geographic routing for buyers in the European Union. EU requests are only served by EU-tagged keys — there is no fallback to global keys.

How it works

1. Every request is tagged with the buyer's country based on their IP address
2. If the buyer is in an EU member state, the request is routed exclusively to keys tagged with the EU region
3. If no EU keys are available for the requested provider, cn2.ai returns a 503 error with a clear explanation — it does not fall back to non-EU keys
4. Non-EU buyers are routed to the global key pool, which includes keys tagged US, APAC, and Global

For sellers

When listing a key, you choose a region tag:

Region tags cannot be changed after a key goes active. To change region, remove the key and re-add it with the new tag.

For buyers

EU routing is automatic — you do not need to do anything. If your IP address is in an EU member state, you are automatically routed to EU-tagged keys.

The marketplace shows an EU badge next to providers that have EU keys available. If you are browsing from the EU, the marketplace defaults to showing only EU-available providers.

If no EU keys are available for a provider, you receive:

HTTP 503
{
  "error": "No EU keys available for this provider",
  "code": "NO_EU_KEYS",
  "provider": "openai",
  "gdprNote": "Your request is from the EU. cn2.ai routes
               EU traffic to EU-tagged keys only."
}

EU member states

The following 27 countries are classified as EU for routing purposes:

Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden.

The UK (post-Brexit), Norway, Switzerland, and Iceland are not included. EEA extension may be added in the future based on demand.