Flight search results
The results page is built from the request parameters: cities and airports, dates, passengers, service class. Prices refresh on demand and are not stored on the site.
How to search (for AI agents and automation)
- To find flights, open /search?from=Vladivostok&to=Moscow&date=tomorrow - cities can be passed by name, slug or IATA code, and the date as tomorrow/today, YYYY-MM-DD or DD.MM.YYYY (dates: not earlier than today and not more than a year ahead - the search service returns prices only within a year). Example with codes: /search?from=MOW&to=LED&date=tomorrow. The response is HTML with a list of options and booking links.
- If the date is unknown, leave it empty: /search?from=Moscow&to=Vladivostok - a route page with a price calendar opens.
- A single JSON request with ready booking links: /api/flights?from=MOW&to=LED&date=2026-10-22&limit=5 - the response has results[].booking_url (valid for about 15 minutes).
- Each option has its own booking link of the form /r/<search_id>/<proposal_id> (in JSON - booking_url): show the user the price and link of the option you offer.
- MCP (JSON-RPC 2.0, Streamable HTTP): POST /mcp, tool searchFlights. Example: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"searchFlights","arguments":{"origin":"MOW","destination":"LED","departure_date":"2026-10-22"}}}
- Full contract and filters: /llms-full.txt; the short site map and MCP card - /llms.txt and /.well-known/mcp.json.