Duffel Flights and Stays API vs FlightClaw

Duffel Flights and Stays API

Self-serve sign-up and test mode with no card or contract. No OpenAPI document, llms.txt or official MCP server.

FlightClaw

Hosted MCP at mcp.flightclaw.com/mcp with OAuth 2.1, PKCE and dynamic client registration, no API keys. Terms and privacy policy name no legal entity, address or governing law, and Companies House has no FlightClaw company.

Duffel Flights and Stays API

1. Send Duffel-Version: v2 on every request or you get a version error
2. Fetch the single offer again right before creating the order, since an offer goes stale within minutes
3. Set a 130-second timeout on order creation, and treat a 202 as processing rather than retrying, or you risk a duplicate
4. Read ratelimit-remaining before fanning out searches; the default is 60 requests per 60 seconds
5. Count offer requests. Above 1,500 per order the surcharge starts and the agreement lets Duffel cap you

FlightClaw

1. Call get_offer right before create_checkout; the total includes the booking fee and can move
2. Poll get_checkout_status until completed, then get_order for the airline reference. A sent link isn't a booking
3. Never ask for card numbers in chat. Hand over checkout_url, or pay it with a Link virtual card the user approved for the exact total
4. Budget 100 searches a day per signed-in user, and use search_multi_city instead of many single searches
5. Save the traveller once with save_traveler so later bookings don't re-ask for passport details