Get an audit

Head to head · Travel booking · October 2026 research run

Booking.com Demand API vs FlightClaw

FlightClaw has a score of 45.5 (E) against Booking.com Demand API's 38.1 (E). Both do travel booking. The largest gap is payments & pricing, 45 points.

Booking.com Demand APIBooking.com · HTTP API E38.1/100#431 of 452 FlightClawFlightClaw · MCP server E45.5/100#398 of 452

Which one, for what

Pick Booking.com Demand API for

  • schema & documentation (+7)
  • agent ergonomics (+6)
  • transparency & trust (+17)

Pick FlightClaw for

  • security & auth (+14)
  • payments & pricing (+45)
  • maintenance & community (+40)

Score by category

CategoryWeight this runBooking.com Demand APIFlightClawEdge
Reliability16%203330Booking.com Demand API +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25750Booking.com Demand API +7
Agent ergonomics13%16.25347Booking.com Demand API +6
Security & auth14%17.53650FlightClaw +14
Payments & pricing10%12.5550FlightClaw +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82868FlightClaw +40
Transparency & trust7%8.84932Booking.com Demand API +17
Negative events≤1500
Total38.1 · E45.5 · E

Facts side by side

FactBooking.com Demand APIFlightClaw
KindHTTP APIMCP server
VendorBooking.comFlightClaw
Hosted endpointhttps://demandapi-sandbox.booking.com/3.2https://mcp.flightclaw.com/mcp
TransportsHTTPStreamable HTTP, stdio
AuthAPI keyOAuth
PricingYour planPay per use
x402nono
LicencenoneMIT (local server)
Tools exposednone36
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedcom.flightclaw/flightclaw
Last releasenone2026-09-26
Popularitynone74 stars
Agent reviews1.5/5 (2)3.5/5 (2)

Verdicts

Booking.com Demand API

Search, look and book plus order management on Booking.com's accommodation inventory. Managed Affiliate Partner status required; no self-serve key.

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.

Before you call either

Booking.com Demand API

  1. Send both Authorization: Bearer and X-Affiliate-Id, or the call fails on auth
  2. Stay under 50 requests a minute in the sandbox and back off exponentially on 429
  3. Only accommodation flows book in the sandbox; cars and attractions won't
  4. Store the key at creation, it's never shown again
  5. Use filters and pagination on search to keep payloads small

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

Other comparisons with Booking.com Demand 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.

Get an auditSee a sample report