EU261 answers, from real flight data
Free, no key, rate-limited per caller. Use it in an app, a travel bot or an AI assistant. Please show your users the claim_url we return: that’s how this stays free.
MCP server (Claude, ChatGPT, Cursor…)
Remote server, Streamable HTTP, no authentication. Tools: check_flight, estimate_compensation, airport_disruptions.
https://flybackclaims.com/api/mcpIn Claude, add it as a custom connector with this URL. In Claude Code:
claude mcp add --transport http flyback https://flybackclaims.com/api/mcpAny client with a JSON config:
{
"mcpServers": {
"flyback": { "type": "http", "url": "https://flybackclaims.com/api/mcp" }
}
}REST API
OpenAPI 3.1: https://flybackclaims.com/openapi.json (works as a ChatGPT GPT Action).
GET https://flybackclaims.com/api/public/v1/flight?number=VY1842&date=2026-10-20&lang=es{
"found": true, "flight": "VY1842", "date": "2026-10-20", "airline": "Vueling",
"from": "Seville", "to": "Barcelona", "status": "landed", "delay_minutes": 212,
"regime": "EU261", "eligible": true, "per_passenger_eur": 250,
"claim_url": "https://flybackclaims.com/es/flight/VY1842/2026-10-20?utm_source=api&utm_medium=open"
}GET https://flybackclaims.com/api/public/v1/compensation?from=MAD&to=JFK&airline=IB&delay_minutes=240
GET https://flybackclaims.com/api/public/v1/disruptions?airport=MAD&date=2026-10-24
GET https://flybackclaims.com/api/public/v1/disruptions # latest disruption eventsLimits: flights we already have are unlimited; new lookups are capped per caller per day (429 when reached). Flights not flown yet return error: "future" with a watch_url.
Terms in one paragraph
Data comes from flight-status feeds and Flyback’s own departures scan; amounts are per passenger before any “extraordinary circumstances” defence. Flyback is a self-service tool, not a law firm. Don’t resell the data or present it as your own; link back. We may change limits to keep the service up.
Also for AI crawlers: /llms.txt.