We count page visits with Google Analytics to see which pages are read. Nothing is stored until you accept, and we never store search queries. Privacy.
Every change Wellknown observed on this MCP server, newest first, with what it was before and what it became. Tool-surface changes carry the definition diff. Nothing here is edited after the fact.
⟨445 unchanged words⟩ booking URL as verification of the displayed offer. Pass sellers=false when the traveler wants the price picture but is not booking through this answer: it skips the live seller-quote wave, so the ranked calendar fares, booking links and metadata.route_price_check still come back but metadata.seller_enrichment_status is `skipped` and no seller quote, seller-level baggage fee or direct seller action is resolved. Provider failure, unavailability, or a spend cap ⟨103 unchanged words⟩
55 words differ · removed · added
inputSchema
⟨262 unchanged words⟩ Ignored in anywhere mode.","examples":["2026-09-262026-09-29"],"title":"earliest","type":" ⟨105 unchanged words⟩ Ignored in anywhere mode.","examples":["2026-12-252026-12-28"],"title":"latest","type":"
Status
Recently observed → Live
TLS
Certificate recorded, valid to 2026-11-23
Authorization
Authorization not required
Status
Live → Recently observed
Tool surface
First tool surface recorded: 2 tools (server version 1.0.3)
","type":"boolean"},"sellers":{"default":true,"description":"Whether to run the live seller-quote wave (Google Flights `booking_options`) for this request. Default `true`: unchanged behavior — the bounded frontier resolves seller prices, baggage basis, and the executable booking action. Set `sellers=false` to ask for the ranked fare calendar and the route-level price check ONLY: the response then carries `metadata.seller_enrichment_status=\"skipped\"`, results keep their Travelpayouts-grounded prices and durable booking links, and no seller quote, seller-level baggage fee, or direct seller action is resolved. It exists for callers that want the price picture cheaply and do not intend to book — our own curve-seeding crons use it — because the seller wave is where a search's provider spend actually goes (about seven of its ~eight calls). Non-economy cabins have no calendar source, so `sellers=false` there leaves `metadata.route_price_check` as the only priced evidence and `results` may be empty.","examples":[true,false],"title":"sellers