How the platform works.
Find and compare in the UI. Ship the same thing with APIs and docs. Ask the copilot when you would rather not assemble the query.
One search, reached three ways. A person types it into the dashboard. A product sends the same fields over HTTP. An agent asks the copilot or calls an MCP server. The required fields are identical in all three, so what works in the dashboard works in your code.
What Ktemia covers is search and comparison across flights, stays, cars, and property — for a trip or a move. Routes are not live yet, so read the examples below as the shape of the response rather than today's prices.
UI
Search, compare prices, hire a car, and find a stay or a home without opening a second tool.
APIs
Put the same search and compare in your own product. REST and GraphQL, same payload.
Docs
Reference, examples, and a path from the first call to production.
AI copilot
Ask for a trip, a move, or a fare in plain words. If the question is unclear, it asks you to elaborate rather than guessing.
Agents
MCP servers, skills, and instructions so an agent can search, compare, and act on the same platform.
Dashboard
Watch usage, raise rate limits, and run the UI, APIs, and copilot from one place.
Who it is for.
Use the UI if you are comparing a weekend or a relocation and you do not want four tabs. Use the APIs and docs if you are putting the same search inside a travel, moving, or listing product. Use the copilot when you would rather describe the trip than assemble the query. Free is free, with the dashboard and 50 API requests a month. Volume sits on pricing.
The four verticals are on use cases: flights, hotels, cars, and real estate. Package them, or take one. Connections into CRMs, warehouses, and automations sit on integrations.
If a required field is missing, the copilot asks for it and the API rejects the call by name. Neither picks a city or a date on your behalf — an incomplete search stays incomplete until you finish it.