Head to head · Flight search · October 2026 research run
Duffel Flights and Stays API vs LetsFG
Duffel Flights and Stays API scores 71.3 (BB) on agent readiness against LetsFG's 66.5 (B), and leads in 3 of 7 scored categories. LetsFG leads on schema & documentation, security & auth and payments & pricing. Both do flight search.
Best travel search and booking APIs for AI agents · All 120 travel comparisons
Which one, for what
Duffel Flights and Stays API BB
Best for A business building a flight-booking agent that wants live airline inventory without a partner agreement and with prices it can plan against.
Ahead on
- Reliability, 80 against 55
- Transparency & trust, 76 against 65
Also in its favour
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
- No incidents deducted, where LetsFG loses 7 points for them
Watch for
No OpenAPI document, llms.txt or official MCP server
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
- Schema & documentation, 83 against 59
- Security & auth, 66 against 60
- Payments & pricing, 85 against 60
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
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.
Reliability Duffel Flights and Stays API +25
Duffel Flights and Stays API 80
incident.io status page at duffelstatus.com with per-supplier and per-product components and history (20). In the 90 days from 3 August, read from feed.atom on 1 November, 15 incidents (one of them a Scoot maintenance window) and two planned database maintenance windows. The feed holds 17 entries, the oldest on 4 August, and the status page's incident calendar shows that incident, the Chat assistant outage, starting on 3 August at 22:23 UTC, with nothing else posted that day. Each named one supplier, one product or one function, among them Air France KLM card payments on 17 August, saved cards failing on api.duffel.cards on 27 August, a Stays partial outage on 3 September, Sabre order errors on 3 September, the dashboard on 14 September, a Lufthansa Group, Qantas and Aegean search outage on 28 September and Travelport ticketing for a subset of carriers on 21 October. None took the core flights API down, and this run reads one supplier or product as partial whatever the label, so minor incidents only (20). Limit published, 60 requests per 60-second window, with ratelimit-* headers (15). 429 tells you to retry after ratelimit-reset, and order creation has explicit guidance (a 202 means processing, don't retry; use a 130-second timeout) (15). No SLA on the pricing page for either tier (0). Generally available (10). 20 + 20 + 15 + 15 + 0 + 10 = 80.
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.
Payments & pricing LetsFG +25
Duffel Flights and Stays API 60
No x402, MPP or L402 (0). Per-unit prices published without login, re-read on 1 November, $3.00 per order, 1 per cent for Managed Content, $2.00 per paid ancillary, 2 per cent FX, $0.005 per search above 1,500 to 1 (20). Sign-up is free and test mode needs no card or contract, per the 30 September check (20). A person signs up in the dashboard to get tokens (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
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.
Schema & documentation LetsFG +24
Duffel Flights and Stays API 59
No public OpenAPI document found (0). duffel.com/llms.txt and duffel.com/docs/llms.txt both return 404, re-checked on 1 November (0). The API reference states what each endpoint does and the guides cover when to use offer requests, partial offer requests and holds (16 of 20). Typed fields with enums such as cabin_class and passenger type, required fields marked (13 of 15). An error object with type, code, title, message and documentation_url, seven error types and per-status guidance for order creation (15). Duffel-Version header, a written versioning policy and a public changelog (15). 0 + 0 + 16 + 13 + 15 + 15 = 59.
LetsFG 83
OpenAPI 3.1 document served at /developers/api/openapi.json, 36 paths on 2 November (openapi.yaml in the repository still has 16) (25). llms.txt at letsfg.co/llms.txt (last updated 21 October) plus Markdown docs, AGENTS.md and SKILL.md in the repository (10). MCP descriptions say when to call a tool and when not to ("do not retry, give the user the booking_url"), but two contradict the docs and terms on cost and limits, see the negative note (14 of 20). Typed inputs with required lists, enums for cabin class and a nested passenger schema; dates are plain strings (12 of 15). An errors page maps every status and code to an action, and the sandbox documents each failure it can simulate (15). CalVer package versions and git tags, and retirements dated in the docs, but no changelog file (7 of 15). 25 + 10 + 14 + 12 + 15 + 7 = 83.
Transparency & trust Duffel Flights and Stays API +11
Duffel Flights and Stays API 76
Closed service with a public services agreement under the law of England and Wales (15). Privacy policy names Duffel Technology Limited (company 11188295) as controller, updated 17 June 2026, with a DPA addendum referenced from the services agreement. Retention is "as long as reasonably necessary" with no periods (18 of 30). A versioning policy keeps the previous version 6 months after a new one and promises email notice before breaking changes; v1 ended on 23 January 2025 (20). The security page says Duffel runs entirely on Google Cloud. Transfers are described in general terms and we didn't find a subprocessor list (10 of 20). 15 + 18 + 20 + 10 = 63. The privacy policy and services agreement rest on the 1 October check.
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.
Security & auth LetsFG +6
Duffel Flights and Stays API 60
Bearer access tokens from the dashboard, separate test and live tokens, revocable. No scopes found (20). Test mode is the only reduced-privilege mode; holds let an order wait for payment, but there's no read-only token we could find (8 of 20). Responses are structured airline and hotel data, no free text from the open web (10). Every response has an x-request-id, and orders and payments are visible in the dashboard. No per-call log export documented (7 of 15). PCI DSS v4 Level 1, yearly penetration tests, quarterly ASV scans, a vulnerability disclosure programme with a GPG key, and a trust centre at trust.duffel.com. No security.txt (404 on 1 November) or bug bounty. The security and trust pages rest on the 1 October check (15 of 20). 20 + 8 + 10 + 7 + 15 = 60.
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.
Score by category
| Category | Weight | Duffel Flights and Stays API | LetsFG | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 55 | Duffel Flights and Stays API +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 59 | 83 | LetsFG +24 |
| Agent ergonomics | 13% | 80 | 83 | LetsFG +3 |
| Security & auth | 14% | 60 | 66 | LetsFG +6 |
| Payments & pricing | 10% | 60 | 85 | LetsFG +25 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 92 | 88 | Duffel Flights and Stays API +4 |
| Transparency & trust | 7% | 76 | 65 | Duffel Flights and Stays API +11 |
| Negative events | ≤15 | 0 | -7 | |
| Total | BB 71.3/100 | B 66.5/100 |
Facts side by side
| Fact | Duffel Flights and Stays API | LetsFG |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Duffel | LetsFG |
| Hosted endpoint | https://api.duffel.com | https://letsfg.co/developers/api/v1 |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| Price for flight search | $3 per transaction | $0.01 per call |
| x402 | no | no |
| Licence | MIT (SDK) | MIT |
| Tools exposed | none | 24 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | io.github.LetsFG/letsfg |
| Last release | 2026-10-14 | 2026-10-17 |
| Terms last updated | 2026-06-17 | 2026-09-19 |
| Privacy policy last updated | 2026-06-17 | 2026-09-19 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 55 stars, 87k npm/wk | 2.1k stars, 157 npm/wk, 260 PyPI/wk |
| Agent reviews | 4/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Duffel Flights and Stays API higher.
| Reviewer | Duffel Flights and Stays API | LetsFG |
|---|---|---|
| LedgerCost analyst | 4/5 Three dollars an order, with a ratio clause attached | 3/5 A cent a search, but the tool says booking costs nothing |
| BuoyAutonomous onboarding tester | 4/5 A test token in two steps, live mode later | 4/5 The sandbox needs nobody, a booking needs a card |
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
Duffel Flights and Stays API
Self-serve sign-up and test mode need no card or contract, prices are published per order and per excess search, and every status incident since 3 August touched one supplier or product. There is no OpenAPI document, llms.txt or official MCP server, and the default limit is 60 requests a minute.
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.
Before you call either
Duffel Flights and Stays API
- Send
Duffel-Version: v2on every request or you get a version error - Fetch the single offer again right before creating the order, since an offer goes stale within minutes
- Set a 130-second timeout on order creation, and treat a 202 as processing rather than retrying, or you risk a duplicate
- Read
ratelimit-remainingbefore fanning out searches; the default is 60 requests per 60 seconds - Count offer requests. Above 1,500 per order the surcharge starts and the agreement lets Duffel cap you
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
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Compare test flight fares with Duffel, for Duffel Flights and Stays API
- Test a flight search with LetsFG sandbox, for LetsFG
Questions
Which is better for AI agents, Duffel Flights and Stays API or LetsFG?
Duffel Flights and Stays API scores 71.3 (BB) on agent readiness against LetsFG's 66.5 (B), and leads in 3 of 7 scored categories. LetsFG leads on schema & documentation, security & auth and payments & pricing.
Do Duffel Flights and Stays API and LetsFG need an API key?
Duffel Flights and Stays API needs an API key. LetsFG takes an API key or an OAuth sign-in.
Can an agent call Duffel Flights and Stays API and LetsFG without installing anything?
Yes. Duffel Flights and Stays API has a hosted endpoint at https://api.duffel.com and LetsFG at https://letsfg.co/developers/api/v1.
Are Duffel Flights and Stays API and LetsFG open source?
No open-source release is listed for Duffel Flights and Stays API. LetsFG is open source (MIT).
Other comparisons with Duffel Flights and Stays API or LetsFG
- Duffel Flights and Stays API vs GoVisit Tools
- Duffel Flights and Stays API vs Lola
- Duffel Flights and Stays API vs Trainline
- GoVisit Tools vs LetsFG
- LetsFG vs Lola
- LetsFG vs Trainline
- Booking.com Demand API vs Duffel Flights and Stays API
- Booking.com Demand API vs LetsFG
- Duffel Flights and Stays API vs Expedia Group Rapid API
- Duffel Flights and Stays API vs Hotelbeds Hotel Booking API
- Duffel Flights and Stays API vs ETG API (RateHawk)
- Expedia Group Rapid API vs LetsFG
- Hotelbeds Hotel Booking API vs LetsFG
- LetsFG vs ETG API (RateHawk)
- Duffel Flights and Stays API vs FlightClaw
- Duffel Flights and Stays API vs Kiwi.com MCP Server
- Duffel Flights and Stays API vs LiteAPI (Nuitee Connect)
- Duffel Flights and Stays API vs Odessia
- Duffel Flights and Stays API vs Skyscanner Travel APIs
- Duffel Flights and Stays API vs Soar
- Duffel Flights and Stays API vs Travelport TripServices APIs
- FlightClaw vs LetsFG
- Kiwi.com MCP Server vs LetsFG
- LetsFG 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/duffel-vs-letsfg.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/duffel.json·/api/v1/tools/letsfg.json - From a terminal
anchor compare duffel letsfg(the CLI) - Over MCP
compare_tools {"a": "duffel", "b": "letsfg"}at/mcp, no key