What the data licences mean for you

Last updated: 14 November 2026, when section 4 was made precise, section 2 said what an empty advisory level means, section 6 said which rows the licence rule covers, section 7 (Foursquare OS Places) was added and the licence counts in section 1 were read again. On 13 November 2026 we checked the licence table in section 1, the advisory sources in section 2 and the not-cleared groups in section 6 against the live licence list. The other sections were last changed on 11 November 2026.
This page is a plain-language summary, not legal advice. The licence texts themselves decide what you may do. If your use case is unusual, or a large part of your product depends on one source, read the licence and talk to your own lawyer. Questions for us go to [email protected] or the contact page.

TravelMindsAI is assembled from open and licensed sources. Each row keeps the licence of the source it came from, and the data endpoints below tell you which one. This page explains what that means when you build on the data.

1. Which licence tags a response carries, and where to see them

On the data endpoints (for example /v1/cities, /v1/pois, /v1/hotels, /v1/restaurants, /v1/visa, /v1/unesco, /v1/circuits and /v1/heritage/in) each row has three fields:

Point-of-interest, hotel, restaurant and visa rows also carry source, the upstream dataset the row came from.

The travel-advisory tool (POST /v1/agent/tool/get_travel_advisories) names the licence of each row and also returns the credits you must show, in attribution_lines (see section 2).

The full list of licence ids is public at GET https://api.travelminds.ai/v1/licenses (no key needed). Each entry has license_id, full_name, url, commercial_use_ok, attribution_required, share_alike and notes. GET /v1/licenses/audit shows the licence position of each endpoint. On 14 November 2026 the list had 50 entries, 41 of them cleared for commercial use.

The tags you are most likely to see include:

TagTypical sourcesCredit neededShare-alike
CC0WikidataNoNo
CC BY 4.0GeoNames and other open datasets; New Zealand SafeTravel advisoriesYesNo
ODbLOpenStreetMapYesYes, for databases you share (section 3)
CC BY-SAWikipedia and Wikivoyage textYesYes, for text you share (section 4)
Apache 2.0, CDLA Permissive 2.0, MITFoursquare OS Places (section 7), other open place datasets and librariesYesNo
OGL (UK, v3.0)UK government open data, including FCDO travel adviceYesNo
Open Government Licence - Canada 2.0Global Affairs Canada's open dataset of travel adviceYesNo
Licence Ouverte 2.0 (Etalab)French government open data, including France Diplomatie travel adviceYesNo
Public domain (US State Department)US travel advisoriesNo (a credit is welcome)No

The live list at /v1/licenses is the authority. If a tag in a response is not explained there, ask us.

2. What you must credit, and where

When attribution_required is true, credit the source wherever people see the data in your product. For travel advisories, show the strings in attribution_lines as they are. These credits come from the data's own licences, so they apply on every plan.

Government travel advisories

Advisories are served from five governments. Each row carries its licence id, and each answer carries the exact credit line in attribution_lines. Each row also carries the issuer's level in level (1 to 4). The level can be empty (null, with level_label "level not stated"): that means the issuer's page states no level, never that a place is safe.

IssuerLicence (id in the list)Credit to show
Canada: the country-wide risk level from Global Affairs Canada's open datasetOpen Government Licence - Canada 2.0 (ogl-canada-2.0-gac)Name the licence with a link to it, and the source: Global Affairs Canada, Country Travel Advice and Advisories.
France: France Diplomatie travel adviceLicence Ouverte 2.0 (etalab-2.0-fr-diplomatie)Name the source, France Diplomatie, and the date the advice was last updated.
New Zealand: SafeTravelCC BY 4.0 (cc-by-4.0-nz-mfat)Name the Ministry of Foreign Affairs and Trade, SafeTravel, in writing, and the licence.
United Kingdom: FCDO travel adviceOpen Government Licence v3.0 (ogl-uk-3.0)Say that the advice contains public sector information licensed under the Open Government Licence v3.0.
United States: State Department travel advisoriesPublic domain (public-domain-us-state-dept)Not required (public domain). The source welcomes a credit: Bureau of Consular Affairs, U.S. Department of State.

Logos, crests, photos and other third-party material are not covered by these licences; the advisory rows hold text only. Do not suggest that a government endorses your product.

For OpenStreetMap data, the OpenStreetMap Foundation's guidance says:

For CC BY 4.0 rows, name the source and the licence, for example "GeoNames, CC BY 4.0". For other licences, use the license_url on the row, and ask us if the right wording is unclear.

The pricing page also asks Free-plan users to show attribution on public deployments. Ask us if you are unsure what that requires for your product.

3. What "share-alike" means for OpenStreetMap data (ODbL)

The OpenStreetMap Foundation separates two things you might make from ODbL data:

Share-alike works like this:

So if you call our API and show the answers in your app, share-alike is not triggered. If you copy many OpenStreetMap-tagged rows into your own dataset and then publish or sell that dataset, it is. Our own reading, recorded in our licence registry, is that an API response is a produced work.

4. Text licensed CC BY-SA (for example Wikivoyage)

Some text comes from Wikivoyage or Wikipedia, which publish their text under Creative Commons Attribution-ShareAlike. This is stricter than the ODbL case, because the share-alike covers the text itself:

The trip-planner tools supply CC BY-SA content only to Enterprise customers who opt in to it. The data routes can return CC BY-SA rows on any plan, and every such row carries its licence tag: /v1/narratives/{city_id} (Wikipedia extracts tagged CC-BY-SA-3.0, Wikivoyage extracts tagged CC-BY-SA-3.0 or CC-BY-SA-4.0), /v1/restaurants (Wikivoyage entries, CC-BY-SA-3.0), and /v1/heritage/in and the nearby-heritage list of /v1/cities/{city_id}/context (ASI monument records, CC-BY-SA-4.0). To leave them out, drop the rows whose licence is CC-BY-SA-3.0 or CC-BY-SA-4.0. /v1/licenses lists these ids in lower case (cc-by-sa-3.0, cc-by-sa-4.0), so compare the ids without regard to case.

5. How to keep only the licences you are comfortable with

Our licence registry marks which licences allow commercial use, and the data endpoints are built to leave out rows that do not. Check the license tag on each row yourself as well.

There is no query parameter that filters by licence today. To narrow results further, read the license field on each row and drop the tags you do not want. Build your list of acceptable tags from /v1/licenses, which tells you for each tag whether commercial use is allowed, whether credit is needed and whether share-alike applies. For example, in Python:

import httpx, os

key = os.environ["TMAI_API_KEY"]
registry = httpx.get("https://api.travelminds.ai/v1/licenses", timeout=30).json()

# keep licences without share-alike
ok = {r["license_id"].lower() for r in registry if not r["share_alike"]}

pois = httpx.get(
    "https://api.travelminds.ai/v1/pois",
    params={"iso_alpha2": "IN", "limit": 50},
    headers={"Authorization": f"Bearer {key}"},
    timeout=30,
).json()

kept = [p for p in pois if (p.get("license") or "").lower() in ok]

If you need a licence filter applied on our side, for example for bulk deliveries, ask us.

6. What the registry marks as not for commercial use

Our licence registry marks these groups as not cleared for commercial use. The public list at /v1/licenses shows each licence and its status:

Some of TravelMindsAI's own data products, tagged tmai_internal, are served on paid plans only.

7. Foursquare OS Places

Places, hotels, restaurants and experiences with source Foursquare come from the Foursquare OS Places dataset under the Apache License, Version 2.0 (licence tag Apache-2.0). Foursquare asks that an API serving the data carries its notice in the developer documentation. Foursquare's notice, in full:

© 2026 Foursquare Labs, Inc. All rights reserved.

The Foursquare OS Places dataset (the "Data") is licensed under the Apache License, Version 2.0 (the "License"). You may not use, modify, or distribute the Data except in compliance with the License.

As set forth more fully in the License, if you use, modify, or distribute the Data, you must:
– provide recipients with a copy of the License.
– if applicable, include prominent notices to the extent you've changed the Data.
– preserve attribution to Foursquare, including preserving the full content of this NOTICE.txt file.

To ensure appropriate attribution to Foursquare, we recommend the following:
– if using/distributing the Data in flat file form as-is or after making changes/modifications: include this NOTICE.txt file, which may be modified to include an additional notice of your changes/modifications, if any.
– if using/distributing the Data in API form as-is or after making changes/modifications: include a copy of the content from this NOTICE.txt file prominently in your developer documentation for such API, which may be modified to include an additional notice of your changes/modifications, if any.

You may obtain a copy of the License at: http://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing, the Data distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

See the License for the specific language governing permissions and limitations under the License.

Notice of changes. TravelMindsAI has changed the Data. It is filtered, matched to TravelMindsAI cities and served in TravelMindsAI's own fields; it is not served as Foursquare published it. Places in /v1/pois are refreshed from Foursquare's monthly releases: a place a release removes is marked removed, with the date the release was applied, and a place a release merges into another is marked merged, with the place it now points to; /v1/pois does not serve either.

The License: https://www.apache.org/licenses/LICENSE-2.0.

8. Sources for this page

9. Contact

For any licence question, write to [email protected] or use the contact page. Tell us the endpoint, the licence tag and how you plan to use the data, and we will answer in plain words.