For national & regional tourism organisations

The ontology layer
under your tourism data.

You have invested in a national data platform. The remaining gap is semantic: assistants, agents and search engines cannot reason over your records without a shared model of what a trail, an opening period or a tasting room actually is. That layer is what we operate — across 8 national and regional platforms today.

Connected platforms and licence attribution

Attribution is rendered wherever the licence requires it — on the destination page and in its machine-readable record. Where a connector is only planned, we publish no attribution at all.

Geography	Platform	Connector	Attribution as published	Live
Austria	Österreich Werbung	Planned	— not claimed until the connector is live	0
Belgium	Visit Flanders / Wallonie Tourisme	Planned	— not claimed until the connector is live	0
France	DATAtourisme	Connected	DATAtourisme, Licence Ouverte / Etalab	152
Italy — Emilia-Romagna	Emilia-Romagna Tourism	Connected	Emilia-Romagna Tourism – Regione Emilia-Romagna (CC-BY 4.0)	10
Germany	Open Data Germany	Planned	— not claimed until the connector is live	0
South Korea	KTO Tourism	Connected	KTO Tourism from data.go.kr	7
Canada — Québec	Données Québec	Connected	Données Québec – Gouvernement du Québec (CC-BY 4.0)	10
Spain	Datos Abiertos Turismo	Planned	— not claimed until the connector is live	0
Italy — Süd-Tirol	Open Data Hub Südtirol	Connected	Open Data Hub Südtirol/Alto Adige (opendatahub.com)	3
Netherlands	Touripedia	Connected	Touripedia	3
Finland	Visit Finland DataHub	Connected	Visit Finland – DataHub (business.finland.fi)	4
Sweden	Visit Sweden national API	Connected	Visit Sweden national API	2

Four things the layer does

Normalise: One entity model across every source, so a Finnish record and a Korean record answer the same question the same way.
Enrich: Live availability, ratings, classifications and accessibility — plus an owner-supplied overlay that never overwrites your record.
Expose: schema.org, JSON-LD, an MCP endpoint and llms.txt, so any assistant can cite your destinations correctly.
Govern: Licence terms, attribution and provenance carried through to the answer, per field.

A destination record, as published

GET /api/destinations/nancy.json

{
  "@context": "https://schema.org",
  "@type": "TouristDestination",
  "name": "Nancy",
  "source": {
    "platform": "DATAtourisme",
    "attribution": "DATAtourisme, Licence
                    Ouverte / Etalab",
    "refresh": "continuous"
  },
  "enrichmentLayer": { "affectsRanking": false },
  "agentEndpoint": "mcp://dm2find.ai/nancy"
}

Publishing this makes the infrastructure claim demonstrable — and positions your destinations to be cited by assistants rather than fighting for blue links.

Sovereignty

Built in the EU and hosted on our own European infrastructure, with an optional fully-European model stack from source to answer. The one exception is the optional voice agent, which runs on ElevenLabs in the US — it is never part of the data layer, and it only loads when a visitor starts it.

Non-exclusive

We sit beside your platform, not in front of it. Your data stays yours; attribution travels with it, per field.

Rollout