Getting started

Ktemia is a search and compare platform for a trip or a move. You can use the dashboard, put the same job in your own product with APIs, or ask the copilot. You do not get a ticket. You do not get an itinerary. You do not get a booked car or a signed lease.

This page is the path into the docs. The HTTP contract for fares sits on the flights API note. How the copilot and the API treat missing fields sits on required fields. Product surfaces sit on product. Caps sit on pricing.

What you can search

Four routes share one platform:

• Flights: origin, destination, and a depart date.
• Stays: city, check-in, check-out, and guests.
• Cars: pick-up place and dates.
• Homes: place and the constraints you name for a listing.

Take one route, or package them. Use cases is the umbrella. Each vertical has its own page.

Three ways to run the same job

UI. Open search in the dashboard. Fill the required fields. Compare the rows. Free includes UI search on every route.

APIs. POST the same fields the UI would send. One request counts as one API request. On Free, the cap is 50 requests a month as one shared pool. Pro raises that to 20,000 a month at 20 requests per second, and Business to 250,000 at 250 per second. Cached responses at the edge do not count.

Copilot. Say the job in plain language. If a required field is missing, it asks. It does not invent Lisbon because you said soon. One copilot turn is one AI credit.

The three surfaces must not disagree. If the copilot asks, the API must reject. If the UI requires origin, the POST body requires origin.

What is not live yet

Routes are not live. Examples in these docs are the contract we will accept, not captured fares, live hotel rates, fleet prices, or asking prices. Do not paste a dashboard key into frontend JavaScript. Do not treat a successful example as a ticket.

When a route is live, this page will say so. Until then, use the docs to learn the job, the fields, and the boundary between search and booking.

Do not paste a dashboard key into frontend JavaScript. Do not treat a 200 from a mock as a ticket. Free includes UI search on every route and 50 API requests a month. Those numbers live on pricing. If a required field is missing, read required fields before you retry.

Next

1. Read required fields so you do not guess a city or a day.
2. Read the flights API if you are wiring POST /v1/flights.
3. Open use cases for the four verticals, or getting started from the blog for the platform story.