# Flait — flight deal intelligence for nomads & their agents **Live board:** https://flait-agent-production.up.railway.app Not another flight-search wrapper. Flait watches prices 24/7 on nomad corridors (US/EU ↔ Latin America, US/EU ↔ Southeast Asia, and the hops between) and builds the price history needed to answer the question every traveler — and every booking agent — actually has: **"is this price good for this route?"** ``` GET /v1/score?origin=LAX&destination=BKK&price_usd=430 → {"verdict":"good","pct_vs_typical":24.2,"typical_price_usd":567,"days_of_history":11,...} ``` History can't be scraped retroactively. Every day the collector runs, the oracle gets harder to replicate — and more useful to you. ## Connect your agent (30 seconds) **Remote MCP endpoint** (Claude, Hermes, OpenClaw, anything MCP): ``` https://flait-agent-production.up.railway.app/mcp/ ``` Claude Desktop / Claude Code: ```json {"mcpServers": {"flait": {"type": "http", "url": "https://flait-agent-production.up.railway.app/mcp/"}}} ``` **READ tools (free):** `is_good_deal` · `find_deals` · `route_history` **ACT tools (guarded):** `set_watch` — your agent creates a standing watch on ANY route (watching a route starts price collection on it), optionally armed to **auto-book when the price hits**, with the user's spend cap enforced · `watch_status` — poll a watch and its bookings with the key `set_watch` returns. > **Writes are guarded.** Auto-booking never fires silently: the human always gets a > "booking in 30 minutes" email with a stop button first, spend is hard-capped at their > number, and one watch books at most one flight. Your agent can also register a > `webhook_url` and receive signed lifecycle events: > `hit` / `booking_scheduled` / `booked` / `booking_failed` / `booking_stopped`. > (Booking is in beta test mode — no real charges.) Per-platform setup (Hermes config, OpenClaw, example agent missions): see **[AGENTS.md](AGENTS.md)**. ## REST API Full OpenAPI schema at [`/openapi.json`](https://flait-agent-production.up.railway.app/openapi.json) — agent-readable by design. | Endpoint | What it answers | |---|---| | `GET /v1/score?origin=&destination=&price_usd=` | Is this price good? (the oracle) | | `GET /v1/deals` | Best current deals vs each route's typical price | | `GET /v1/history/{origin}/{destination}` | Daily price history for a route | | `POST /v1/intents` | Set a watch (mandate fields = auto-book; `webhook_url` = agent callbacks) | | `GET /v1/watch/status?k=` | Watch + booking status for a status_key | ## Humans welcome too The [deal board](https://flait-agent-production.up.railway.app) shows the same intelligence visually — and you can set a standing watch ("BKK under $450") and get an email the moment it hits. ## Honest notes - Verdicts are backed by our own collected history. Routes without ≥3 days of data return `"verdict": "unknown"` — we don't guess. - Prices come from cached airline-search data: great for deal intelligence, always verify the live fare at booking. - Free during beta. Be reasonable (≤1 req/sec). Building on Flait? Say hi — high-volume keys and webhooks are coming. --- Built in public by one human + [Claude](https://www.anthropic.com).