Does JetSetGo have an API?

Yes. JetSetGo exposes its platform several ways: a Model Context Protocol (MCP) server purpose-built for AI agents, an OCTO-compatible distribution API for reseller connections, and REST and GraphQL access scoped to an operator's own tenant. Every interface reaches the same underlying booking, inventory and pricing engines — there is no second version of the operation.

Does JetSetGo support MCP (Model Context Protocol)?

Yes, through two MCP deployments. The Booking MCP gives customer-facing AI agents a booking-only toolset with hosted payment hand-off. The Operations & Configuration MCP gives operators' assistants governed access to routes, pricing, inventory, customers and configuration, with preview-and-confirm guarded writes. Both are documented in depth on this site.

Can an AI agent book trips directly through JetSetGo?

Yes. The Booking MCP is built exactly for that: authorised agents discover products, resolve the choices each trip requires, check availability, read live prices, create bookings and hand off payment to JetSetGo's hosted checkout. Card data never passes through the agent, and JetSetGo's booking engine validates every step.

What is OCTO compatibility?

OCTO is a standard API for tours and activities distribution. JetSetGo speaks OCTO Core strictly where interoperability matters, and offers namespaced, versioned extensions where an operation is richer than the standard can express — vehicles, rooms and cabins, multi-sector journeys, scoped questions and add-ons. Operators control which products each reseller connection sees.

Whose permissions apply when an AI assistant works inside JetSetGo?

The calling operator's own. Assistants act through the same permissions the operator has in the apps, within their own tenant. Consequential changes require the operator to review and approve an exact preview before anything is applied.

JetSetGo AI Integrations & APIs — MCP, OCTO, REST and GraphQL

JetSetGo is built to be called. Customer-facing agents, operator assistants, resellers and partner systems all reach the same authoritative engines — booking, inventory, pricing, fulfilment — through an interface designed for their job. There is one platform behind every surface: no shadow copy of the catalogue, no stale mirror of availability, no parallel booking path.

Four surfaces cover the integration landscape:

Surface	Who it's for	What it does
Booking MCP	Customer-facing AI agents, travel assistants, distribution partners	Complete agent booking journey: discover products, resolve trip choices, check availability, price, create bookings, manage changes, hosted payment hand-off
Operations & Configuration MCP	Operators' AI assistants (including Hubert) and authorised external clients	Governed working access to routes, pricing, inventory, bookings, customers, policies, communications, finance and configuration — preview-and-confirm on every write
OCTO-compatible distribution API	Resellers, OTAs, aggregators	Standard OCTO Core catalogue, availability, booking and lifecycle operations, plus versioned JetSetGo extensions for richer products
REST & GraphQL APIs	Operators and their own integrations	Direct programmatic access to tenant data — reporting, dashboards, custom portals and back-office automation

Booking MCP

The Booking MCP answers a question most booking platforms have not yet addressed: what happens when your customer is an AI agent? It gives authorised agents exactly the tools the job needs and nothing else — thirteen booking tools covering product discovery, progressive choice resolution (party details, vehicles, rooms, parking, add-ons), availability, live pricing, booking creation, contact updates, cancellation, and a hosted payment hand-off that keeps card data entirely out of the agent.

Every write follows preview-then-confirm semantics, credentials are scoped to one customer account or one partner integration, and the platform's own booking engine remains the sole authority on validation, availability and price.

Read the full Booking MCP documentation.

Operations & Configuration MCP

Inside the platform, Hubert — JetSetGo's built-in AI assistant — works through a governed tool layer spanning roughly three dozen capability modules and more than 400 tools: routes and scheduling, fares and pricing rules, capacity layouts and inventory allocation, customers, packages, policies, communications, ledger mappings and settings. Authorised external MCP clients connect to the identical layer.

The safety model is structural rather than advisory: every request runs with the calling operator's own identity and permissions, the tenant is pinned by the connection, and every consequential change returns an exact preview bound to a snapshot of current state — applied only after a human approves and nothing has drifted.

Read the full Operations & Configuration MCP documentation.

OCTO-compatible distribution API

For reseller connections, JetSetGo implements the OCTO standard — the catalogue, availability, booking and lifecycle operations that distribution partners expect — strictly and faithfully wherever a product fits OCTO Core. Where the real product is richer than the standard can express, clients can negotiate JetSetGo's namespaced, versioned extensions instead of flattening the product to fit: vehicle details and consumption, multi-sector journeys, rooms and cabins, multi-night stays, scoped questions, add-ons and product variations.

Operators stay in control throughout: they publish approved profiles for the products they want distributed, and every booking still runs through JetSetGo's normal pricing, inventory and fulfilment machinery.

Read the full OCTO distribution API documentation — base URL, authentication, the complete Strict Core flow with examples, error handling and retry safety.

REST & GraphQL APIs

Operators own their data and can build directly against it. GraphQL access is scoped to an operator's own tenant — the same data the apps render — supporting custom dashboards, reporting pipelines, kiosks and self-service portals. REST endpoints underpin booking flows and integrations. Access is provisioned per operator by JetSetGo; see the enterprise and API overview on the homepage for orientation, or contact us to discuss an integration.

Choosing the right surface

Building a customer-facing agent that sells trips? Use the Booking MCP.
Giving an operator's assistant or internal tool working access to run the business? Use the Operations & Configuration MCP.
Connecting resellers or OTAs to sell your catalogue? Use the OCTO-compatible distribution API.
Building your own dashboard, portal or report on top of your tenant? Use the REST and GraphQL APIs.

All four enforce the same boundary: callers work within the authority granted to them, and the platform's engines — not the caller — decide what is true.