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 11 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. Ready means a connector is built and tested and goes live per destination; until a destination runs on it, and wherever a connector is only planned, we publish no attribution at all.
| Geography | Platform | Connector | Attribution as published | Live |
|---|---|---|---|---|
| FranceRegional tourism information system used by tourist offices in several French regions, Auvergne-Rhône-Alpes first among them | Apidae | Ready | — not claimed until the first destination runs on it | — |
| Austria | Österreich Werbung | Connected | Datenschnittstelle der Österreich Werbung | 10 |
| Belgium | Visit Flanders / Wallonie Tourisme | Planned | — not claimed until the connector is live | — |
| France | DATAtourisme | Connected | DATAtourisme, Licence Ouverte / Etalab | 233 |
| Italy — Emilia-Romagna | Emilia-Romagna Tourism | Connected | Emilia-Romagna Tourism – Regione Emilia-Romagna (CC-BY 4.0) | 10 |
| DenmarkOutdoor facilities and routes maintained by Denmark’s municipalities: shelters, beaches, campsites, viewpoints, walking, cycling and riding routes | GeoFA (udinaturen.dk) | Ready | — not claimed until the first destination runs on it | — |
| GermanyNuremberg, Munich and Freiburg only — other German destinations run on public sources | Open Data Germany | Connected | Open Data Germany | 3 |
| JapanKyoto Prefecture, Osaka City (Map Navi Osaka) and 14 wards and cities of Tokyo — other Japanese destinations run on public sources | Japanese local-government open data | Connected | Japanese local government open data (CC BY 4.0 / CC BY 2.1 JP), adapted by DM2find. Every record names its prefecture or city and dataset, e.g. Source: Kyoto Prefecture, 観光施設一覧 (CC BY 4.0), adapted by DM2find — in Japanese 出典:京都府「観光施設一覧」(CC BY 4.0)を加工して作成 | 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 | — |
| 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 |
Apidae · ready
Apidae: enrichment, not a second copy
Many French tourist offices maintain their offer in Apidae, and much of that offer also reaches DATAtourisme, which we already read. So the Apidae connector does not import a second copy of the same hotel. It matches each Apidae object to the DATAtourisme record it belongs to — by the producer's own ID first, by name and position only when that is unambiguous — and fills what that record leaves empty: contact details, photos, star ratings, accessibility, spoken languages, and clean English where the national translation chain has lost characters. Objects that never reach DATAtourisme become records of their own.
The connector is built and tested on Apidae's own demonstration project, and it goes live per office. You create an API project for DM2find with the selections you want published and share its key. We review a dry run with you — every record it would add or enrich, with nothing written — and from the next night it runs, after the DATAtourisme import. We only read from Apidae. A value DATAtourisme provides always stands, and every field Apidae fills is recorded, so it can be traced and reversed.
Data sources by country
Every concierge starts from the official open tourism data of its country or region. That covers all categories: sights, events, restaurants, accommodation and routes. The other columns add specialist data on top.
| Country / region | Official open dataAll categories | Guides & awardsRestaurants, hotels | EV chargingCharge points | Bathing waterQuality per site | RoutesWalking, cycling | MapBase map |
|---|---|---|---|---|---|---|
| France | DATAtourisme | Michelin, Gault&Millau | IRVE | EU bathing water | OpenStreetMap | OpenStreetMap |
| Netherlands | Touripedia | Michelin, Gault&Millau | NDW (DOT-NL) | EU bathing water | Wandelnet, OpenStreetMap | OpenStreetMap |
| Belgium | Open Data Flanders (Flanders, accommodation only) | Michelin, Gault&Millau | not connected | EU bathing water | OpenStreetMap | OpenStreetMap |
| Germany | Deutsche Zentrale für Tourismus | Michelin | Bundesnetzagentur | EU bathing water | not connected | OpenStreetMap |
| Austria | Österreich Werbung | Michelin | not connected | EU bathing water | not connected | OpenStreetMap |
| Italy — Emilia-Romagna | Emilia-Romagna Tourism | Michelin | not connected | EU bathing water | not connected | OpenStreetMap |
| Italy — South Tyrol | Open Data Hub Südtirol | Michelin | not connected | EU bathing water | not connected | OpenStreetMap |
| Finland | Visit Finland | Michelin | Fintraffic (Digitraffic) | EU bathing water | not connected | OpenStreetMap |
| Sweden | Visit Sweden | Michelin | not connected | EU bathing water | not connected | OpenStreetMap |
| South Korea | Korea Tourism Organization | Michelin | not connected | not connected | not connected | OpenStreetMap |
| Japan | Local-government open data (Tokyo, Osaka, Kyoto) | not connected | not connected | not connected | not connected | OpenStreetMap |
| Canada — Québec | Données Québec | Michelin | not connected | not connected | not connected | OpenStreetMap |
✓ connected and in use · — not (yet) connected. Guides and awards appear as recognitions (stars, toques) on the card. Map data © OpenStreetMap contributors.
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.
EU-first
European destination.
European AI.
For every destination in the EU this is the default, and 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, not the voice.
Every destination already runs on our own servers in Germany. For EU destinations, everything the question touches on its way to an answer stays in Europe as well — every link in the list, voice included. The international edition, with US AI and extras such as photo recognition, is available on request.
Try it on Strasbourg, with live DATAtourisme data — or on any EU destination →- 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
- VoiceGradium and Mistral Voxtral 3 speech recognition and voice, LiveKit on our own servers — no ElevenLabsEU endpoints, Germany — default for EU destinationsEU
Sovereignty
Built in the Netherlands, hosted on our own servers in Germany. For EU destinations the fully European chain — model, search, email and voice — is the default, with voice in more than 30 languages through Gradium and Mistral Voxtral 3. The international edition is available on request.
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
Restaurants — 30 systems
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.