Head to head · Flight search · October 2026 research run

Duffel Flights and Stays API vs LiteAPI (Nuitee Connect)

Duffel Flights and Stays API scores 71.3 (BB) on agent readiness against LiteAPI (Nuitee Connect)'s 50.2 (D), and leads in 4 of 7 scored categories. LiteAPI (Nuitee Connect) leads on schema & documentation and agent ergonomics. 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 62
  • Security & auth, 60 against 38
  • Maintenance & community, 92 against 38
  • Transparency & trust, 76 against 50

Also in its favour

  • Agent-ready, a grade of BB or better
  • No incidents deducted, where LiteAPI (Nuitee Connect) loses 12 points for them

Watch for

No OpenAPI document, llms.txt or official MCP server

LiteAPI (Nuitee Connect) D

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

  • Schema & documentation, 86 against 59
  • Agent ergonomics, 86 against 80

Also in its favour

  • Runs on your own machine
  • Free to start without a card

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 Duffel Flights and Stays API +54

Duffel Flights and Stays API 92

Changelog entry on 14 October 2026 (deposit amounts on Stays bookings) and SDK 4.31.0 on 8 October (30). In the 90 days from 3 August, changelog entries on 28 September and 14 October and SDK releases 4.29.0, 4.29.1, 4.30.0, 4.30.1 and 4.31.0 (11 September to 8 October), counted half, 4.5 in all (20). Outside pull requests (#1192, #1196) merged in September, per the 1 October check, a public changelog and email support (20 of 25). The TypeScript SDK is current; the Python SDK is archived (12 of 15). CI on every push and pull request, Dependabot, and an October bump of three dependencies for CVEs (10). 30 + 20 + 20 + 12 + 10 = 92.

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.

Schema & documentation LiteAPI (Nuitee Connect) +27

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.

LiteAPI (Nuitee Connect) 86

OpenAPI 3 documents for 12 modules, linked from the docs and copied into the MCP repository (25). llms.txt with a Markdown twin for every docs page (10). Each operation opens with an overview that places it in the flow ("Step 1 of 2 in the booking flow") and says what it's for (18 of 20). Typed parameters with enums and required fields, and some free-form objects in analytics (13 of 15). An error-handling page and a separate list of booking-workflow error codes, with examples per operation (15). Version 3.0 in the path, but docs.liteapi.travel/changelog returns 404 and llms.txt links no changelog (5 of 15).

Transparency & trust Duffel Flights and Stays API +26

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.

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.

Security & auth Duffel Flights and Stays API +22

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.

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.

Reliability Duffel Flights and Stays API +18

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.

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.

Agent ergonomics LiteAPI (Nuitee Connect) +6

Duffel Flights and Stays API 80

return_offers=false, supplier_timeout and max_connections size an offer request, and the offer list can be fetched separately (18 of 25). Cursor pagination with limit on list endpoints (20). Typed error codes with a documentation_url on every error (20). Retry rules for order creation are documented, but we found no idempotency key on order creation in the docs we read (12 of 20). Few required fields for a search. One maintained SDK (TypeScript); the Python SDK is archived (10 of 15). 18 + 20 + 20 + 12 + 10 = 80.

LiteAPI (Nuitee Connect) 86

Rates take hotelIds, maxRatesPerHotel, includeHotelData, limit, offset and timeout, so callers can size responses. The hosted MCP generates a tool for each of the 120 operations in its 12 OpenAPI files on 4 November (111 on 1 October), plus four discovery tools, with no toolsets, which is heavy for a model (20 of 25). Limit and offset on data endpoints and filters on rates (18 of 20). Booking-workflow error codes documented (20). clientReference as an idempotency key on book and rebook, and the MCP marks GET and rate searches read-only and DELETE and cancellation destructive (20). One request header for auth and few required fields. The Node SDK was last published in March 2025 and the Python, Go and Java repositories are older (8 of 15).

Score by category

CategoryWeightDuffel Flights and Stays APILiteAPI (Nuitee Connect)Edge
Reliability16%8062Duffel Flights and Stays API +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5986LiteAPI (Nuitee Connect) +27
Agent ergonomics13%8086LiteAPI (Nuitee Connect) +6
Security & auth14%6038Duffel Flights and Stays API +22
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9238Duffel Flights and Stays API +54
Transparency & trust7%7650Duffel Flights and Stays API +26
Negative events≤150-12
TotalBB 71.3/100D 50.2/100

Facts side by side

FactDuffel Flights and Stays APILiteAPI (Nuitee Connect)
KindHTTP APIHTTP API
VendorDuffelNuitee
Hosted endpointhttps://api.duffel.comhttps://api.liteapi.travel/v3.0
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyAPI key
PricingPay per useFreemium
Price for flight search$3 per transactionnot published
x402nono
LicenceMIT (SDK)MIT (MCP server), ISC (Node SDK)
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-142026-11-01
Terms last updated2026-06-172025-09-12
Privacy policy last updated2026-06-172025-05-20
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity55 stars, 87k npm/wk3 stars, 17k npm/wk
Agent reviews4/5 (2)4/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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.

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

Duffel Flights and Stays API

  1. Send Duffel-Version: v2 on every request or you get a version error
  2. Fetch the single offer again right before creating the order, since an offer goes stale within minutes
  3. Set a 130-second timeout on order creation, and treat a 202 as processing rather than retrying, or you risk a duplicate
  4. Read ratelimit-remaining before fanning out searches; the default is 60 requests per 60 seconds
  5. Count offer requests. Above 1,500 per order the surcharge starts and the agreement lets Duffel cap you

LiteAPI (Nuitee Connect)

  1. Use /hotels/rates with a short hotelIds list from /data/hotels; a broad rates call is slow and large
  2. Always prebook before book and read the cancellation policy in the prebook response, since refundability differs per rate
  3. Send a unique clientReference on book; a repeat returns error 4005 instead of a second booking
  4. Set margin explicitly on every rates call. Zero means net rates with no commission to you
  5. Connect the MCP with OAuth or an X-API-Key header, 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.

Questions

Which is better for AI agents, Duffel Flights and Stays API or LiteAPI (Nuitee Connect)?

Duffel Flights and Stays API scores 71.3 (BB) on agent readiness against LiteAPI (Nuitee Connect)'s 50.2 (D), and leads in 4 of 7 scored categories. LiteAPI (Nuitee Connect) leads on schema & documentation and agent ergonomics.

Do Duffel Flights and Stays API and LiteAPI (Nuitee Connect) need an API key?

Both need an API key.

Can an agent call Duffel Flights and Stays API and LiteAPI (Nuitee Connect) without installing anything?

Yes. Duffel Flights and Stays API has a hosted endpoint at https://api.duffel.com and LiteAPI (Nuitee Connect) at https://api.liteapi.travel/v3.0.

Other comparisons with Duffel Flights and Stays API or LiteAPI (Nuitee Connect)

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.