For AI agents: a documentation index is available at https://docs.parallel.ai/llms.txt. The full text of all docs is at https://docs.parallel.ai/llms-full.txt. You may also fetch any page as Markdown by appending
European (EU) data residency lets you run the Search and Extract APIs in the European Union. When you send a request to .md to its URL or sending Accept: text/markdown.For Search and Extract, use /v1/search and /v1/extract for all new integrations and agent tool calls. Use /v1beta/search and /v1beta/extract only when maintaining an existing integration that already uses them. The request bodies changed too: on /v1/extract, full_content, fetch_policy and excerpt_settings go inside advanced_settings, and sending the v1beta top-level excerpts, full_content and fetch_policy to /v1/extract returns a 422. Do not substitute /v1 for the documented FindAll or Ingest endpoint paths.https://eu.parallel.ai, Parallel processes and serves it in the EU and doesn’t retain the request or response content. Only the base URL changes.
EU data residency is available through an enterprise agreement. It isn’t available on self-serve plans.
Who it’s for
Use the EU endpoint when your customers or vendor reviews require EU processing for web search and extraction. Two common cases:- You build AI applications for European customers who require EU data residency.
- You’re an EU enterprise or regulated organization, and your vendor review requires EU processing.
Get access
- Contact your Parallel account team or sales to add EU data residency to your enterprise agreement.
- Create or keep your existing API key. The EU endpoint accepts the same keys as
api.parallel.ai. (Note that it takes on average one hour for the EU endpoint to activate on fresh API keys.) - Set your client’s base URL to
https://eu.parallel.ai.
Set the base URL
Python SDK setup
Python
PARALLEL_BASE_URL environment variable to https://eu.parallel.ai instead of passing base_url.
For direct HTTP requests, replace https://api.parallel.ai with https://eu.parallel.ai. The x-api-key header stays the same.
Supported endpoints
Search
On the EU endpoint, Search works like this:modeis required and must be"basic". Requests with any other mode return an error.- Each request returns up to 20 results.
- Parallel answers the request from the EU search index. Search on the EU endpoint makes no live fetches.
Extract
On the EU endpoint, Extract works like this:- Each request accepts up to 20 URLs.
- To run cache-only, set
advanced_settings.fetch_policy.timeout_secondsto0. Extract then returns cached content only, and an uncached URL returns an error. - If you don’t set
timeout_secondsto0, Extract live-fetches uncached pages.
Extract looks up each URL in Parallel’s cache of public web pages, which Parallel hosts outside the EU. For that lookup, Parallel sends only the URL. Your objective and all processing stay in the EU. See What runs where.
What runs where
Extract cache lookups: Extract looks up each URL in Parallel’s cache of public web pages, which Parallel hosts outside the EU. Parallel sends only the URL, and under ZDR it doesn’t save it. The objective and all processing stay in the EU. Live fetch, which is on unless
timeout_seconds is 0, retrieves uncached public pages the same way.
Billing, metrics, and edge logs contain no request or response content.
Unsupported APIs and errors
The EU endpoint serves only the two endpoints above. It doesn’t serve these APIs:- Search with any mode other than
basic - Task API
- FindAll API
- Monitor API
- Chat API
- Responses API
- MCP servers
eu.parallel.ai return an error. Parallel never forwards them to the US. To use these APIs, send requests to api.parallel.ai, where they run in the US.