Get an audit

Head to head · Travel stays · October 2026 research run

Booking.com Demand API vs LetsFG

LetsFG has a score of 64.2 (B) against Booking.com Demand API's 38.1 (E). Both do travel stays. The largest gap is payments & pricing, 60 points.

Booking.com Demand APIBooking.com · HTTP API E38.1/100#431 of 452 LetsFGLetsFG · HTTP API B64.2/100#189 of 452

Which one, for what

Pick Booking.com Demand API for

No category where it leads by five points or more.

Pick LetsFG for

  • reliability (+22)
  • schema & documentation (+26)
  • agent ergonomics (+30)
  • security & auth (+30)
  • payments & pricing (+60)
  • maintenance & community (+60)
  • transparency & trust (+18)

Score by category

CategoryWeight this runBooking.com Demand APILetsFGEdge
Reliability16%203355LetsFG +22
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25783LetsFG +26
Agent ergonomics13%16.25383LetsFG +30
Security & auth14%17.53666LetsFG +30
Payments & pricing10%12.5565LetsFG +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82888LetsFG +60
Transparency & trust7%8.84967LetsFG +18
Negative events≤150-7
Total38.1 · E64.2 · B

Facts side by side

FactBooking.com Demand APILetsFG
KindHTTP APIHTTP API
VendorBooking.comLetsFG
Hosted endpointhttps://demandapi-sandbox.booking.com/3.2https://letsfg.co/developers/api/v1
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingYour planFreemium
x402nono
LicencenoneMIT
Tools exposednone24
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 listedio.github.LetsFG/letsfg
Last releasenone2026-09-14
Popularitynone2.1k stars, 157 npm/wk, 260 PyPI/wk
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.

LetsFG

Hosted MCP with OAuth 2.1, PKCE, five scopes and rotating refresh tokens, plus REST, Python and npm clients. Tickets are bought by a LetsFG booking agent after the hold, 4 to 11 minutes per the docs, and bookings can pause with questions.

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

LetsFG

  1. Start on /v1/sandbox/ with no key; the booking states, questions and timings match production
  2. After book_flight, poll get_flight_booking every 20 to 30 seconds and answer questions before expires_at_ms; an unanswered price change fails the booking and releases the hold
  3. Honour retry_after_seconds on a 429. Over MCP the limit is 10 searches per 10 minutes and 100 a day, and early retries lengthen the pause
  4. Fetch results with get_flight_results and the search_id rather than searching again, which spends allowance
  5. Send the same idempotency_key when retrying a booking after a timeout
  6. Treat a 410 as a retired route and read the replacement path in its body

Other comparisons with Booking.com Demand API or LetsFG

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