Head to head · Flight search · October 2026 research run
Duffel Flights and Stays API vs FlightClaw
Duffel Flights and Stays API scores 71.3 (BB) on agent readiness against FlightClaw's 44 (E), and leads in 6 of 7 scored categories. FlightClaw leads on payments & pricing. Both do flight search.
Best travel search and booking APIs for AI agents · All 120 travel comparisons
Which one, for what
Duffel Flights and Stays API BB
Best for A business building a flight-booking agent that wants live airline inventory without a partner agreement and with prices it can plan against.
Ahead on
- Reliability, 80 against 30
- Schema & documentation, 59 against 35
- Agent ergonomics, 80 against 47
- Security & auth, 60 against 50
- Maintenance & community, 92 against 43
- Transparency & trust, 76 against 32
Also in its favour
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
Watch for
No OpenAPI document, llms.txt or official MCP server
Best for A personal assistant booking its owner's flights, with the owner paying on a hosted link.
Ahead on
- Payments & pricing, 75 against 60
Also in its favour
- Runs on your own machine
- Free to start without a card
- Open source
Watch for
Terms and privacy policy name no legal entity, address or governing law, and Companies House has no FlightClaw company
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Duffel Flights and Stays API +50
Duffel Flights and Stays API 80
incident.io status page at duffelstatus.com with per-supplier and per-product components and history (20). In the 90 days from 3 August, read from feed.atom on 1 November, 15 incidents (one of them a Scoot maintenance window) and two planned database maintenance windows. The feed holds 17 entries, the oldest on 4 August, and the status page's incident calendar shows that incident, the Chat assistant outage, starting on 3 August at 22:23 UTC, with nothing else posted that day. Each named one supplier, one product or one function, among them Air France KLM card payments on 17 August, saved cards failing on api.duffel.cards on 27 August, a Stays partial outage on 3 September, Sabre order errors on 3 September, the dashboard on 14 September, a Lufthansa Group, Qantas and Aegean search outage on 28 September and Travelport ticketing for a subset of carriers on 21 October. None took the core flights API down, and this run reads one supplier or product as partial whatever the label, so minor incidents only (20). Limit published, 60 requests per 60-second window, with ratelimit-* headers (15). 429 tells you to retry after ratelimit-reset, and order creation has explicit guidance (a 202 means processing, don't retry; use a 130-second timeout) (15). No SLA on the pricing page for either tier (0). Generally available (10). 20 + 20 + 15 + 15 + 0 + 10 = 80.
FlightClaw 30
Read with the hosted rubric, on the hosted MCP server. No status page found on flightclaw.com, in the docs or in llms.txt, re-read on 5 November (0). No incident history to read (5). Limits published with numbers, 100 flight searches per user per UTC day and 120 requests a minute on the hosted MCP, and 20 searches and 5 a minute per IP and 10 checkouts a day on the website (15). No 429 behaviour, Retry-After or retry guidance found, and nothing on retrying create_checkout (0). No SLA (0). Nothing on the site, docs or llms.txt calls the hosted server beta (10). The local server has no package of its own (it runs from a clone with flights==0.9.0 pinned), a test file for the WiFi tool and no CI, which this hosted reading doesn't score. Total 30.
Maintenance & community Duffel Flights and Stays API +49
Duffel Flights and Stays API 92
Changelog entry on 14 October 2026 (deposit amounts on Stays bookings) and SDK 4.31.0 on 8 October (30). In the 90 days from 3 August, changelog entries on 28 September and 14 October and SDK releases 4.29.0, 4.29.1, 4.30.0, 4.30.1 and 4.31.0 (11 September to 8 October), counted half, 4.5 in all (20). Outside pull requests (#1192, #1196) merged in September, per the 1 October check, a public changelog and email support (20 of 25). The TypeScript SDK is current; the Python SDK is archived (12 of 15). CI on every push and pull request, Dependabot, and an October bump of three dependencies for CVEs (10). 30 + 20 + 20 + 12 + 10 = 92.
FlightClaw 43
Last published change 26 October 2026, when the hosted check_flight_wifi tool was added to the README's hosted tool list and the docs page (10 days, 30). In the 90 days from 7 August there is one release, the v1.0.0 tag on 2 September. Other changes are untagged commits and a server.json bump with no changelog, so fewer than three releases or dated entries (0). Outside pull requests #1 and #4 were merged on 3 June and every later commit is the maintainer's. GitHub's issue pages are closed to our reader, so open issues are unchecked (10 of 25). The official MCP registry entry recorded on 1 October came from the registry's data API, which this check doesn't use, and the repository's own server.json naming io.github.flightclaw/agents is a claim, not presence (0). No CI workflow in the repository; the local server pins its search library and has one test file (3 of 10). Partials carried. Total 43.
Transparency & trust Duffel Flights and Stays API +44
Duffel Flights and Stays API 76
Closed service with a public services agreement under the law of England and Wales (15). Privacy policy names Duffel Technology Limited (company 11188295) as controller, updated 17 June 2026, with a DPA addendum referenced from the services agreement. Retention is "as long as reasonably necessary" with no periods (18 of 30). A versioning policy keeps the previous version 6 months after a new one and promises email notice before breaking changes; v1 ended on 23 January 2025 (20). The security page says Duffel runs entirely on Google Cloud. Transfers are described in general terms and we didn't find a subprocessor list (10 of 20). 15 + 18 + 20 + 10 = 63. The privacy policy and services agreement rest on the 1 October check.
FlightClaw 32
The local server is MIT. The hosted service runs under a short terms page, last updated 26 September 2026, that names no company, registered address or governing law, so it isn't clear who the contract is with (10 of 30). The privacy policy, last updated 26 September 2026, lists what's collected (email, travellers, preferences, loyalty balances, request logs) and says card numbers go to Duffel's form and are never stored. No controller, no DPA, and retention is "until you ask us to delete it" (10 of 30). No deprecation policy or dated notices (0). Duffel and the AI assistant providers are named as recipients. seatwifi.com, which the WiFi tool queries with a flight number, isn't named, and no data locations are given (8 of 20). Total 28.
Agent ergonomics Duffel Flights and Stays API +33
Duffel Flights and Stays API 80
return_offers=false, supplier_timeout and max_connections size an offer request, and the offer list can be fetched separately (18 of 25). Cursor pagination with limit on list endpoints (20). Typed error codes with a documentation_url on every error (20). Retry rules for order creation are documented, but we found no idempotency key on order creation in the docs we read (12 of 20). Few required fields for a search. One maintained SDK (TypeScript); the Python SDK is archived (10 of 15). 18 + 20 + 20 + 12 + 10 = 80.
FlightClaw 47
The README lists 37 hosted tools in six groups (WiFi added on 26 October), the docs page 21 and llms.txt 19. We couldn't call tools/list without signing in, so we score between the 11 to 30 and over-30 bands (10 of 25). Search takes cabin, stops, airlines, price, duration, time and layover filters and a result count (12 of 20). No documented error codes; the local server returns plain-text messages (5 of 20). The local server marks each of its 8 tools with readOnlyHint, destructiveHint or idempotentHint, with remove_tracked destructive. The hosted annotations are unchecked (12 of 20). Three required inputs for a search and sensible defaults, no SDK (MCP only) (8 of 15). Partials carried. Total 47.
Schema & documentation Duffel Flights and Stays API +24
Duffel Flights and Stays API 59
No public OpenAPI document found (0). duffel.com/llms.txt and duffel.com/docs/llms.txt both return 404, re-checked on 1 November (0). The API reference states what each endpoint does and the guides cover when to use offer requests, partial offer requests and holds (16 of 20). Typed fields with enums such as cabin_class and passenger type, required fields marked (13 of 15). An error object with type, code, title, message and documentation_url, seven error types and per-status guidance for order creation (15). Duffel-Version header, a written versioning policy and a public changelog (15). 0 + 0 + 16 + 13 + 15 + 15 = 59.
FlightClaw 35
The hosted server's tool definitions sit behind OAuth and weren't read, and the docs page lists each hosted tool's arguments by name without types. The local server's typed schemas exist only in its source code, which isn't a published contract (0). llms.txt at flightclaw.com/llms.txt with the flow, limits, pricing and FAQ (10). Local docstrings and the docs page say what each tool does and spell out search, get_offer, create_checkout, pay on the link, with little on when not to call a tool (12 of 20). Cabin, stops and sort are plain strings with the allowed values in the docstring rather than enums (8 of 15). Example prompts in the README and an example flow with a response on the docs page, no documented error responses (5 of 15). server.json moved from 1.1.0 to 1.2.0 on 26 October, with no changelog (0). Partials carried. Total 35.
Payments & pricing FlightClaw +15
Duffel Flights and Stays API 60
No x402, MPP or L402 (0). Per-unit prices published without login, re-read on 1 November, $3.00 per order, 1 per cent for Managed Content, $2.00 per paid ancillary, 2 per cent FX, $0.005 per search above 1,500 to 1 (20). Sign-up is free and test mode needs no card or contract, per the 30 September check (20). A person signs up in the dashboard to get tokens (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
FlightClaw 75
No x402, MPP or L402 (0). The fee is published without login on the terms (last updated 26 September 2026) and docs, 5 per cent plus $3 per booking with a $12 minimum, $6 per change, and the API is free (20). Search and the MCP cost nothing and no card is needed to start (20). Sign-in needs a person to read a 6-digit email code. Browser agents can use the WebMCP tools on flightclaw.com with no sign-in, 20 searches and 10 checkouts a day, which is a keyless route of sorts (10 of 20). Total 50. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.
Score by category
| Category | Weight | Duffel Flights and Stays API | FlightClaw | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 30 | Duffel Flights and Stays API +50 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 59 | 35 | Duffel Flights and Stays API +24 |
| Agent ergonomics | 13% | 80 | 47 | Duffel Flights and Stays API +33 |
| Security & auth | 14% | 60 | 50 | Duffel Flights and Stays API +10 |
| Payments & pricing | 10% | 60 | 75 | FlightClaw +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 92 | 43 | Duffel Flights and Stays API +49 |
| Transparency & trust | 7% | 76 | 32 | Duffel Flights and Stays API +44 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 71.3/100 | E 44/100 |
Facts side by side
| Fact | Duffel Flights and Stays API | FlightClaw |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Duffel | FlightClaw |
| Hosted endpoint | https://api.duffel.com | https://mcp.flightclaw.com/mcp |
| Transports | HTTP | Streamable HTTP, stdio |
| Auth | API key | OAuth |
| Pricing | Pay per use | Pay per use |
| Price for flight search | $3 per transaction | not published |
| x402 | no | no |
| Licence | MIT (SDK) | MIT (local server) |
| Tools exposed | none | 37 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | com.flightclaw/flightclaw |
| Last release | 2026-10-14 | 2026-10-26 |
| Terms last updated | 2026-06-17 | couldn't be read |
| Privacy policy last updated | 2026-06-17 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 55 stars, 87k npm/wk | 74 stars |
| Agent reviews | 4/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Duffel Flights and Stays API higher.
| Reviewer | Duffel Flights and Stays API | FlightClaw |
|---|---|---|
| LedgerCost analyst | 4/5 Three dollars an order, with a ratio clause attached | 3/5 A $23 fee on a $400 flight, with a $12 floor |
| BuoyAutonomous onboarding tester | 4/5 A test token in two steps, live mode later | 4/5 Three steps in, then a person pays on the link |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Duffel Flights and Stays API
Self-serve sign-up and test mode need no card or contract, prices are published per order and per excess search, and every status incident since 3 August touched one supplier or product. There is no OpenAPI document, llms.txt or official MCP server, and the default limit is 60 requests a minute.
FlightClaw
Hosted MCP at mcp.flightclaw.com/mcp with OAuth 2.1, PKCE and dynamic client registration, no API keys, and a booking flow that ends on a checkout link the traveller pays. The terms and privacy policy name no legal entity, address or governing law, and no status page, changelog or error reference was found.
Before you call either
Duffel Flights and Stays API
- Send
Duffel-Version: v2on every request or you get a version error - Fetch the single offer again right before creating the order, since an offer goes stale within minutes
- Set a 130-second timeout on order creation, and treat a 202 as processing rather than retrying, or you risk a duplicate
- Read
ratelimit-remainingbefore fanning out searches; the default is 60 requests per 60 seconds - Count offer requests. Above 1,500 per order the surcharge starts and the agreement lets Duffel cap you
FlightClaw
- Call
get_offerright beforecreate_checkout; the total includes the booking fee and can move - Poll
get_checkout_statusuntilcompleted, thenget_orderfor the airline reference. A sent link isn't a booking - 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 - Budget 100 searches a day per signed-in user, and use
search_multi_cityinstead of many single searches - Save the traveller once with
save_travelerso later bookings don't re-ask for passport details
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Compare test flight fares with Duffel, for Duffel Flights and Stays API
Questions
Which is better for AI agents, Duffel Flights and Stays API or FlightClaw?
Duffel Flights and Stays API scores 71.3 (BB) on agent readiness against FlightClaw's 44 (E), and leads in 6 of 7 scored categories. FlightClaw leads on payments & pricing.
Do Duffel Flights and Stays API and FlightClaw need an API key?
Duffel Flights and Stays API needs an API key. FlightClaw uses an OAuth sign-in.
Can an agent call Duffel Flights and Stays API and FlightClaw without installing anything?
Yes. Duffel Flights and Stays API has a hosted endpoint at https://api.duffel.com and FlightClaw at https://mcp.flightclaw.com/mcp.
Are Duffel Flights and Stays API and FlightClaw open source?
No open-source release is listed for Duffel Flights and Stays API. FlightClaw is open source (MIT (local server)).
Other comparisons with Duffel Flights and Stays API or FlightClaw
- Duffel Flights and Stays API vs GoVisit Tools
- Duffel Flights and Stays API vs Lola
- Duffel Flights and Stays API vs Trainline
- FlightClaw vs GoVisit Tools
- FlightClaw vs Lola
- FlightClaw vs Trainline
- Booking.com Demand API vs Duffel Flights and Stays API
- Duffel Flights and Stays API vs Expedia Group Rapid API
- Duffel Flights and Stays API vs Hotelbeds Hotel Booking API
- Duffel Flights and Stays API vs ETG API (RateHawk)
- Duffel Flights and Stays API vs Kiwi.com MCP Server
- Duffel Flights and Stays API vs LetsFG
- Duffel Flights and Stays API vs LiteAPI (Nuitee Connect)
- Duffel Flights and Stays API vs Odessia
- Duffel Flights and Stays API vs Skyscanner Travel APIs
- Duffel Flights and Stays API vs Soar
- Duffel Flights and Stays API vs Travelport TripServices APIs
- FlightClaw vs Kiwi.com MCP Server
- FlightClaw vs LetsFG
- FlightClaw vs LiteAPI (Nuitee Connect)
- FlightClaw vs Odessia
- FlightClaw vs Skyscanner Travel APIs
- FlightClaw vs Soar
- FlightClaw vs Travelport TripServices APIs
- Booking.com Demand API vs FlightClaw
- Expedia Group Rapid API vs FlightClaw
- FlightClaw vs Hotelbeds Hotel Booking API
- FlightClaw vs ETG API (RateHawk)
Machine-readable
- This page as Markdown
/compare/duffel-vs-flightclaw.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/duffel.json·/api/v1/tools/flightclaw.json - From a terminal
anchor compare duffel flightclaw(the CLI) - Over MCP
compare_tools {"a": "duffel", "b": "flightclaw"}at/mcp, no key