EU Data Residency
The full Mathpix API is available at https://eu.api.mathpix.com, a deployment hosted entirely
in the European Union for customers whose compliance or contractual requirements demand that
document data stays in the EU. Your existing API keys work as-is - change the base URL and nothing
else:
curl -X POST https://eu.api.mathpix.com/v3/text \
-H "app_id: YOUR_APP_ID" \
-H "app_key: YOUR_APP_KEY" \
-F "file=@document.jpg" \
-F 'options_json={"formats": ["text"]}'
All endpoint families are served: image OCR (/v3/text), PDF processing (/v3/pdf), conversions
(/v3/converter), and the async Files API (/files/v1/*), including
data sources.
What stays in the EU
Everything derived from your documents is processed and stored in EU data centers: document
processing compute, uploaded files, page images, conversion outputs, OCR results, document tracking
and job state, cropped images (served from eu-cdn.mathpix.com), and operational telemetry.
Only account metadata that is not derived from your documents, such as API key authentication and usage counts for billing, is handled by our global account infrastructure.
Results are queryable per region
Results live in the region that processed them: GET https://eu.api.mathpix.com/v3/ocr-results
lists documents processed through the EU endpoint, and the same call on api.mathpix.com lists
documents processed through the global endpoint. Result histories are never merged across regions -
your EU results have no path through US infrastructure, including at query time.
Console
The Mathpix Console works with both endpoints: the Playground and Results pages include a region selector, and usage and billing are shared - one account, one plan, one bill across both endpoints.
Data processing agreements
EU residency commitments can be incorporated into your Data Processing Agreement. Contact support@mathpix.com to set that up or to discuss migrating existing workloads.
The Privacy and Data Retention behaviors described in this section apply identically on the EU endpoint.