Every number on this site — population, property prices, tax-regime eligibility — is also published as data an AI assistant can read directly. Connect one, and you can skip the pages and just ask.
“What’s the going rate per square metre in Introdacqua, and does it qualify for the 7% pensioner tax regime?”
A connected assistant answers from real Agenzia delle Entrate and ISTAT figures, with the vintage and source attached — not a guess, and not a number it made up because it couldn’t find one.
Pick whichever matches what you use. No account, no login, no cost.
Add this address wherever your assistant lets you add a tool, connector or MCP server:
https://www.expatliving.it/api/v1/mcpPoint it at the API specification:
https://www.expatliving.it/api/v1/openapi.jsonPlenty of assistants — and the autonomous crawlers behind Perplexity, ChatGPT Search and Claude web browsing — don’t call a tool at all, they just fetch a page. llms.txt is the plain-text manifest they look for: what this site is, what data it holds, and where the API and MCP endpoints above actually live. Point yours at:
https://www.expatliving.it/llms.txtA good answer names its source and says how current it is — data as of 2026-08-09 for most of this site, and its own vintage for property prices and tax rules. If your assistant gives you a number with nothing behind it, ask it to check again; the source is always there to cite.
Where we genuinely don’t have a figure — a comune with no property market, say — a connected assistant should tell you that plainly rather than inventing one. What we hold and don’t hold is on the methodology page.
Tax-regime answers describe places, not people: a comune qualifying for a regime means it meets the geographic criteria, not that any particular person does. That’s not tax advice, and no assistant connected to this data can make it so.
Building something with this data yourself? The developer docs have the REST endpoints, the full OpenAPI spec, and a copy-paste MCP config.