Changelog · September 21, 2026
Keep AI processing in the EU, per organization
EU processing end to end, AI included, for teams whose data can't leave Europe.
By Roger Campos · Last updated: September 2026
TL;DR
Pages have always been fetched, rendered and stored in Europe. The language model behind /meta, /summarize and /keywords was the one step that could leave. An organization can now switch on EU data residency, which sends those calls only to providers processing inside the EU, with no fallback outside it — free, on every plan.
Free plan, no credit card. 1,000 credits a month.
Organization settings gained an EU data residency switch. With it on, the model calls behind the three AI endpoints are decrypted and processed inside the European Union and routed only to EU providers; there is no fallback outside it. Every other endpoint — /markdown included — calls no model at all, so it is processed in the EU whatever the setting.
Residency costs nothing extra and changes no prices. The same retention guarantees hold in both regions: model providers that neither log nor retain prompts and do not train on them.
Endpoints
The endpoints on this page
- Check a page's Open Graph tags and metadata
Paste a link and get the page's metadata — title, description, author, publication date, feed and main image — cleaned into one structured object.
Try it free - Summarize any web page with AI
Paste a link and get a concise AI summary of the page's main content — the substance, without the navigation, ads and boilerplate.
Try it free - Get the keywords from any URL
Paste a link to any website or article and get the 5–15 keywords and phrases that describe it best, ranked — for SEO briefs, tagging and content analysis.
Try it free
FAQ
Frequently asked questions
Which endpoints does EU residency affect?
Does EU residency cost more?
Is there a fallback outside the EU?
Try it on the free plan.
Free plan, no card. Confirm your email and your API key is live — you'll be making real requests in minutes.