About TourScanner AI

TourScanner AI is an infrastructure and catalog of tours, tickets and experiences built for AI agents. Through a REST API or a remote MCP server, an agent can search 1M+ tours and tickets from 14 providers, check live availability, and book safely.

With the introduction of tourscanner.ai, we want AI agents to do the hard work of travel. We see a future where an agent knows what is on wherever a traveller goes: which tours run, which tickets are left, which experiences fit the trip. It books them safely, and the traveller stays in charge.

People remember a trip for what they did there: the tour, the show, the boat trip at sunset. We want all of it to be easy for an agent to find, check and book.

The team

The people who build and run TourScanner day to day.

How it started

AI agents are becoming the way travel gets planned and booked. They already search, compare and plan for travellers, and they are starting to book. We think the travel products that win next will be built for agents first.

Tours and experiences are the hard part. Every provider keeps its own catalog, and prices and availability change by date, time slot, ticket type and group size. An agent cannot guess its way through that. It needs one catalog it can trust and a safe way to act on it.

We have worked on this problem since 2018. tourscanner.com compares tours and activities across providers for travellers. tourscanner.ai brings that catalog to agents, and we built it for them from the start.

What we build

tourscanner.ai is the tours and activities layer for AI agents. One REST API and one remote MCP server give an agent 1M+ tours, tickets, activities and experiences from 14 providers, with live availability and booking. The AI agent on our homepage runs on the same tools.

The catalog covers 5,000+ cities and 7,800+ attractions in 8 languages. It includes skip-the-line tickets, guided and private tours, walking tours, day trips, food tours, boat tours and cruises, cooking classes, shows, theme parks and hop-on hop-off buses. Agents can filter by tour type and by features like free cancellation, instant confirmation and mobile tickets.

We build around what we believe agents need.

Agents need data, not web pages
Booking sites are built for people to click through. An agent needs one catalog it can query. Every tour from every provider comes back with the same fields, and the docs are written for agents as well as people.
Agents need facts they can trust
If an agent says the 10:00 tour still has space, it has to be true. Times and prices for a date come from a live check, and we check the slot again before a checkout link is made.
Agents need a safety net
Calls fail, and agents try again. A retry must never book twice, so booking requests accept an idempotency key. Tools say whether they only read or can change something, and errors say whether a retry can work.

Learn more