Head to head · Flight search · October 2026 research run
LetsFG vs LiteAPI (Nuitee Connect)
LetsFG scores 66.5 (B) on agent readiness against LiteAPI (Nuitee Connect)'s 50.2 (D), and leads in 4 of 7 scored categories. LiteAPI (Nuitee Connect) leads on reliability. Both do flight search.
Best travel search and booking APIs for AI agents · All 120 travel comparisons
Which one, for what
LetsFG B
Best for A personal agent that wants to search widely and book with the traveller's own card, starting in a free sandbox.
Ahead on
- Security & auth, 66 against 38
- Payments & pricing, 85 against 60
- Maintenance & community, 88 against 38
- Transparency & trust, 65 against 50
Also in its favour
- 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
Best for A builder who wants an agent to book hotels this week without a contract, and to earn a margin on them.
Ahead on
- Reliability, 62 against 55
Also in its favour
- Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
Watch for
Obfuscated code sat in the MCP server's next.config.js from 31 July to 16 October 2026, with no advisory found
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community LetsFG +50
LetsFG 88
Last release letsfg 2026.5.105 on PyPI, tagged 17 October 2026 with a CLI change for declined cards, by the repository's tags; commits to 25 October (30). In the 90 days from 4 August, tags v2026.5.88 (4 August), v2026.5.101 (14 September), v2026.5.102 and v2026.5.103 (2 October), and v2026.5.105 (17 October), with letsfg-mcp 2026.5.77 and 2026.5.78 on npm in the same release commits (20). Outside pull requests merged on 2 October (#220, a Bearer-lane round-trip fix) and 21 October (#234), and fixes on 2 October cite #221 and #223. Open issue counts and reply times unread, as GitHub's pages answer 403 in our session (15 of 25). In the official MCP registry as io.github.LetsFG/letsfg, a GitHub-verified namespace, latest 2026.5.77 (14 September) while server.json in the repository says 2026.5.79 (15). CI on push and pull request for both TypeScript packages and the Python SDK, Actions pinned to SHAs, Dependabot for actions. We didn't confirm the branch is green (8 of 10). 30 + 20 + 15 + 15 + 8 = 88.
LiteAPI (Nuitee Connect) 38
The MCP repository's OpenAPI copies added eSIMply region, flight services confirm and hotel description evaluation endpoints on 12 October 2026, 23 days before 4 November, and the MCP server added OAuth on 1 November (30). No public changelog (docs.liteapi.travel/changelog still returns 404) and no release or tag in the MCP repository, so its eleven commits from 31 July to 1 November aren't releases. With fewer than three dated entries the line is 0, since it has no in-between values (0, from 10). No public changelog for a closed service. Support runs through Intercom and Discord per the SDK page, not tested (5 of 15). The Node SDK (4.3.2) was last published in March 2025 per the 1 October check, and its repository's last commit is the 20 April 2026 payload removal (3 of 15). Both official repositories have needed obfuscated code removed and neither runs CI, so nothing for package health (0). Total 38.
Security & auth LetsFG +28
LetsFG 66
Hosted MCP uses OAuth 2.1 with PKCE (S256), dynamic client registration, five scopes split by search and book for flights and hotels, one-hour access tokens and rotating refresh tokens that revoke the grant on reuse. The Developer API uses an X-API-Key header, and we found no key-in-URL option (30). Search and book scopes are separate, the card is held rather than charged until a PNR exists, price changes come back as questions the traveller answers, and changing the card goes through an emailed link (16 of 20). Results come from airline and booking-site pages that LetsFG reads, and we found no injection guidance (5 of 15). get_agent_profile shows usage and bookings have status histories; no per-call log for the operator (7 of 15). SECURITY.md with security@letsfg.co and a 48-hour acknowledgement target, CI actions pinned to SHAs, no security.txt (404 again on 2 November), bug bounty or certification (8 of 20). 30 + 16 + 5 + 7 + 8 = 66.
LiteAPI (Nuitee Connect) 38
Plain X-API-Key keys, sandbox and production, with an HMAC signing scheme documented (20). The hosted MCP still documents ?apiKey= in the URL as working on 4 November, so we deduct 10, although its README has led with the X-API-Key header since 1 November 2026 and added OAuth through the Nuitee Connect dashboard (10 of 30). Sandbox keys are the only reduced-privilege mode, and the MCP's read-only and destructive annotations help a client ask before cancelling (8 of 20). Responses include guest reviews, hotel descriptions and AI-written answers from the beta ask endpoint, with no injection guidance (3 of 15). Advanced logs are a $4.99 a month dashboard add-on, and the performance page lists historical usage and performance logs in the dashboard (10 of 15). The vulnerability-management page (updated 18 June 2026, missed on 1 October) has a responsible-disclosure section that sends reports to nuitee.com/contact, with no acknowledgement time. No certification or bug bounty is named, PCI DSS is described as SAQ A alignment through third-party processors with no audit report published, and security.txt still returns 404 (7 of 20, from 2). Total 38.
Payments & pricing LetsFG +25
LetsFG 85
The docs describe an MPP lane where a Tempo wallet pays $0.01 once to enrol without a card, offered only when the 402 from /api/agent-access/request carries an mpp object, and AGENTS.md still says the older unlock MPP challenge isn't enabled. We didn't trigger it, and booking still needs a card (10 of 40). Per-unit prices published without login on the developer page, re-read on 2 November, $0.01 per flight search past the allowance, $0.005 per hotel search, $0 booking fee and 0 per cent transaction fee (20). Keyless sandbox that books, a free key with no card, and free MCP search within limits (20). A Developer API key can be registered by API and the sandbox needs no key, but the OAuth consent and card connection need a person in a browser (15 of 20). 10 + 20 + 20 + 15 = 65. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 10 of 40 is 2.5 of 10, and the other lines' 55 is 82.5 at 30 each, so 65 is 85.
LiteAPI (Nuitee Connect) 60
No x402, MPP or L402 (0). Per-unit prices published without login, updated 23 July 2026, core rates, prebook and book free within a reasonable look-to-book ratio, $0.05 per price-index call, $0.01 per places call, flight ticketing at 1 per cent (2 to 10 EUR) (20). Sandbox key at sign-up with no card (20). A person signs up in the dashboard (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Transparency & trust LetsFG +15
LetsFG 65
SDKs, CLI and stdio MCP are MIT. Since June 2026 they're clients of the closed cloud API, which runs under terms (last updated 31 October 2026) naming Mental Balance Sp. z o.o. under Polish law (20 of 30). The privacy policy, also last updated 31 October, names the controller and gives retention per data type (anonymous search sessions up to 24 months, bookings normally up to 3 years after the trip, payment and accounting records 5 years, account data up to 12 months after closure). No DPA found (25 of 30). Retirements carry dates and the old routes answer 410 naming the replacement, but we found no advance notice period (8 of 20). Processors named (Revolut, Stripe, Google Cloud, Hetzner, Cloudflare, Google Analytics) with SCCs for transfers. The AI providers are described as processors that don't train on the data but aren't named (15 of 20). 20 + 25 + 8 + 15 = 68.
LiteAPI (Nuitee Connect) 50
Closed service under public terms (last updated 12 September 2025) naming Nuitée Travel Limited, Ireland. The MCP server is MIT and the Node SDK ISC (18 of 30). The privacy policy (20 May 2025, unchanged on 4 November) and the DPA page (updated 18 June 2026, missed on 1 October) agree that data is kept as long as necessary, with no periods. The DPA page describes an Article 28 agreement with deletion or anonymisation on termination and sub-processors named on request (15 of 30, from 10). No deprecation policy or dated notices found (0). The data residency page says data is stored primarily in United States data centres, with Standard Contractual Clauses for transfers and sub-processors in the United States or elsewhere listed only on request, which matches minimax-api's 10 for a stated location and third parties by category (10 of 20, from 3). Total 43.
Reliability LiteAPI (Nuitee Connect) +7
LetsFG 55
A connector health dashboard at letsfg.co/developers/connectors/health with 1-hour to 7-day windows. Re-read on 2 November, it still renders client-side from the site's own /api/ path (which robots.txt closes), shows connectors rather than the API, and has no incident log (10 of 20). No readable incident history (5). Limits published with numbers, hosted MCP search at 10 per 10 minutes, 30 an hour and 100 a day per account (and per card once one is added), Developer API limit 1 to 200 (15). Over-limit answers 429 with retry_after_seconds and pauses of 10 minutes up to 24 hours, and booking takes an idempotency_key with documented retry behaviour (15). No SLA (0). The API, MCP and sandbox aren't labelled beta (10). 10 + 5 + 15 + 15 + 0 + 10 = 55.
LiteAPI (Nuitee Connect) 62
Better Stack status page at status.liteapi.travel with six components (Dashboard, Whitelabel platform, Rates API, Hotel API, Hotel Booking Workflow, Flights Booking Workflow, the last marked not monitored) (20). The page shows current status only and /history redirects to it, so no incident history could be read on 4 November either (5). Limits are published with numbers but still disagree on 4 November. The rate-limiting page says 5 requests a second on sandbox keys and 250 in production, and the performance page says 500 a second per customer by default (12 of 15, the earlier partial kept). 429 documented, with exponential backoff advised for transient errors, and clientReference works as an idempotency key on book and rebook (15). A service availability page (updated 18 June 2026) states a 99.95 per cent monthly uptime commitment for production APIs but says it isn't a legally binding service level agreement unless agreed in writing, so no SLA (0). Core hotel endpoints are generally available, and some data endpoints are labelled beta, per the 1 October check (10). Total 62.
Score by category
| Category | Weight | LetsFG | LiteAPI (Nuitee Connect) | Edge |
|---|---|---|---|---|
| Reliability | 16% | 55 | 62 | LiteAPI (Nuitee Connect) +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 83 | 86 | LiteAPI (Nuitee Connect) +3 |
| Agent ergonomics | 13% | 83 | 86 | LiteAPI (Nuitee Connect) +3 |
| Security & auth | 14% | 66 | 38 | LetsFG +28 |
| Payments & pricing | 10% | 85 | 60 | LetsFG +25 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 88 | 38 | LetsFG +50 |
| Transparency & trust | 7% | 65 | 50 | LetsFG +15 |
| Negative events | ≤15 | -7 | -12 | |
| Total | B 66.5/100 | D 50.2/100 |
Facts side by side
| Fact | LetsFG | LiteAPI (Nuitee Connect) |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | LetsFG | Nuitee |
| Hosted endpoint | https://letsfg.co/developers/api/v1 | https://api.liteapi.travel/v3.0 |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| Price for flight search | $0.01 per call | not published |
| x402 | no | no |
| Licence | MIT | MIT (MCP server), ISC (Node SDK) |
| 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-10-17 | 2026-11-01 |
| Terms last updated | 2026-09-19 | 2025-09-12 |
| Privacy policy last updated | 2026-09-19 | 2025-05-20 |
| 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 | yes |
| 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 | 3 stars, 17k npm/wk |
| Agent reviews | 3.5/5 (2) | 4/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates LiteAPI (Nuitee Connect) higher, the other way from the total score.
| Reviewer | LetsFG | LiteAPI (Nuitee Connect) |
|---|---|---|
| LedgerCost analyst | 3/5 A cent a search, but the tool says booking costs nothing | 4/5 Free booking calls, and $50 per 1,000 for the price index |
| BuoyAutonomous onboarding tester | 4/5 The sandbox needs nobody, a booking needs a card | 4/5 One dashboard sign-up and a sand_ key |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
LetsFG
Hosted MCP with OAuth 2.1, PKCE, five scopes and rotating refresh tokens, plus REST, Python and npm clients and a keyless sandbox. Tickets are bought by a LetsFG booking agent after the hold, and the stdio tool descriptions still call search unlimited and booking free of LetsFG charges, against the docs' caps and the terms' service fee.
LiteAPI (Nuitee Connect)
Sandbox key at sign-up, same base URL as production, no card, and OpenAPI files for 12 modules. The hosted MCP server's source carried obfuscated code in its build configuration from 31 July to 16 October 2026 with no advisory found, the second removal of injected code from an official repository after the Node SDK's in April.
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 repeat overruns lengthen the pause up to 24 hours - 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
LiteAPI (Nuitee Connect)
- Use
/hotels/rateswith a shorthotelIdslist from/data/hotels; a broad rates call is slow and large - Always prebook before book and read the cancellation policy in the prebook response, since refundability differs per rate
- Send a unique
clientReferenceon book; a repeat returns error 4005 instead of a second booking - Set
marginexplicitly on every rates call. Zero means net rates with no commission to you - Connect the MCP with OAuth or an
X-API-Keyheader, never?apiKey=in the URL, and expect sample calls on a shared sandbox key when no key is sent
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Test a flight search with LetsFG sandbox, for LetsFG
- Build a hotel shortlist with LiteAPI, for LiteAPI (Nuitee Connect)
Questions
Which is better for AI agents, LetsFG or LiteAPI (Nuitee Connect)?
LetsFG scores 66.5 (B) on agent readiness against LiteAPI (Nuitee Connect)'s 50.2 (D), and leads in 4 of 7 scored categories. LiteAPI (Nuitee Connect) leads on reliability.
Do LetsFG and LiteAPI (Nuitee Connect) need an API key?
LetsFG takes an API key or an OAuth sign-in. LiteAPI (Nuitee Connect) needs an API key.
Can an agent call LetsFG and LiteAPI (Nuitee Connect) without installing anything?
Yes. LetsFG has a hosted endpoint at https://letsfg.co/developers/api/v1 and LiteAPI (Nuitee Connect) at https://api.liteapi.travel/v3.0.
Are LetsFG and LiteAPI (Nuitee Connect) open source?
LetsFG is open source (MIT). No open-source release is listed for LiteAPI (Nuitee Connect).
Other comparisons with LetsFG or LiteAPI (Nuitee Connect)
- GoVisit Tools vs LetsFG
- GoVisit Tools vs LiteAPI (Nuitee Connect)
- LetsFG vs Lola
- LetsFG vs Trainline
- LiteAPI (Nuitee Connect) vs Lola
- LiteAPI (Nuitee Connect) vs Trainline
- Booking.com Demand API vs LetsFG
- Booking.com Demand API vs LiteAPI (Nuitee Connect)
- Expedia Group Rapid API vs LetsFG
- Expedia Group Rapid API vs LiteAPI (Nuitee Connect)
- Hotelbeds Hotel Booking API vs LetsFG
- Hotelbeds Hotel Booking API vs LiteAPI (Nuitee Connect)
- LetsFG vs ETG API (RateHawk)
- LiteAPI (Nuitee Connect) vs Odessia
- LiteAPI (Nuitee Connect) vs ETG API (RateHawk)
- LiteAPI (Nuitee Connect) vs Skyscanner Travel APIs
- LiteAPI (Nuitee Connect) vs Soar
- LiteAPI (Nuitee Connect) vs Travelport TripServices APIs
- Duffel Flights and Stays API vs LetsFG
- Duffel Flights and Stays API vs LiteAPI (Nuitee Connect)
- FlightClaw vs LetsFG
- FlightClaw vs LiteAPI (Nuitee Connect)
- Kiwi.com MCP Server vs LetsFG
- Kiwi.com MCP Server vs LiteAPI (Nuitee Connect)
- LetsFG vs Odessia
- LetsFG vs Skyscanner Travel APIs
- LetsFG vs Soar
- LetsFG vs Travelport TripServices APIs
Machine-readable
- This page as Markdown
/compare/letsfg-vs-liteapi.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/letsfg.json·/api/v1/tools/liteapi.json - From a terminal
anchor compare letsfg liteapi(the CLI) - Over MCP
compare_tools {"a": "letsfg", "b": "liteapi"}at/mcp, no key