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 10 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	Connected	Datenschnittstelle der Österreich Werbung	10
Belgium	Visit Flanders / Wallonie Tourisme	Planned	— not claimed until the connector is live	0
France	DATAtourisme	Connected	DATAtourisme, Licence Ouverte / Etalab	222
Italy — Emilia-Romagna	Emilia-Romagna Tourism	Connected	Emilia-Romagna Tourism – Regione Emilia-Romagna (CC-BY 4.0)	10
GermanyNuremberg, Munich and Freiburg only — other German destinations run on public sources	Open Data Germany	Connected	Open Data Germany	3
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
NetherlandsProvince of Groningen only — other Dutch destinations run on public sources	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.

The European option

European destination.
European AI.

An option per destination — and when it is on, it is complete. From the visitor's question to the answer, no American AI service handles it: not the model, not the web search, not the email.

Every destination already runs on our own servers in Germany. What the option changes is everything the question touches on its way to an answer. Choose it and every link in the list stays in Europe, with one exception you can switch off.

Strasbourg runs on it today — ask it something →

BuiltDM2findthe NetherlandsEU
HostingOur own servers — app, workflows and database, self-hostedGermanyEU
Language modelMistralParisEU
Web searchMistralParisEU
Event emailsScalewayParisEU
Tourism dataÖsterreich Werbung, DATAtourisme, Emilia-Romagna Tourism, Open Data Germany, Open Data Hub Südtirol, Touripedia, Visit Finland DataHub and Visit Sweden national APIEU open dataEU
VoiceElevenLabsNot European yet — can be switched off per destinationOptional

Sovereignty

Built in the Netherlands, hosted on our own servers in Germany. A fully European chain — model, search and email — is one switch per destination; voice is the only part that is not, and it can be switched off.

Non-exclusive

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

Rollout

Pilot three destinations, then extend nationally with per-DMO branding on one shared layer.

Booking systems

The ontology reaches past open data.

Open tourism data says a golf course exists. It cannot say whether Saturday at 08:40 is free — that lives in the club's own tee sheet and changes by the minute. We reach 15 tee-sheet systems and 30 restaurant reservation platforms, so a venue never changes software to work with us.

Golf — 15 systems

Lightspeed GolfTeeControlBRS GolfClubV1PC CADDIETeeOneIntoGolfGolfmanagerNexxchangeand 6 more

Restaurants — 30 systems

SevenRoomsResDiaryZenchefCoverManagerTableCheckFormitableGuestplanNappkinOpenTableTheForkHappyChefand 19 more

Live lookup

Green pills read availability directly. The visitor gives a date and a party size inside the conversation and gets an answer back.

Direct link

Grey pills — Golfmanager, Nexxchange, OpenTable, TheFork and HappyChef — hand over to the venue's own booking page instead. The answer is a button, not a time slot.

We never take the booking

No payment, no inventory held, no commission. We show what is free; the venue completes the reservation on its own system.

Which system do you use?

If it is not listed above, it is probably still one of the 45 we reach — and if it genuinely is not, tell us which one and we will say plainly whether we can.

The ontology layerunder your tourism data.