Search a Trip or a Move in One Place

Search a trip or a move means you compare flights, a stay, a car, and a home in one platform. You do not get a ticket. You do not get a day-by-day itinerary. You do not get an expense report.

This page is the Ktemia contract for that job: the same search in the UI, APIs, and copilot, AI search as the default use case, and a copilot that asks when a field is missing. The routes are not live yet. Nothing below is a captured fare, a live listing, or a booked car.

The flights HTTP job stays on the flight search API post. The agent job stays on flights MCP, skills, and instructions. This URL is the platform: trip or move, not a second flights tutorial.

Key Takeaways

• Booking Holdings’ 2025 10-K calls KAYAK meta-search: compare itineraries and prices, not the OTA that sells the room.
• Required fields still include origin, destination, and dates. The copilot asks. It does not guess.
• Free is $0: UI search for flights, stays, cars, and homes, plus 50 API requests a month.

What is search-and-compare for a trip or a move?

In its 2025 Form 10-K, Booking Holdings describes KAYAK as online meta-search: consumers search and compare travel itineraries and prices from hundreds of platforms at once. That is the compare job. It is not the Booking.com reservation job in the same filing. Search-and-compare for a trip or a move is that compare job, with a home on the table when the weekend becomes a relocation.

Ktemia’s terms say the same boundary in product language: search and compare flights, stays, cars, and homes for a trip, a move, or a relocation. Results come from third parties. Prices and availability can change. A search is not a reservation unless a separate booking flow says so.

Head terms ai travel planner and travel booking software are other SERPs. The first wants a Wednesday restaurant list. The second wants receipts and a PNR. This page is the missing middle: comparable options for getting there, staying, hiring, and living, without pretending we issued the ticket.

A citation you can lift: search-and-compare returns offers you can rank. It does not capture payment. KAYAK’s Search and discovery help states it is a travel search engine, not a ticket seller, and that you complete the reservation with the airline or OTA you pick.

How is this different from an AI travel planner?

On 14 January 2026, Google’s How to use Canvas in AI Mode for travel planning said Canvas builds a custom itinerary: flights and hotels plus daily restaurants, attractions, and more. That is an AI travel planner. Ktemia is not that product. We search and compare the pieces of a trip or a move. We do not draft your Saturday in Alfama.

The same cluster includes booking. On 27 August 2026, Google’s How to book travel with AI Mode added hotel booking in the chat, with the hotel or platform as merchant of record. On 6 May 2026, Mindtrip and Sabre announced in-chat flight booking on Sabre Mosaic with PayPal checkout. Those are agentic book stories. They are not this URL.

Layla’s public pitch is a day-by-day plan covering flights, hotels, activities, and dining. Fine for a vacation script. It does not answer “I need a fare, a month’s stay, a car at LIS, and listings if I stay.” That package is on AI search: flights, hotels, cars, and a place to live.

If the prompt is “plan me a week in Lisbon,” an itinerary model will happily invent a schedule. If the prompt is “LIS to LHR, 12 October, then a stay and a car,” Ktemia’s copilot needs those names. If any required field is missing, it asks. It does not fill LHR because you said “soon.”

How is this different from travel booking software?

SAP Concur’s expense product is travel and expense software: submit receipts, approve spend, reimburse employees, sync accounting. At Fusion 2026, SAP’s newsroom note described booking travel and filing reports from Microsoft 365. That is travel booking software and T&E for a travel manager. It is not search-and-compare for a person moving cities.

The commercial dump for travel management software and travel agency software is CRM, back office, and expense. Ktemia does not invoice a corporate card. It does not run agency accounting. A GDS or a hotel booking engine is that book-and-ops stack, unpacked on GDS vs booking engine vs a search API. Free is a dashboard, a small request cap, and UI search. See pricing.

Job	What you want	What you get	Typical buyer
Search / compare	Origin, dates, city	Rankable fares, rates, cars, listings	Traveler or builder
Itinerary / planner	“A week in Lisbon”	Day-by-day sights and meals	Vacation planner
Book / ticket	Offer plus pay	Order, PNR, confirmation	OTA, airline, TMC
T&E / management	Receipts and policy	Expense report, reimbursement	Finance / travel manager

If your tab is full of Concur alternatives, you are shopping a back office. If it is full of “best AI travel planner,” you are shopping a schedule. Neither tab is this page. Do not retitle the product to either keyword.

What can you search: flights, stays, cars, and a home?

As of 23 October 2026, pricing says Free includes search in the UI for flights, stays, cars, and homes. Those four verticals sit under AI search. You can take each piece alone, or put them together as a package for a trip or a relocation.

The worked query stays LIS → LHR, depart 2026-10-12. Same airports as the POST /v1/flights contract. For a stay, you still need a city and nights. For a car, a pick-up. For a home, a place you might live, not a Saturday tapas list. We will not paste invented TAP fares, hotel rates, or listing prices. When a route is live, this page gets a dated example.

On Free, 50 API requests a month is one shared pool across the four. One invented city on flights spends a call homes could have used. Cached edge responses, when they exist, are documented as not counting. That behaviour is not live. Do not build billing assumptions on it yet.

A weekend and a relocation share the same search. They do not share the same fields. A copilot that packages a home because you asked for a Friday fare is guessing. Guessing is out of contract.

How do the UI, the API, and the copilot share one search?

The product is three surfaces on the same compare job. The UI is search and compare without a second tool. APIs put that search in your product. The copilot is for when you would rather not assemble the query. Agents add MCP, skills, and instructions on Business. The dashboard watches usage.

Flights as HTTP is POST /v1/flights with origin, destination, and depart. Flights as an agent is the flights MCP at https://mcp.ktemia.com/mcp, with a skill that says ask if unclear. Stays, cars, and homes will follow the same rule when those routes exist: required fields, reject or ask, no invented city.

Do not expect the copilot to be laxer than the API. If the POST would fail, the chat should ask. That is already how the product describes the copilot.

Snippets are the same POST as the API article. Connectors (n8n, Zapier, Make) are workflows. Same no-origin-no-call rule. We are not documenting a live connector here.

Does the copilot book tickets or invent a city?

No, and no.

KAYAK’s help on Ask AI is blunt: you don’t book with Ask AI. You search and compare. (Search and discovery, retrieved 2026-09-18). Ktemia’s terms match: we do not sell the flight, the stay, the car, or the home unless a separate booking flow says so. This post is not that flow. The copilot is not live as a booking desk, and a successful search will still not be a ticket.

The ask-if-unclear rule is the other half. Pro includes 50 AI copilot credits. One credit is one copilot turn: a question, a package suggestion, or a drafted query. Unused credits reset with the billing period. That number is on pricing. Inventing LIS because the user said “Europe soon” spends a credit and, if it triggers an API call, a request on the wrong route.

Required for a flight search: origin, destination, depart. If any is missing, ask. Do not fill LHR. The same idea applies to a stay (city, nights), a car (pick-up), and a listing (where you might live). We will publish exact field names with each live route, not invent a hotels JSON here.

What plan includes which surface?

As of 23 October 2026, pricing publishes four monthly plans.

Free is $0: dashboard, 50 API requests a month, and search in the UI for flights, stays, cars, and homes. Pro is $29.99 a month: 20,000 API requests at 20 requests per second, 50 copilot credits, price tracking, and alerts. Business is $299: 250,000 requests at 250 per second, MCP servers and skills, workflow integrations. Enterprise is a call.

Every plan counts the same unit: a monthly pool shared across the four routes. The rate limit is the second cap — 20 calls a second on Pro, 250 on Business, however much monthly quota is left.

MCP servers sit on Business, not on Free or Pro. That is already in the flights MCP post. Do not invent a “unlimited AI travel agent” tier. Ktemia can change some plan prices when demand is high. Read the page you bill against.

Start with one search.

Search a trip or a move is one compare job across four pieces. It is not an itinerary generator, not a TMC, and not a booking API. The copilot asks. It does not guess. Caps live on pricing. Surfaces live on product. The default use case is AI search.

Flights as HTTP is the flight search API article. Flights as an agent is flights MCP. This page is the platform around them. Routes are not live. When they are, this URL gets dated examples, not a prettier fiction.