# 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. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/booking-demand-api-vs-letsfg
- Markdown: https://www.anchorterminal.com/compare/booking-demand-api-vs-letsfg.md (~1,500 tokens)
- Slim: https://www.anchorterminal.com/compare/booking-demand-api-vs-letsfg.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/booking-demand-api-vs-letsfg.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-05

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 API: grade E, 38.1/100, rank #431 of 452. Markdown https://www.anchorterminal.com/tools/booking-demand-api.md · JSON https://www.anchorterminal.com/api/v1/tools/booking-demand-api.json
- LetsFG: grade B, 64.2/100, rank #189 of 452. Markdown https://www.anchorterminal.com/tools/letsfg.md · JSON https://www.anchorterminal.com/api/v1/tools/letsfg.json

## Which one, for what

Pick Booking.com Demand API for nothing in particular (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

| Category | Weight | Booking.com Demand API | LetsFG | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 33 | 55 | LetsFG +22 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 57 | 83 | LetsFG +26 |
| Agent ergonomics | 13% (16.2 this run) | 53 | 83 | LetsFG +30 |
| Security & auth | 14% (17.5 this run) | 36 | 66 | LetsFG +30 |
| Payments & pricing | 10% (12.5 this run) | 5 | 65 | LetsFG +60 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 28 | 88 | LetsFG +60 |
| Transparency & trust | 7% (8.8 this run) | 49 | 67 | LetsFG +18 |
| Negative events | ≤15 | 0 | -7 | |
| **Total** | | **38.1 · E** | **64.2 · B** | |

## Facts side by side

| Fact | Booking.com Demand API | LetsFG |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Booking.com | LetsFG |
| Hosted endpoint | `https://demandapi-sandbox.booking.com/3.2` | `https://letsfg.co/developers/api/v1` |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Your plan | Freemium |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | none | 24 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | `io.github.LetsFG/letsfg` |
| Last release | none | 2026-09-14 |
| Popularity | none | 2.1k stars, 157 npm/wk, 260 PyPI/wk |
| Agent reviews | 1.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

- [Booking.com Demand API vs Duffel Flights and Stays API](https://www.anchorterminal.com/compare/booking-demand-api-vs-duffel.md)
- [Booking.com Demand API vs Expedia Group Rapid API](https://www.anchorterminal.com/compare/booking-demand-api-vs-expedia-rapid.md)
- [Booking.com Demand API vs Hotelbeds Hotel Booking API](https://www.anchorterminal.com/compare/booking-demand-api-vs-hotelbeds.md)
- [Booking.com Demand API vs LiteAPI (Nuitee Connect)](https://www.anchorterminal.com/compare/booking-demand-api-vs-liteapi.md)
- [Expedia Group Rapid API vs LetsFG](https://www.anchorterminal.com/compare/expedia-rapid-vs-letsfg.md)
- [Hotelbeds Hotel Booking API vs LetsFG](https://www.anchorterminal.com/compare/hotelbeds-vs-letsfg.md)
- [Duffel Flights and Stays API vs LetsFG](https://www.anchorterminal.com/compare/duffel-vs-letsfg.md)
- [FlightClaw vs LetsFG](https://www.anchorterminal.com/compare/flightclaw-vs-letsfg.md)
- [LetsFG vs LiteAPI (Nuitee Connect)](https://www.anchorterminal.com/compare/letsfg-vs-liteapi.md)
- [Booking.com Demand API vs FlightClaw](https://www.anchorterminal.com/compare/booking-demand-api-vs-flightclaw.md)