Head to head · Travel flights · October 2026 research run
LetsFG vs Travelport TripServices APIs
LetsFG scores 64 (B) on agent readiness against Travelport TripServices APIs's 45.9 (E), and leads in 6 of 7 scored categories. Both do travel flights.
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 19
- Agent ergonomics, 83 against 51
- Security & auth, 66 against 47
- Payments & pricing, 65 against 20
- Maintenance & community, 88 against 56
- Transparency & trust, 65 against 52
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
Travelport TripServices APIs E
Good for A travel agency, travel management company or travel platform that will sign a GDS contract and wants GDS, NDC and low-cost air content with full servicing plus hotels.
Also in its favour
- No incidents deducted, where LetsFG loses 7 points for them
Watch for
The API and SDK Terms of Use forbid any automated process or tool, such as a bot, without written authorisation from Travelport
Score by category
| Category | Weight this run | LetsFG | Travelport TripServices APIs | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 55 | 19 | LetsFG +36 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 83 | 84 | Travelport TripServices APIs +1 |
| Agent ergonomics | 13%16.2 | 83 | 51 | LetsFG +32 |
| Security & auth | 14%17.5 | 66 | 47 | LetsFG +19 |
| Payments & pricing | 10%12.5 | 65 | 20 | LetsFG +45 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 88 | 56 | LetsFG +32 |
| Transparency & trust | 7%8.8 | 65 | 52 | LetsFG +13 |
| Negative events | ≤15 | -7 | 0 | |
| Total | 64 · B | 45.9 · E |
Facts side by side
| Fact | LetsFG | Travelport TripServices APIs |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | LetsFG | Travelport |
| Hosted endpoint | https://letsfg.co/developers/api/v1 | https://api.travelport.net |
| Transports | HTTP, Streamable HTTP, stdio | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Paid |
| Price for travel flights | $0.01 per call | not published |
| x402 | no | no |
| Licence | MIT | Proprietary service under a Developer Contract and Travelport's API and SDK Terms of Use |
| 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-08-12 |
| Terms last updated | 2026-09-19 | no date given |
| Privacy policy last updated | 2026-09-19 | 2025-01-03 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 2.1k stars, 157 npm/wk, 260 PyPI/wk | none |
| 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.
Travelport TripServices APIs
Public OpenAPI 3.0 files, Markdown docs and an llms.txt cover search, pricing, booking, ticketing, exchanges and hotel stays, with dated release notes through August 2026. Production needs a sales contract and certification with 15 days' notice. No price, API rate limit, status page or SLA is published, and the terms bar automated tools without written permission.
Before you call either
LetsFG
- Start on
/v1/sandbox/with no key; the booking states, questions and timings match production - After
book_flight, pollget_flight_bookingevery 20 to 30 seconds and answer questions beforeexpires_at_ms; an unanswered price change fails the booking and releases the hold - Honour
retry_after_secondson a 429. Over MCP the limit is 10 searches per 10 minutes and 100 a day, and early retries lengthen the pause - Fetch results with
get_flight_resultsand thesearch_idrather than searching again, which spends allowance - Send the same
idempotency_keywhen retrying a booking after a timeout - Treat a 410 as a retired route and read the replacement path in its body
Travelport TripServices APIs
- Request one token and cache it for 24 hours. Travelport declines certification for refreshing more often than every 23 hours without a stated reason
- Send
Accept-Encoding: gzip, deflateandXAUTH_TRAVELPORT_ACCESSGROUP(orTVP-PCC-CORE) on every call. Production traffic without compression is refused - Send
offersPerPageon a journey-based search, or later calls can't reference its results. Cached searches last 12 minutes for GDS content and 34 for NDC - Commit a workbench within 30 minutes or it expires, and read
Result/Errorin the body even on HTTP 200 - Get written authorisation for agent access before production. The terms bar automated tools and speculative or duplicate bookings
Questions
Which is better for AI agents, LetsFG or Travelport TripServices APIs?
LetsFG scores 64 (B) on agent readiness against Travelport TripServices APIs's 45.9 (E), and leads in 6 of 7 scored categories.
Do LetsFG and Travelport TripServices APIs need an API key?
LetsFG takes an API key or an OAuth sign-in. Travelport TripServices APIs uses an OAuth sign-in.
Can an agent call LetsFG and Travelport TripServices APIs without installing anything?
Yes. LetsFG has a hosted endpoint at https://letsfg.co/developers/api/v1 and Travelport TripServices APIs at https://api.travelport.net.
Are LetsFG and Travelport TripServices APIs open source?
LetsFG is open source (MIT). No open-source release is listed for Travelport TripServices APIs.
Other comparisons with LetsFG or Travelport TripServices APIs
- Booking.com Demand API vs LetsFG
- Booking.com Demand API vs Travelport TripServices APIs
- Expedia Group Rapid API vs LetsFG
- Expedia Group Rapid API vs Travelport TripServices APIs
- Hotelbeds Hotel Booking API vs LetsFG
- Hotelbeds Hotel Booking API vs Travelport TripServices APIs
- LetsFG vs ETG API (RateHawk)
- LiteAPI (Nuitee Connect) vs Travelport TripServices APIs
- ETG API (RateHawk) vs Travelport TripServices APIs
- Duffel Flights and Stays API vs LetsFG
- Duffel Flights and Stays API vs Travelport TripServices APIs
- FlightClaw vs LetsFG
- FlightClaw vs Travelport TripServices APIs
- Kiwi.com MCP Server vs LetsFG
- Kiwi.com MCP Server vs Travelport TripServices APIs
- LetsFG vs LiteAPI (Nuitee Connect)
- LetsFG vs Skyscanner Travel APIs
- Skyscanner Travel APIs vs Travelport TripServices APIs
Machine-readable
- This page as Markdown
/compare/letsfg-vs-travelport.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/letsfg.json·/api/v1/tools/travelport.json - From a terminal
anchor compare letsfg travelport(the CLI) - Over MCP
compare_tools {"a": "letsfg", "b": "travelport"}at/mcp, no key