What the data licences mean for you
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:
license: the licence id, for exampleODbL,cc-by-4.0orCC0.license_url: a link to the licence text.attribution_required:trueif you must credit the source when you use the row.
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:
| Tag | Typical sources | Credit needed | Share-alike |
|---|---|---|---|
| CC0 | Wikidata | No | No |
| CC BY 4.0 | GeoNames and other open datasets; New Zealand SafeTravel advisories | Yes | No |
| ODbL | OpenStreetMap | Yes | Yes, for databases you share (section 3) |
| CC BY-SA | Wikipedia and Wikivoyage text | Yes | Yes, for text you share (section 4) |
| Apache 2.0, CDLA Permissive 2.0, MIT | Foursquare OS Places (section 7), other open place datasets and libraries | Yes | No |
| OGL (UK, v3.0) | UK government open data, including FCDO travel advice | Yes | No |
| Open Government Licence - Canada 2.0 | Global Affairs Canada's open dataset of travel advice | Yes | No |
| Licence Ouverte 2.0 (Etalab) | French government open data, including France Diplomatie travel advice | Yes | No |
| Public domain (US State Department) | US travel advisories | No (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.
| Issuer | Licence (id in the list) | Credit to show |
|---|---|---|
| Canada: the country-wide risk level from Global Affairs Canada's open dataset | Open 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 advice | Licence Ouverte 2.0 (etalab-2.0-fr-diplomatie) | Name the source, France Diplomatie, and the date the advice was last updated. |
| New Zealand: SafeTravel | CC 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 advice | Open 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 advisories | Public 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:
- Name OpenStreetMap and make clear the data is under the Open Database License. A link from the word "OpenStreetMap" to
openstreetmap.org/copyrightdoes this. "© OpenStreetMap contributors" is accepted wording. - On an interactive map, put the credit in a corner of the map. It may fade after a few seconds or after the user moves the map, as long as it can still be found, for example behind an info button or an About menu.
- In an app, a credit on the start-up screen is enough if the licence link is easy to find later, for example under a menu item called "Data licences".
- For search and routing results, the service and the app that uses it must credit OpenStreetMap, but each single result does not need its own credit.
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:
- A produced work: something made from the data that is not itself a database, such as a map image, a page of results, or an itinerary shown to a user. You may licence a produced work on any terms you like.
- A derivative database: a database built from the data, for example a table of OpenStreetMap rows you have stored, extended or merged.
Share-alike works like this:
- It applies when you make a derivative database available outside your organisation. That database must stay under the ODbL.
- It does not apply to showing results to your users, or to data you keep and use only inside your own organisation. Internal use carries no sharing obligation.
- If you publicly use a produced work that was made from a derivative database, the people who receive it can ask you for a copy of that derivative database under the ODbL.
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:
- Credit: name the source. Online, link back to the article the text came from. Offline, name the source.
- Share-alike: if you distribute the text, or an edited version of it, it must stay under the same licence, and you must say so.
- Commercial use is allowed when you meet both conditions.
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:
- Data licensed for non-commercial use only, such as academic datasets.
- Proprietary sources with no redistribution right and no commercial agreement.
- Content whose licence is still unclear or pending legal review.
- Internal-only data, which is not for redistribution.
- Rows with no licence tag. Since 14 November 2026 the row-level rule of the
data tables leaves out a row without one. The curated lists behind
/v1/hotels,/v1/restaurants,/v1/experiencesand the/v1/citieslist are not covered by that rule; on 14 November 2026 they held no row without a licence tag.
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
- OpenStreetMap Foundation, Licence and Legal FAQ (sections on produced works, share-alike and attribution).
- OpenStreetMap Foundation, Licence Community Guidelines, including the Produced Work guideline and the Attribution Guidelines.
- Wikivoyage, Copyleft.
- Foursquare, OS Places NOTICE.txt, and the Apache License, Version 2.0.
- Our API docs and the live registry at
/v1/licenses.
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.