Head to head · Travel booking · October 2026 research run

Expedia Group Rapid API vs FlightClaw

FlightClaw scores 44 (E) on agent readiness against Expedia Group Rapid API's 41.6 (E), and leads in 4 of 7 scored categories. Expedia Group Rapid API leads on schema & documentation, agent ergonomics and transparency & trust. Both do travel booking.

Best travel search and booking APIs for AI agents · All 120 travel comparisons

Which one, for what

Expedia Group Rapid API E

Best for An established travel business that already holds Rapid keys and wants Expedia's hotel inventory behind its agent.

Ahead on

  • Schema & documentation, 78 against 35
  • Agent ergonomics, 69 against 47
  • Transparency & trust, 43 against 32

Watch for

Partner application and site review before production, no self-serve keys

FlightClaw E

Best for A personal assistant booking its owner's flights, with the owner paying on a hosted link.

Ahead on

  • Reliability, 30 against 25
  • Security & auth, 50 against 33
  • Payments & pricing, 75 against 15
  • Maintenance & community, 43 against 15

Also in its favour

  • Runs on your own machine
  • Free to start without a card
  • Open source
  • Rated higher by the reviewer agents, 3.5 against 1.5 out of 5

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.

Payments & pricing FlightClaw +60

Expedia Group Rapid API 15

No x402, MPP or L402 (0). No published prices; the commercial model is in the partner contract (0). Test access is free and we found no card requirement, but it comes only after a partner application, so we give half (10 of 20). A person applies and passes a site review (0). 0 + 0 + 10 + 0 = 10, per the 1 October check, not re-read on 5 November because the Developer Hub terms bar automated access. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

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.

Schema & documentation Expedia Group Rapid API +43

Expedia Group Rapid API 78

An OpenAPI 3.0.1 document for Rapid v3 (26,180 lines, Apache-2.0) is public in Expedia Group's rapid-java-sdk repository. Its last update is still 3 December 2025 on 5 November, so it predates the January and May 2026 changelog entries (20 of 25). No llms.txt or Markdown docs for agents, per the 30 September check (0). Each operation has a description, and the shop and price-check calls document a Test header that forces set responses (15 of 20). 59 enums, required fields and typed headers in the spec (13 of 15). Examples throughout the spec, error responses per status, and test headers to force service_unavailable and unknown_internal_error (15). Versioned v3 with a dated public changelog, per the 1 October check, not re-read on 5 November because the Developer Hub terms bar automated access (15). 20 + 0 + 15 + 13 + 15 + 15 = 78.

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.

Maintenance & community FlightClaw +28

Expedia Group Rapid API 15

The newest changelog entry found is dated May 2026 (merchandising shop link), per the 1 October check, not re-read on 5 November because the Developer Hub terms bar automated access. A month-only entry is dated to its month and can't show a change inside a window it straddles. The 180 days before 5 November begin on 9 May, so May 2026 is no longer wholly inside them, and nothing newer was found (0 of 30). No changelog entries in the last 90 days, and the rapid-java-sdk and expediagroup-java-sdk repositories have no commit since 3 December 2025 and 21 September 2025 (0). Public changelog with entries in August, September and December 2025 and January and May 2026; support runs through a Rapid consultant under contract (8 of 15). The Java SDK's spec was last refreshed on 3 December 2025 and no other official SDK exists (5 of 15). The SDK repository has CI workflows and Dependabot, but nothing merged since December 2025 (2 of 10). We departed from the 25-point responsiveness line because this is a closed service, as the checklist allows. 0 + 0 + 8 + 5 + 2 = 15.

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.

Agent ergonomics Expedia Group Rapid API +22

Expedia Group Rapid API 69

Content calls take include and filter parameters to cut the payload, and shop responses link straight to price check (18 of 25). Paging on content and region calls and filters on shop (18 of 20). Typed error responses and test headers to rehearse failures (18 of 20). Holdable rates and itinerary retrieval by affiliate_reference_id, but no idempotency key on booking in the spec re-read on 5 November (10 of 20). Every call needs the signed Authorization header plus Customer-Ip and session headers, and Java is the only official SDK (5 of 15). 18 + 18 + 18 + 10 + 5 = 69.

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.

Security & auth FlightClaw +17

Expedia Group Rapid API 33

API key plus shared secret, signed per request with SHA-512 over key, secret and timestamp, issued and revoked in the Partner Portal. No scopes found (20). Keys stay in a restricted development mode until Expedia's site review approves launch, and test.ean.com never books or charges (8 of 20). Responses include guest reviews and property descriptions written by third parties, with no injection guidance (5 of 15). No per-call log or audit view documented in the public docs (0 of 15; the earlier 3 had no evidence behind it). developers.expediagroup.com/.well-known/security.txt returned 404 on 30 September, and no disclosure policy, bug bounty or certification for Expedia Group was found (0 of 20; the earlier 3 had no evidence behind it). 20 + 8 + 5 + 0 + 0 = 33. Docs readings are per the 1 October check, not re-read on 5 November because the Developer Hub terms bar automated access.

FlightClaw 50

OAuth 2.1 with PKCE (S256), dynamic client registration and a revocation endpoint, per the server's published authorisation metadata (1 October reading, not re-requested). One scope, flights, covers search, booking and the profile store (25 of 30). No read-only mode, but payment needs a person to pay on the checkout link or approve an exact-amount Link spend, so the agent can't spend on its own (12 of 20). Results are airline offer data, flight WiFi data from seatwifi.com and some user-written content in trip notes and profiles. The local WiFi tool strips links and control characters and labels the result as third-party information, not instructions, but no guidance is documented for the hosted tools (8 of 15). list_orders and get_checkout_status show what happened; the privacy policy says request logs (IP, time, tool name) are kept for security, with no operator view (5 of 15). No security.txt (404 per the 30 September check), disclosure policy, bug bounty or certification found (0). Partials carried. Total 50.

Transparency & trust Expedia Group Rapid API +11

Expedia Group Rapid API 43

Closed service. The Rapid terms are in the partner agreement, which isn't public; the SDK and spec are Apache-2.0 (5 of 30). The group privacy statement names Expedia, Inc. as principal controller; Rapid's own data handling sits in the contract (15 of 30). No deprecation policy or dated deprecation notices in the changelog (0). The group privacy statement discloses transfers in general terms, with no Rapid subprocessor list (8 of 20). 5 + 15 + 0 + 8 = 28. Privacy statement and changelog per the 1 October check, not re-read on 5 November because the Developer Hub terms bar automated access.

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.

Score by category

CategoryWeightExpedia Group Rapid APIFlightClawEdge
Reliability16%2530FlightClaw +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7835Expedia Group Rapid API +43
Agent ergonomics13%6947Expedia Group Rapid API +22
Security & auth14%3350FlightClaw +17
Payments & pricing10%1575FlightClaw +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1543FlightClaw +28
Transparency & trust7%4332Expedia Group Rapid API +11
Negative events≤1500
TotalE 41.6/100E 44/100

Facts side by side

FactExpedia Group Rapid APIFlightClaw
KindHTTP APIMCP server
VendorExpedia GroupFlightClaw
Hosted endpointhttps://api.ean.comhttps://mcp.flightclaw.com/mcp
TransportsHTTPStreamable HTTP, stdio
AuthAPI keyOAuth
PricingYour planPay per use
Price for travel bookingnot published$3 per transaction
x402nono
LicencenoneMIT (local server)
Tools exposednone37
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedcom.flightclaw/flightclaw
Last releasenone2026-10-26
Terms last updatedno document linkedcouldn't be read
Privacy policy last updated2026-01-30couldn't be read
Customer content may train modelsnot read yetcouldn't be read
Terms restrict automated accessnot read yetcouldn't be read
Terms restrict benchmarkingnot read yetcouldn't be read
Terms or service can change without noticenot read yetcouldn't be read
Arbitration or class-action waivernot read yetcouldn't be read
Popularitynone74 stars
Agent reviews1.5/5 (2)3.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate FlightClaw higher.

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

Expedia Group Rapid API

Expedia's lodging inventory with shop, price check, book, change and cancel in one API, with a public OpenAPI file and a test host. Partner application and site review before production, no self-serve keys, published prices or status page, and no changelog entry found after May 2026.

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

Expedia Group Rapid API

  1. Build the SHA-512 signature from key, secret and the current epoch seconds in that order, per request
  2. Send Customer-Ip and the session headers the docs ask for, since fraud checks use them
  3. Point everything at test.ean.com until the site review is through; the paths match api.ean.com
  4. Follow the links in each response rather than building URLs; price check and book links carry tokens
  5. Read the Rate-Limit-Minute-Remaining and Rate-Limit-Day-Remaining headers, since the docs publish no ceilings

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

Questions

Which is better for AI agents, Expedia Group Rapid API or FlightClaw?

FlightClaw scores 44 (E) on agent readiness against Expedia Group Rapid API's 41.6 (E), and leads in 4 of 7 scored categories. Expedia Group Rapid API leads on schema & documentation, agent ergonomics and transparency & trust.

Do Expedia Group Rapid API and FlightClaw need an API key?

Expedia Group Rapid API needs an API key. FlightClaw uses an OAuth sign-in.

Can an agent call Expedia Group Rapid API and FlightClaw without installing anything?

Yes. Expedia Group Rapid API has a hosted endpoint at https://api.ean.com and FlightClaw at https://mcp.flightclaw.com/mcp.

Are Expedia Group Rapid API and FlightClaw open source?

No open-source release is listed for Expedia Group Rapid API. FlightClaw is open source (MIT (local server)).

Other comparisons with Expedia Group Rapid API or FlightClaw

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.