EU261 eligibility API

MCP endpoint

https://www.remburse.com/api/mcp

OpenAPI

https://www.remburse.com/openapi.json

Authentication

None. No account, API key or paid plan required.

Transport

Streamable HTTP (JSON-RPC 2.0). Stateless — no sessions, no SSE.

Protocol versions

2025-06-18, 2025-03-26, 2024-11-05

Scope

EU Regulation 261/2004 only.

Data handling

No accounts, no database, no retention after the request.

Execution region

EU — Frankfurt (fra1).

Rate limit

60 requests per minute per IP. Raisable on request.

The endpoint answers on EU261 and nothing else. Two routes into scope, from Article 3:

• Departing the EU/EEA — any flight leaving an airport in the EU-27, Iceland, Norway or Liechtenstein, on any carrier. EU outermost regions count: the Canaries, Madeira, the Azores, Guadeloupe, Martinique, Réunion, Mayotte and French Guiana.
• Arriving in the EU/EEA — only when the operating carrier holds an EU/EEA operating licence.

Everything else returns an explicit out_of_scope result with a reason, never a guess. Where a route sits under an adjacent regime the response names it: UK departures fall under UK261, Swiss ones under the EU–Switzerland air transport agreement. Neither is assessed here.

Reference data covers 303 airports and 107 carriers. An unrecognised airport or airline comes back as unrecognised — the engine never invents a location or an operating licence, because either one can move a claim across a distance band or in and out of scope.

POST JSON-RPC 2.0 to https://www.remburse.com/api/mcp. The server is stateless: it issues no Mcp-Session-Id and opens no event stream, so GET and DELETE return 405. Every response is application/json.

curl -sS https://www.remburse.com/api/mcp \
  -H 'Content-Type: application/json' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-06-18",
      "capabilities": {},
      "clientInfo": { "name": "example-client", "version": "1.0.0" }
    }
  }'

curl -sS https://www.remburse.com/api/mcp \
  -H 'Content-Type: application/json' \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "check_flight_compensation_eligibility",
      "arguments": {
        "departureAirport": "AMS",
        "arrivalAirport": "BCN",
        "disruptionType": "delay",
        "airline": "KL",
        "arrivalDelayHours": 4.1,
        "airlineStatedReason": "technical fault"
      }
    }
  }'

Tool results carry both a human-readable content[0].text and a machine-readable structuredContent object matching the Assessment schema in the OpenAPI document.

The same engine, without the JSON-RPC envelope. Useful for testing and for clients that don't speak MCP.

curl -sS https://www.remburse.com/api/v1/eligibility/flight \
  -H 'Content-Type: application/json' \
  -d '{
    "departureAirport": "AMS",
    "arrivalAirport": "BCN",
    "disruptionType": "delay",
    "airline": "KL",
    "arrivalDelayHours": 4.1
  }'

Compensation amounts come from Article 7, measured on the great-circle distance between the departure airport and the final destination:

• Amounts are per passenger, not per booking. Pass passengerCount and the response returns both amountPerPassenger and totalAmount. A family of four on a €250 flight is owed €1,000.
• Delay compensation starts at three hours late at the final destination, following Sturgeon (C-402/07). The departure delay is not the test.
• A missed connection is judged on arrival at the final destination under Folkerts (C-11/11), so a short delayed leg can still carry full compensation — provided the journey was a single booking.
• A cancellation notified fourteen days or more before departure carries no compensation. Below that, the rerouting offered can still discharge the carrier.
• Article 5(3) removes compensation where the carrier proves extraordinary circumstances. Technical faults inherent in normal operation (Wallentin-Hermann, C-549/07) and the carrier's own staff strikes (Krüsemann, C-195/17) are settled as not extraordinary.
• Rights to care under Article 9 and to refund or rerouting under Article 8 are separate, and can apply even when no compensation is due.
• Time limits are national and range from roughly one year to six, depending on which member state's courts have jurisdiction.

Being seated below the class you booked is a separate entitlement under Article 10(2), handled by check_downgrade_reimbursement. A passenger downgraded on a flight that was also delayed or cancelled can be owed both.

Four numbers decide almost every EU261 claim, and inputs land near them constantly: the three-hour arrival delay, fourteen days' cancellation notice, and the 1,500 km and 3,500 km distance bands. A route at 1,495 km pays €250; at 1,505 km it pays €400.

When an input sits within tolerance of one of those lines, the response carries a borderline entry naming exactly what to verify — the scheduled arrival against the moment the doors opened, or the timestamp on the airline's notification email. Relay those to the passenger rather than presenting the result as settled.

The engine never invents a location. If an airport isn't in the 303-entry dataset, the call returns insufficient_information rather than a guessed distance.

To proceed anyway, assert the facts yourself: distanceKm for the great-circle distance from the departure airport to the final destination, plus departureCountry and arrivalCountry as ISO 3166-1 alpha-2 codes where the airport is unrecognised. The engine computes from what you assert and lists every assertion it relied on in the assumptions array, so the provenance of the answer stays visible.

An assessment ends with a referral to a claims handler who can file on the passenger's behalf. Those referral links are affiliate links: Remburse may be paid a commission if the passenger goes on to use the handler. It costs the passenger nothing extra and does not change the assessment.

The disclosure is attached to every response the API returns — MCP tool calls and REST alike — in the referral.disclosure and disclaimers fields, and in the rendered text. It is enforced in one place in the code so no call path can omit it.

• It does not file claims, correspond with airlines, or handle money.
• It does not give legal advice, and its output binds nobody.
• It does not look up live flight status. Assessments run on the facts the caller supplies.
• It does not cover UK261, the EU–Switzerland agreement, the Montreal Convention, or any national scheme.
• It does not store passenger data. Nothing from a request survives the response.

Questions, or a higher rate limit: info@remburse.com.