European AI products can no longer treat “we only store embeddings in Frankfurt” as enough when the search vendor still routes queries through Virginia. On November 13, 2026 Exa announced EU search: a second full stack in AWS Stockholm (eu-north-1) with the same main web index, on-GPU inference, and a dedicated https://api.eu.exa.ai endpoint. For builders shipping RAG agents under GDPR procurement reviews, that is the difference between a policy exception and a default integration.
This guide explains what Exa replicated, how region-locked keys fail closed, which APIs work on day one, and how the launch compares to other sovereign search moves we track in Europe AI landscape coverage.
TL;DR
| Item | Detail (Exa, Nov 13, 2026) |
|---|---|
| Region | AWS Stockholm eu-north-1 |
| Endpoint | api.eu.exa.ai |
| Keys | EU team keys work only on EU endpoint |
| APIs live | Search + Contents; auto and lite types |
| Fallback | Refuse request; no silent US route |
| Audit header | x-exa-processing-region: eu |
| Retention | EU teams default to zero request retention |
What Exa rebuilt (not just a proxy)
Exa’s post stresses “a true second home from the ground up.” Components running in-region include:
- Replicated web index maintained in real time across continents
- API routers, vector databases, rerankers, highlights on Exa-owned GPUs in Stockholm
- Contents cache served from EU copies, with live fetches via EU proxies
That is heavier than pinning DNS to a US backend. It also explains lead time: keeping petabyte-scale crawl indexes aligned is an engineering program, not a feature flag.
For agent builders comparing retrieval vendors, pair this with Perplexity locate extraction updates and Bedrock AgentCore web search APIs—each makes different residency promises.
Quality and latency claims
Exa published US-versus-EU tables on benchmarks including deep-search-qa, ATLAS, live-browsecomp, and finsearchcomp for both lite and auto modes. The vendor says no benchmark differed by more than three percentage points, while EU clients saved over 100ms versus hitting the US endpoint.
Treat vendor benchmarks as smoke tests, not your product eval. Run your own golden questions from production logs, especially if you mix financial or medical retrieval where a 2-point gap matters.
Fail-closed governance design
Three controls matter for security reviewers:
- Region-locked accounts — EU keys error on
api.exa.ai; US keys error onapi.eu.exa.ai. - No silent fallback — unsupported features return errors before metering, never served from another region.
- Response proof — every payload includes
x-exa-processing-region: eu.
Exa also says residency rules are enforced in code review with monitoring if EU data appears outside expected stores.
Document the caveat: account metadata and aggregated metrics may still live outside the EU. If your DPA forbids even admin identity abroad, read the enterprise agreement rather than the marketing page alone.
Getting started in Python
Exa’s sample client:
from exa_py import Exa
exa = Exa(api_key="YOUR_EU_KEY", base_url="https://api.eu.exa.ai")
results = exa.search("EU AI Act obligations for model providers", type="auto")
Provisioning requires an EU team from Exa sales; region is fixed at team creation. Plan environment separation in CI so staging keys never cross regions.
What is not in the EU yet
Day-one scope is Search and Contents with auto and lite. Agents, Websets, and Monitors remain US-only for now. Products that orchestrate multi-step research must either split architectures or wait for parity.
If you already run n8n personal agent sandboxes with Exa tools, verify which node version targets which base URL before compliance sign-off.
Why this matters for EU AI Act workflows
Procurement teams increasingly ask where prompts, snippets, and cached HTML live—not just where fine-tuning happens. A retrieval layer that silently egresses to the US breaks many internal data maps even when your LLM runs in Paris.
Exa’s move complements—but does not replace—choices like on-prem crawlers, open Metasearch, or sovereign cloud models we discuss in UK and Singapore landscape posts. It is specifically about neural web search APIs popular in coding agents and research bots.
Procurement questionnaire mapping
Security reviewers typically ask six questions Exa’s EU page now answers with product behavior rather than marketing slides:
| Reviewer question | Exa EU answer (Nov 13) |
|---|---|
| Where are queries processed? | AWS Stockholm eu-north-1 |
| Can data egress to US silently? | No; unsupported calls refuse before metering |
| How do we audit region? | Response header x-exa-processing-region: eu |
| Are API keys region scoped? | EU keys rejected on US host and vice versa |
| Is request content retained? | EU teams default to zero retention |
| What still leaves EU? | Account metadata and aggregated metrics (disclosed) |
Copy those rows into your vendor assessment; link Exa’s EU residency product page as evidence.
Benchmark tables: how to rerun them locally
Exa published paired lite and auto scores for deep-search-qa, ATLAS, live-browsecomp, and finsearchcomp. Before switching production traffic:
- Freeze a golden set of 200 prompts from your application logs (strip PII).
- Run each prompt against both
api.exa.aiandapi.eu.exa.aiin the same hour to control index drift. - Measure latency p50/p95 from your EU VPC, not from a US CI runner.
- Track downstream LLM cost—if EU quality dips on finance prompts, reranking changes may increase tokens.
The vendor’s “within three points” claim is an aggregate; your distribution may differ if you search niche regulatory sites crawled less often.
Architecture patterns for agent builders
Split clients by region. Store EXA_BASE_URL in config maps: EU microservices never mount US keys. CI pipelines that run in GitHub-hosted US runners should not integration-test EU residency unless they target api.eu.exa.ai intentionally.
Fail closed in code. Wrap the Exa SDK so a mis-set base URL throws at startup when EU_DEPLOYMENT=true. Exa refuses cross-region keys, but your own staging misconfigurations are still possible.
Hybrid RAG stacks. Many teams pair Exa with Bedrock Knowledge Bases or local indexes. Keep embeddings in-region even when web search moves to Stockholm—mixed residency stories confuse auditors.
Sovereign AI map illustrating EU-hosted Exa search data residency in Stockholm
Roadmap gaps to watch
Exa says Agents, Websets, and Monitors follow later. Products that chain search → excerpt → monitor must either stay US-only or split workflows. Document that limitation in your EU AI Act technical file until parity ships.
Comparison with other retrieval options in Europe
| Approach | Residency story | Trade-off |
|---|---|---|
| Exa EU endpoint | Vendor-operated Stockholm stack | Fast neural search, enterprise sales |
| Self-hosted crawlers plus local index | You own disks | High ops burden |
| Bing or Google APIs | US processing typical | Familiar relevance, unclear GDPR |
| Bedrock Knowledge Bases in eu-central-1 | AWS region locked | Needs your documents, not whole web |
| Open metasearch | Variable | Weaker semantic ranking |
Pick Exa EU when live web breadth matters and legal will sign a vendor DPA covering the disclosed metadata exceptions.
Monitoring and SRE practices
Alert if any production response lacks x-exa-processing-region: eu while using EU keys—that indicates misrouting worth paging. Log the header alongside trace IDs the same way you log model region for Gemini deployments.
Rotate EU keys through your secrets manager with region labels in the secret name (exa-eu-prod) so engineers do not paste US keys into EU Terraform modules during incident response.
Contents API and caching implications
Exa replicated content caches in EU, meaning page bodies retrieved through Contents should not round-trip through Virginia. Validate that your pipeline does not re-fetch US mirrors after search—some teams accidentally store URLs then pull HTML from origin servers in other jurisdictions.
Cost and contract negotiation tips
Enterprise EU teams often pay region premiums. Negotiate egress-free clauses for cross-border monitoring traffic if your observability stack sits in another region. Ask Exa whether Websets pricing will differ when those SKUs launch in EU.
Incident response playbooks
If legal requests data locality proof after an incident, collect:
- Redacted API logs showing
x-exa-processing-region: eu - Terraform or console screenshots proving EU team key IDs
- Contracts noting metadata exceptions
- Timestamps proving no US endpoint calls during the window in question
Store samples monthly so you are not reconstructing headers from sparse logging after a breach.
Developer experience details
EU provisioning still flows through sales-led EU team creation, not self-serve toggles. Plan two-week lead time in enterprise rollouts. Training materials should show both base URLs side by side; onboarding slides that only mention api.exa.ai set new hires up for compliance mistakes.
Exa’s November post also highlights zero data retention by default for EU teams. Confirm whether your account team enables retention for debugging—and document that choice in your privacy policy if end users’ queries could be stored.
Why Europe traffic pushed this launch
Exa writes that a significant portion of API traffic already comes from Europe, yet many customers could not send queries to a US service. That mirrors stories in our EU landscape coverage: procurement blocks US routing even when engineers prefer American latency. Stockholm is a compromise—same index quality target, shorter RTT for Berlin or Paris VPCs, contractual residency language procurement can sign.
FAQ alignment for your security packet
When security questionnaires ask “Is customer content processed in the EU?”, answer with the exact scope Exa documents: queries, returned results, and cached page contents stay in-region; account administration metadata may not. Link Exa’s product page and sample headers rather than paraphrasing from memory—questionnaires get archived for years.
If your application forwards Exa snippets to a US-hosted LLM, you still have a secondary transfer to document. EU search residency does not automatically EU-host the rest of your stack.
Related reading on explainx.ai
- Europe AI landscape and EU Act context
- California AI freeze lawsuit parallels
- Amazon Bedrock KB ACL patterns
- AgentCore web search API
- Perplexity Decider extraction
- Podqi risky shopping links in AI answers
Official: Exa EU residency blog, product page.
API scope and benchmark tables reflect Exa’s November 13, 2026 announcement.
