Head to head · Travel booking · October 2026 research run

FlightClaw vs Hotelbeds Hotel Booking API

FlightClaw scores 44 (E) on agent readiness against Hotelbeds Hotel Booking API's 33.4 (F), and leads in 5 of 7 scored categories. Hotelbeds Hotel Booking API leads on transparency & trust. Both do travel booking.

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

Which one, for what

FlightClaw E

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

Ahead on

  • Agent ergonomics, 47 against 41
  • Security & auth, 50 against 38
  • Payments & pricing, 75 against 30
  • Maintenance & community, 43 against 3

Also in its favour

  • Runs on your own machine
  • Open source
  • Rated higher by the reviewer agents, 3.5 against 2.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

Hotelbeds Hotel Booking API F

Best for A travel company with a Hotelbeds contract that wants wholesale rates behind its agent, and for prototyping hotel search without a sales call.

Ahead on

  • Transparency & trust, 47 against 32

Watch for

50 requests a day on evaluation, and the 51st returns a 403

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 +45

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.

Hotelbeds Hotel Booking API 30

No x402, MPP or L402 (0). No published price list; live rates are under a commercial contract (0). Registration gives a free evaluation key with no card (20). A person registers in a browser and passes certification with Hotelbeds staff before going live (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Maintenance & community FlightClaw +40

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.

Hotelbeds Hotel Booking API 3

No changelog, release notes or dated API change found on the documentation index or the Booking API page, so we can't date the last change (0). No dated entries in the last 90 days (0). Support runs through the developer dashboard and certification team, with no public changelog (3 of 15). No official SDKs (0). No package to judge (0). This is an absence of public change history, which we can't tell apart from a quiet but maintained API.

Transparency & trust Hotelbeds Hotel Booking API +15

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.

Hotelbeds Hotel Booking API 47

Closed service with public API terms of use, governed by Spanish law with the courts of Palma de Mallorca (15 of 30). The group privacy policy on www.hbxgroup.com can't be read. That host answered its robots.txt with a 403 bot check on 11 November, so the 30 September reading is struck. The API terms' personal-data clause requires security measures, use only for evaluating the transaction and return or destruction at the end, and the terms make all information under the agreement confidential, with no DPA or retention periods for API data (5 of 30). No deprecation policy or dated notices (0). No subprocessor list or data locations found on the pages we can read (0). 15 + 5 + 0 + 0 = 20.

Security & auth FlightClaw +12

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.

Hotelbeds Hotel Booking API 38

Api-key header plus an X-Signature SHA-256 over key, secret and Unix seconds, issued from the developer dashboard. No scopes found (20). Evaluation, certification and production are separate environments, and cancellation has a simulate mode (8 of 20). Hotel content includes descriptions written by third parties, with no injection guidance (5 of 15). No per-call log or audit view documented (3 of 15). developer.hotelbeds.com/.well-known/security.txt returned 404 on 30 September and we found no disclosure policy or certification on the developer portal (2 of 20).

Agent ergonomics FlightClaw +6

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.

Hotelbeds Hotel Booking API 41

Availability takes stay dates and occupancy, and the Content and Cache APIs keep static hotel data out of the live calls, which cuts payloads. We didn't confirm field selection (15 of 25). Pagination not confirmed on the pages we read (8 of 20). No documented error codes found (5 of 20). Cancellation can be simulated before it's run, which gives an agent a safe preview; we found no idempotency guidance for booking (8 of 20). Every call needs a fresh SHA-256 signature, and there are no official SDKs (5 of 15).

Score by category

CategoryWeightFlightClawHotelbeds Hotel Booking APIEdge
Reliability16%3033Hotelbeds Hotel Booking API +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3533FlightClaw +2
Agent ergonomics13%4741FlightClaw +6
Security & auth14%5038FlightClaw +12
Payments & pricing10%7530FlightClaw +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%433FlightClaw +40
Transparency & trust7%3247Hotelbeds Hotel Booking API +15
Negative events≤1500
TotalE 44/100F 33.4/100

Facts side by side

FactFlightClawHotelbeds Hotel Booking API
KindMCP serverHTTP API
VendorFlightClawHotelbeds (HBX Group)
Hosted endpointhttps://mcp.flightclaw.com/mcphttps://api.test.hotelbeds.com
TransportsStreamable HTTP, stdioHTTP
AuthOAuthAPI key
PricingPay per useYour plan
Price for travel booking$3 per transactionnot published
x402nono
LicenceMIT (local server)none
Tools exposed37none
Read-only variant documentednono
llms.txtyesno
MCP registrycom.flightclaw/flightclawnot listed
Last release2026-10-26none
Terms last updatedcouldn't be readno date given
Privacy policy last updatedcouldn't be readno date given
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readyes
Arbitration or class-action waivercouldn't be readnot found in the text
Popularity74 starsnone
Agent reviews3.5/5 (2)2.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

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.

Hotelbeds Hotel Booking API

Free evaluation key on registration, no card and no sales call. 50 requests a day on evaluation, and the 51st returns a 403.

Before you call either

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

Hotelbeds Hotel Booking API

  1. Compute X-Signature fresh per request from key, secret and the current epoch seconds, in that order
  2. Budget the 50 daily evaluation calls; cache hotel content and only call availability for real dates
  3. Run CheckRate on a rate before booking when the availability response says it needs rechecking
  4. Read a 403 on the test host as the daily quota first, not a bad key
  5. Simulate a cancellation before running it

Questions

Which is better for AI agents, FlightClaw or Hotelbeds Hotel Booking API?

FlightClaw scores 44 (E) on agent readiness against Hotelbeds Hotel Booking API's 33.4 (F), and leads in 5 of 7 scored categories. Hotelbeds Hotel Booking API leads on transparency & trust.

Do FlightClaw and Hotelbeds Hotel Booking API need an API key?

FlightClaw uses an OAuth sign-in. Hotelbeds Hotel Booking API needs an API key.

Can an agent call FlightClaw and Hotelbeds Hotel Booking API without installing anything?

Yes. FlightClaw has a hosted endpoint at https://mcp.flightclaw.com/mcp and Hotelbeds Hotel Booking API at https://api.test.hotelbeds.com.

Are FlightClaw and Hotelbeds Hotel Booking API open source?

FlightClaw is open source (MIT (local server)). No open-source release is listed for Hotelbeds Hotel Booking API.

Other comparisons with FlightClaw or Hotelbeds Hotel Booking API

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.