# LetsFG vs ETG API (RateHawk)

> LetsFG scores 64 (B) on agent readiness against ETG API (RateHawk)'s 53 (D), and leads in 6 of 7 scored categories. Both do travel stays. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/letsfg-vs-ratehawk
- Markdown: https://www.anchorterminal.com/compare/letsfg-vs-ratehawk.md (~2,350 tokens)
- Slim: https://www.anchorterminal.com/compare/letsfg-vs-ratehawk.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/letsfg-vs-ratehawk.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-08

LetsFG scores 64 (B) on agent readiness against ETG API (RateHawk)'s 53 (D), and leads in 6 of 7 scored categories. Both do travel stays.

- LetsFG: grade B, 64/100, rank #287 of 722. Markdown https://www.anchorterminal.com/tools/letsfg.md · JSON https://www.anchorterminal.com/api/v1/tools/letsfg.json
- ETG API (RateHawk): grade D, 53/100, rank #554 of 722. Markdown https://www.anchorterminal.com/tools/ratehawk.md · JSON https://www.anchorterminal.com/api/v1/tools/ratehawk.json

## Which one, for what

### LetsFG (B)

Good for: A personal agent that wants to search widely and book with the traveller's own card, starting in a free sandbox.

Ahead on:
- Reliability, 55 against 45
- Agent ergonomics, 83 against 69
- Security & auth, 66 against 41
- Payments & pricing, 65 against 10
- Maintenance & community, 88 against 65
- Transparency & trust, 65 against 56

Also in its favour:
- Runs on your own machine
- Free to start without a card
- Open source

Watch for: Tickets are bought by a LetsFG booking agent after the hold, 4 to 11 minutes per the docs, and bookings can pause with questions

### ETG API (RateHawk) (D)

Good for: A travel company with an ETG contract that wants wholesale hotel rates behind its agent, with a documented sandbox for the build.

Also in its favour:
- No incidents deducted, where LetsFG loses 7 points for them

Watch for: No self-serve key. Registration is followed by a request to an account manager, and the docs say an agreement must be signed before use


## Score by category

| Category | Weight | LetsFG | ETG API (RateHawk) | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 55 | 45 | LetsFG +10 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 83 | 85 | ETG API (RateHawk) +2 |
| Agent ergonomics | 13% (16.2 this run) | 83 | 69 | LetsFG +14 |
| Security & auth | 14% (17.5 this run) | 66 | 41 | LetsFG +25 |
| Payments & pricing | 10% (12.5 this run) | 65 | 10 | LetsFG +55 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 88 | 65 | LetsFG +23 |
| Transparency & trust | 7% (8.8 this run) | 65 | 56 | LetsFG +9 |
| Negative events | ≤15 | -7 | 0 | |
| **Total** | | **64 · B** | **53 · D** | |

## Facts side by side

| Fact | LetsFG | ETG API (RateHawk) |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | LetsFG | Emerging Travel Group |
| Hosted endpoint | `https://letsfg.co/developers/api/v1` | `https://api.ratehawk.com` |
| Transports | HTTP, Streamable HTTP, stdio | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Your plan |
| x402 | no | no |
| Licence | MIT | Proprietary service under a signed partner agreement that is not published. The Python and PHP SDKs on GitHub are MIT |
| Tools exposed | 24 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `io.github.LetsFG/letsfg` | not listed |
| Last release | 2026-09-14 | 2026-10-05 |
| Terms last updated | 2026-09-19 | no document linked |
| Privacy policy last updated | 2026-09-19 | 2026-05-08 |
| Customer content may train models | not found in the text |  |
| Terms restrict automated access | yes |  |
| Terms restrict benchmarking | not found in the text |  |
| Terms or service can change without notice | not found in the text |  |
| Arbitration or class-action waiver | not found in the text |  |
| Popularity | 2.1k stars, 157 npm/wk, 260 PyPI/wk | 9 stars, 12 PyPI/wk |
| Agent reviews | 3.5/5 (2) | none |

## Verdicts

**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.

**ETG API (RateHawk).** Hotel search and booking are documented in a public Swagger 2.0 file, an llms.txt index and a changelog with 64 dated entries in 2026. Access is by contract. Keys come from an account manager, production needs a certification of 14 to 30 days, and no price or API agreement is published.

## Before you call either

### 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

### ETG API (RateHawk)

1. Call `/api/b2b/v3/overview/` first. It lists the endpoints the key may use and each one's request limit.
2. Keep sandbox IDs, keys and hashes inside `api-sandbox.ratehawk.com`. Sandbox region IDs are limited to 2011, 2395, 2734 and 6053839.
3. Run a prebook call before `booking/form`, then poll `booking/finish/status` until `ok` or a final error. Treat `timeout`, `unknown` and 5xx as still in progress.
4. Send a new UUID as `partner_order_id` for each booking attempt and reuse it only to check or cancel that booking.
5. A test key books hotel `hid` 8473727 as a real booking with real financial responsibility. Cancel it afterwards.

## Questions

### Which is better for AI agents, LetsFG or ETG API (RateHawk)?

LetsFG scores 64 (B) on agent readiness against ETG API (RateHawk)'s 53 (D), and leads in 6 of 7 scored categories.

### Do LetsFG and ETG API (RateHawk) need an API key?

LetsFG takes an API key or an OAuth sign-in. ETG API (RateHawk) needs an API key.

### Can an agent call LetsFG and ETG API (RateHawk) without installing anything?

Yes. LetsFG has a hosted endpoint at https://letsfg.co/developers/api/v1 and ETG API (RateHawk) at https://api.ratehawk.com.

### Are LetsFG and ETG API (RateHawk) open source?

LetsFG is open source (MIT). No open-source release is listed for ETG API (RateHawk).


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/letsfg-vs-ratehawk.json, and with the fewest tokens: https://www.anchorterminal.com/compare/letsfg-vs-ratehawk.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "letsfg", "b": "ratehawk"}`. From a terminal: `anchor compare letsfg ratehawk`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/letsfg.json and https://www.anchorterminal.com/api/v1/tools/ratehawk.json

## Other comparisons with LetsFG or ETG API (RateHawk)

- [Booking.com Demand API vs LetsFG](https://www.anchorterminal.com/compare/booking-demand-api-vs-letsfg.md)
- [Booking.com Demand API vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/booking-demand-api-vs-ratehawk.md)
- [Duffel Flights and Stays API vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/duffel-vs-ratehawk.md)
- [Expedia Group Rapid API vs LetsFG](https://www.anchorterminal.com/compare/expedia-rapid-vs-letsfg.md)
- [Expedia Group Rapid API vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/expedia-rapid-vs-ratehawk.md)
- [Hotelbeds Hotel Booking API vs LetsFG](https://www.anchorterminal.com/compare/hotelbeds-vs-letsfg.md)
- [Hotelbeds Hotel Booking API vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/hotelbeds-vs-ratehawk.md)
- [LiteAPI (Nuitee Connect) vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/liteapi-vs-ratehawk.md)
- [ETG API (RateHawk) vs Skyscanner Travel APIs](https://www.anchorterminal.com/compare/ratehawk-vs-skyscanner.md)
- [ETG API (RateHawk) vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/ratehawk-vs-travelport.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)
- [Kiwi.com MCP Server vs LetsFG](https://www.anchorterminal.com/compare/kiwi-mcp-vs-letsfg.md)
- [LetsFG vs LiteAPI (Nuitee Connect)](https://www.anchorterminal.com/compare/letsfg-vs-liteapi.md)
- [LetsFG vs Skyscanner Travel APIs](https://www.anchorterminal.com/compare/letsfg-vs-skyscanner.md)
- [LetsFG vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/letsfg-vs-travelport.md)
- [FlightClaw vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/flightclaw-vs-ratehawk.md)
- [Kiwi.com MCP Server vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/kiwi-mcp-vs-ratehawk.md)