Skip to content
ApiqDevelopers
API v1.64.0Open console

Fly for Agents

One URL. Your agent onboards, searches and books. Claude, Cursor or any MCP client can search, price and hold travel, read orders and trip data, and prepare bookings that a person on your team approves. The tools are generated from the same contract as the REST API, so they behave the same way.

Preview: the hosted MCP endpoint is not open to customers yet. Use these pages to plan your integration.

How an agent reaches the platformYour agent connects to the MCP server and picks one of four toolsets; the platform answers. A booking or cancellation goes to a person on your team, who approves it in the console before the platform acts.Your agentClaude · Cursor · your owntools/callMCP serverone door per toolsetOnboarding tools/mcp/publicTravel tools/mcp/publicConsole tools/mcp/consoleSupplier tools/mcp/supplierDining partner tools/mcp/partnerPlatformsearch · price · ordersa booking requestA person approvesin your console, then it runs

Three lights: what an agent may do on its own

Every tool carries one of three lights. The platform enforces the light, whatever the agent is asked to do.

  • Needs a personBooking, cancelling or paying files a request. Nothing happens until someone on your team approves it in the console.2 tools and resources
  • Change, if allowedHolds and other changes that move no money run only where your account lets agents make them.17 tools and resources
  • Read onlySearching, pricing and reading orders never change anything. Call them freely.123 tools and resources

The booking journey, stop by stop

From what your account sells to finding a booking again, its travel documents and a cancellation. Each tool answers with the reference the next one takes as an argument: the offerRef from a search is what you check, hold and book, the request's proposalId is what you watch, and the orderRef is what you find, read, collect documents for and cancel. A cancellation is a request a person approves, like the booking. Select a stop to open its reference.

The booking journey: each tool hands the next one its argumentdomainWhat you sellv1_capabilitiesdomainofferRefSearchsearch_tripsquery*offerRefComparecompare_offersofferRefs*offerRefRulesv1_rulesdomain*message*offerRefHoldhold_offerofferRef*proposalIdRequestbook_offerofferRef*travelers*orderRefApprovein the consoleorderRefWatchget_proposal_statusproposalId*orderRefFind bookingsv1_orders_searchdomain*message*orderRefTrip statusget_trip_statusorderReforderRefDocumentslist_order_documentsorderRef*Cancelcancel_with_quoteorderRef*Arguments under each stop · * required · between stops, the reference passed on

Explore every tool and its arguments

Search by tool, by what it does or by an argument name. The inspector shows the signature and every argument with its type, and builds a ready-to-send call.

146 matches

book_offer

Needs a person's approvalTravel tools · /mcp/public

Get a live price, then file a request to book the offer at that price. A person on your team approves it before anything is booked.

Files a request. Nothing is booked, cancelled or paid until a person on your team approves it in the console.

Tool signaturebook_offer(
  offerRef*: string,
  travelers*: array of traveler,
  requiredInfoAnswers?: object,
  paymentRef?: string,
  domain?: string,
  clientReference?: string
)
// * required   ? optional

Arguments

  • offerRefrequired
    string The offer, as search_trips or v1_search returned it.
  • travelersrequired
    array of traveler The people travelling, one entry each.
    traveler: 5 fields
    • firstNamerequired
      string First name, as on the travel document.
    • lastNamerequired
      string Last name, as on the travel document.
    • emailoptional
      string Email address for the booking's messages.
    • typeoptional
      string Adult (ADT), child (CHD) or infant (INF); ADT | CHD | INF.
    • dateOfBirthoptional
      string (date) Date of birth; needed for children and infants.
  • requiredInfoAnswersoptional
    object Answers to the questions the offer's requiredInfo asks, keyed as it names them.
  • paymentRefoptional
    string Pre-created payment intent.
  • domainoptional
    string Optional when the offer came from search_trips.
  • clientReferenceoptional
    string Your own reference for the booking, kept on the order.

Build the call

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "book_offer",
    "arguments": {
      "offerRef": "OF-H-7f3a9c",
      "travelers": [
        {
          "firstName": "Ada",
          "lastName": "Example",
          "type": "ADT"
        }
      ]
    }
  }
}
Open in the Travel tools reference

In your AI tool

Add the travel tools to the AI tool you already use. Each setup is the one its vendor documents, checked against their documentation; the pictures beside them are illustrations, not screenshots.

Set it up in Claude Code

Setup checked against the vendor's documentation, sign-in included.

In a terminal
claude mcp add --transport http travel \
  https://YOUR-MCP-HOST/mcp/public \
  --header "Authorization: Bearer $YOUR_MCP_TOKEN"
  1. Run the command in your project, with the token in YOUR_MCP_TOKEN.
  2. Start Claude Code and type /mcp: travel lists its tools.

Claude Code documentation · checked on 2026-10-29

Claude CodeIllustration
Illustration of Claude Code, not a screenshot: asking for 2 nights in Lisbon calls the travel tools' search_trips, which only reads.

setup confirmed sign-in with a key unconfirmed MCP support unconfirmed

Toolsets

Each toolset has its own endpoint, except the onboarding tools, which share the travel tools' endpoint and key. An agent connected to one endpoint cannot see or call the tools of another.

Onboarding tools

Take your account from sign-up to live: who the platform thinks you are, your go-live checklist, the integration checks your sandbox traffic has covered, and your API keys. These tools are served on the same endpoint, with the same key, as the travel tools.

Endpoint
/mcp/public
Sign-in
An API key for agents, from your console.
2 tools
4 resources
  • get_activationYour account's go-live checklist. Each step, its state and what is still needed.
  • get_certificationThe integration checks observed from your sandbox traffic.
  • get_meWho the platform thinks you are. Your account, site and permissions.
  • resolve_agentThe public profile of one agent by handle.
Coming soon (4)
  • list_api_keysYour account's API keys. Never a secret.
  • mint_api_keyCreate a scoped API key. The secret is shown once, in the answer.
  • onboardWhere your account is on the way to going live, and the next step to take.
  • revoke_api_keyRevoke an API key immediately.
Onboarding tools reference

Travel tools

Search, price and hold travel across every product your account sells, read orders and trip data, and file booking requests that a person on your team approves. This is the toolset most agents need.

Endpoint
/mcp/public
Sign-in
An API key for agents, from your console.
44 tools
  • book_offer needs a person's approvalGet a live price, then file a request to book the offer at that price. A person on your team approves it before anything is booked.
  • cancel_with_quote needs a person's approvalQuote the cancellation penalty, then file a request to cancel at that penalty. A person on your team approves it before anything is cancelled.
  • compare_offersCompare up to five offers side by side. Details, conditions and rules.
  • create_enquiry change, if allowedSend an enquiry to a supplier that takes leads only, such as private dining. Nothing is priced, held or booked.
  • create_upload change, if allowedGet a one-time upload slot for a file a booking asks for, such as a travel document.
  • extend_hold change, if allowedAsk for more time on an active hold, where the supplier allows it.
  • flight_returnsThe second step of a round-trip flight search. List the return flights for a chosen outbound, or choose one.
  • get_carbon_summaryYour account's emissions and carbon saved over a period.
  • get_entry_requirementsThe documents a traveller needs between two countries. It is guidance, not an eligibility decision.
  • get_flight_amenitiesCabin amenities of a flight, with confidence.
  • get_flight_emissionsCO2 emissions per passenger for flights, and typical emissions for routes.
  • get_flight_ratingsOn-time statistics for a flight number or a route.
  • get_flight_statusOperational status of a flight, one record per operated leg.
  • get_flight_trackThe flown track of a flight, one record per operated leg that has taken off.
  • get_holidaysPublic holidays and long weekends for a country.
  • get_proposal_statusFollow a booking or cancellation request until a person approves or rejects it, and read the outcome.
  • get_route_estimatesDoor-to-door time and distance per leg, or an origins × destinations matrix.
  • get_schedulesDeparture, sailing and showtime calendars.
  • get_seatmapThe seat, berth, cabin or table map of an offer.
  • get_trip_statusThe state of an order and each of its items, by order reference or by your own reference.
  • get_weatherCurrent, forecast or historical weather at a place.
  • hold_offer change, if allowedGet a live price, then hold the offer for free where the supplier allows it. Holds that need a deposit are refused.
  • list_ancillariesThe extras you can add to an offer before booking.
  • list_enquiriesYour enquiries, newest first.
  • list_eventsReplay the events your webhooks may have missed.
  • list_order_eventsAn order's timeline, its events oldest first.
  • list_wallet_transactionsYour wallet's movements, newest first.
  • list_webhook_deliveriesThe delivery log of one webhook subscription, with every attempt.
  • regenerate_order_documents change, if allowedRegenerate an order's documents, such as vouchers and invoices.
  • search_tripsSearch any product your account sells, from a plain-language query or structured fields. Waits for slower searches to finish.
  • simulate_rule_setPrice sample offers against a draft or published markup rule set, without changing any price.
  • sync_contentSync the static content catalogue, with a feed of what changed.
  • v1_capabilitiesWhat your account can sell, product by product, and which steps each supports.
  • v1_detailFull details of one offer or product.
  • v1_hold change, if allowedReserve an offer without paying, where the supplier allows it.
  • v1_lookupSearch reference data, such as places and codes.
  • v1_lookup_recordOne reference record, by its id.
  • v1_orders_cancel_quotePreview the cancellation penalty of a booking before cancelling.
  • v1_orders_getOne order and the state of each of its items.
  • v1_orders_searchFind orders by your own reference, traveller, date, product or state.
  • v1_repriceA firm, live price for an offer. Always fresh, never cached.
  • v1_rulesFare rules, cancellation policy and terms for an offer, before you book.
  • v1_searchStart a search for any product your account sells.
  • v1_search_pollPoll, page and filter the results of a search that is still running.
11 resources
Travel tools reference

Console tools

Your team's back office: queues, reports, team, webhooks, pricing rules and supplier data. An agent you connect here acts as you, with your current permissions and never more.

Endpoint
/mcp/console
Sign-in
You sign in as yourself (OAuth 2.1). You approve the agent in your browser and choose what it may read.
Availability
Sandbox only for now.
34 tools
13 resources
Console tools reference

Supplier tools

For suppliers selling through the platform: the bookings routed to you, your performance, statements, contract and integration health. An agent you connect here acts as you and can only read.

Endpoint
/mcp/supplier
Sign-in
You sign in as yourself (OAuth 2.1). You approve the agent in your browser and choose what it may read.
Availability
Sandbox only for now.
9 tools
14 resources
Supplier tools reference

Dining partner tools

For restaurant partners: the directory, reservations, point-of-sale data and reviews of the restaurants you have linked. Every tool here reads; nothing changes or books.

Endpoint
/mcp/partner
Sign-in
A dining partner API key.
Availability
Sandbox only for now.
6 tools
5 resources
Dining partner tools reference

Money needs a human

Reads are open to agents. Changes that move no money run only where your account allows them. Booking and cancelling are only ever requests: a person on your team sees the amount and approves it in the console, and an agent can never approve its own request.

Every page is also listed for agents and crawlers in llms.txt