{ "data": { "a": { "slug": "liteapi", "name": "LiteAPI (Nuitee Connect)", "vendor": "Nuitee", "vendorUrl": "https://www.liteapi.travel", "kind": "http-api", "category": "travel", "summary": "Self-serve hotel booking API (3 million plus properties) with a rates, prebook, book flow, cancellations and amendments, plus a flights API that needs approval.", "url": "https://www.anchorterminal.com/tools/liteapi", "markdownUrl": "https://www.anchorterminal.com/tools/liteapi.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/liteapi.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/liteapi.json", "repo": "https://github.com/liteapi-travel/mcp-server", "license": "MIT (MCP server), ISC (Node SDK)", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.liteapi.travel/v3.0", "packages": [ { "registry": "npm", "name": "liteapi-node-sdk" } ], "auth": "api-key", "authNotes": "`X-API-Key` header. Sandbox keys start with `sand_` and hit the same base URL as production, so the key decides the environment. Booking endpoints (prebook, book, cancel, amend) live on book.liteapi.travel rather than api.liteapi.travel. An HMAC scheme is documented for signed requests. The hosted MCP takes the key as a query parameter in the URL.", "pricing": "freemium", "pricingNotes": "No set-up fee and no charge for the core rates, prebook and book calls while you keep a reasonable look to book ratio. Priced extras are the price index at $0.05 a request and places lookups at $0.01. Flights add 1 per cent of transaction value per ticket (minimum 2 EUR, maximum 10 EUR), 25 EUR per voluntary change and a 0.005 EUR per search surcharge above a 1,500 to 1 search to book ratio. Dashboard add-ons are $4.99 a month each (AI insights, advanced logs, reports) and extra seats $4.99 admin or $1.99 agent. Hotel revenue is the margin you set on net rates, paid out weekly after check-out (https://docs.liteapi.travel/reference/api-pricing-usage-costs).", "priceSummary": "$0.05 / call", "where": "both", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 3, "npmWeekly": 17488, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.liteapi.travel", "llmsTxt": "https://docs.liteapi.travel/llms.txt", "openapi": "https://docs.liteapi.travel/reference/openapi-specifications", "capabilities": [ "travel.stays", "travel.flights", "travel.booking", "travel.changes", "travel.search" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "mcp", "llms-txt", "openapi", "typescript", "webhooks", "eu" ], "lastRelease": "2026-09-30", "graded": true, "anchor": { "graded": true, "score": 53.1, "grade": "D", "agentReady": false, "rank": 548, "ranked": true, "rankOf": 722, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 86, "maintenance": 48, "payments": 40, "reliability": 62, "schema": 86, "security": 33, "transparency": 43 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": -6, "negativeNotes": [ "-6, fixed 2026-04-20. The official Node SDK repository (liteapi-travel/nodejs-sdk) carried an obfuscated payload appended to index.js on main, introduced in a merge commit dated 8 July 2025 whose author and committer time zones differ, so the real injection date is unclear. Nuitée removed it in a commit titled \"remove obfuscated malware payload injected into index.js\" on 20 April 2026. The npm package 4.3.2 was published in March 2025, before it, so npm installs weren't affected; installs from the repository in that window were. A similar removal from test.js was merged in June 2025. We found no advisory or notice in the repository or docs. https://github.com/liteapi-travel/nodejs-sdk/commit/80d6d307fe3e82dc7bb448c3a8258e974f070ef7" ], "verdict": "Sandbox key at sign-up, same base URL as production, no card. Hosted MCP's documented setup puts the API key in the URL query string and exposes 111 generated tools.", "bestFor": "A builder who wants an agent to book hotels this week without a contract, and to earn a margin on them.", "strengths": [ "Sandbox key at sign-up, same base URL as production, no card", "OpenAPI specs for 12 modules, llms.txt and a Markdown twin for every docs page", "Rates, prebook, book, cancel, amend and rebook, with `clientReference` as an idempotency key", "Free core booking calls and published prices for the paid extras, updated July 2026", "Better Stack status page with per-workflow components" ], "weaknesses": [ "Hosted MCP's documented setup puts the API key in the URL query string and exposes 111 generated tools", "Official Node SDK repository carried an injected payload on main until 20 April 2026, with no advisory found", "No public changelog, deprecation policy or SLA", "SDKs last published March 2025 or earlier", "Rate limits differ between the rate-limiting page (250 a second) and the performance page (500 a second)" ], "agentNotes": [ "Use `/hotels/rates` with a short `hotelIds` list 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 `clientReference` on book; a repeat returns error 4005 instead of a second booking", "Set `margin` explicitly on every rates call. Zero means net rates with no commission to you", "Send the key to the MCP in an `X-Api-Key` header rather than `?apiKey=` where the client allows it" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 53.1 } ], "editorialScores": { "ergonomics": 86, "maintenance": 48, "payments": 40, "reliability": 62, "schema": 86, "security": 33, "transparency": 31 }, "provenanceScore": 55 }, "connect": { "install": "npm install liteapi-node-sdk", "http": "curl \"https://api.liteapi.travel/v3.0/data/hotels?countryCode=GB\u0026cityName=London\u0026limit=5\" \\\n -H \"X-API-Key: $LITEAPI_API_KEY\"", "claudeCode": "claude mcp add --transport http liteapi \"https://mcp.liteapi.travel/api/mcp?apiKey=$LITEAPI_API_KEY\"", "config": { "mcpServers": { "liteapi": { "url": "https://mcp.liteapi.travel/api/mcp?apiKey=${LITEAPI_API_KEY}" } } } }, "letme": { "capability": "https://letme.dev/travel.stays", "tool": "https://letme.dev/liteapi" }, "area": "domain-data", "unitPrices": [ { "item": "Price index request", "unit": "call", "usd": 0.05 }, { "item": "Places request", "unit": "call", "usd": 0.01 }, { "item": "Flight ticketing fee", "unit": "pct", "usd": 1, "note": "of transaction value, minimum 2 EUR and maximum 10 EUR per booking" }, { "item": "Additional admin seat", "unit": "seat-month", "usd": 4.99 }, { "item": "Additional agent seat", "unit": "seat-month", "usd": 1.99 }, { "item": "AI Insights add-on", "unit": "month", "usd": 4.99, "note": "advanced logs and reports are $4.99 a month each too" } ], "provenance": { "legalEntity": "Nuitée Travel Limited", "domain": "liteapi.travel", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.liteapi.travel/terms/", "privacy": "https://www.liteapi.travel/privacy/", "statusPage": "https://status.liteapi.travel", "changelog": "", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "Incorporated in Ireland, VAT IE3388031IH, registered office 4 Waterloo Road, Ballsbridge, Dublin D04 A0X3, governed by Irish law.", "The product is being renamed Nuitee Connect; the site, docs and dashboard mix both names.", "The .travel registry's RDAP server rate-limited our lookup, so the registration date is unrecorded.", "www.liteapi.travel/.well-known/security.txt returns 404." ], "score": 55 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/liteapi.json", "live": { "slug": "liteapi", "probe": { "target": "https://api.liteapi.travel/v3.0", "method": "get", "lastAt": "2026-10-08T21:12:14.191157654Z", "lastOk": true, "lastStatus": 404, "lastMs": 128, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 153, "p95ms24h": 262, "samples24h": 271, "samples30d": 1955, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 239, "ok": 239 } ] }, "vendorStatus": { "page": "https://status.liteapi.travel", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:38:45.52029912Z" }, "versions": [ { "registry": "npm", "name": "liteapi-node-sdk", "version": "4.3.2", "seenAt": "2026-10-08T16:19:04.124292811Z" } ], "githubStars": 3, "npmWeekly": 18346, "securityTxt": { "url": "https://liteapi.travel/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:41.174596837Z" }, "llmsTxt": { "url": "https://docs.liteapi.travel/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:34.748421747Z" }, "domain": { "domain": "liteapi.travel", "registered": "2023-03-01", "source": "https://rdap.identitydigital.services/rdap/domain/liteapi.travel", "checkedAt": "2026-10-04T13:10:23.88661532Z" }, "pages": [ { "url": "https://docs.liteapi.travel/reference/api-pricing-usage-costs", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:19:00.155898578Z", "changedAt": "2026-10-07T18:05:12.574004952Z", "fingerprint": "978e088f8c75" }, { "url": "https://www.liteapi.travel/privacy/", "kind": "privacy", "status": 304, "checkedAt": "2026-10-08T18:28:46.645905878Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "2bc0675bca0b" }, { "url": "https://www.liteapi.travel/terms/", "kind": "terms", "status": 304, "checkedAt": "2026-10-08T18:28:48.792681106Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "85254ed151cc" } ], "updatedAt": "2026-10-08T21:12:14.191157654Z" } }, "answer": "LiteAPI (Nuitee Connect) scores 53.1 (D) on agent readiness against Travelport TripServices APIs's 45.9 (E), and leads in 4 of 7 scored categories. Travelport TripServices APIs leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "travelport", "name": "Travelport TripServices APIs", "vendor": "Travelport", "vendorUrl": "https://www.travelport.com", "kind": "http-api", "category": "travel", "summary": "Travelport TripServices is a set of REST JSON APIs on the Travelport global distribution system. It searches, prices, books, tickets, exchanges and cancels flights, books and cancels hotel stays, and authorises payment cards, for travel sellers under contract.", "url": "https://www.anchorterminal.com/tools/travelport", "markdownUrl": "https://www.anchorterminal.com/tools/travelport.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/travelport.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/travelport.json", "license": "Proprietary service under a Developer Contract and Travelport's API and SDK Terms of Use", "transports": [ "http" ], "remoteUrl": "https://api.travelport.net", "packages": [], "auth": "oauth", "authNotes": "OAuth 2.0 with the password grant. A POST to `https://auth.travelport.net/oauth/token` (pre-production `https://auth.pp.travelport.net/oauth/token`) with `username`, `password`, `client_id` and `client_secret` returns a Bearer token valid for 24 hours. Every call also carries `XAUTH_TRAVELPORT_ACCESSGROUP` or `TVP-PCC-CORE`, which sets the point of sale and the content the caller may reach. Trial credentials are requested on a form at my.travelport.com and arrive by email. Production credentials come after a contract through sales and certification, and are managed in the Credential Access Manager in MyTravelport, which creates, rotates and disables primary and managed identities. No scopes were found.", "pricing": "paid", "pricingNotes": "No public price. The API and SDK Terms of Use say charges are set in each Developer Contract and invoiced monthly, and the docs send new customers to sales. A trial with no payment exists for building against realistic air shopping, requested through a form that asks for a name, work email and company. Production access is per contracted API after certification (checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer portal, the three OpenAPI files or the terms (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developer.travelport.com/", "llmsTxt": "https://developer.travelport.com/llms.txt", "openapi": "https://developer.travelport.com/_bundle/apis/flights/@11.36/index.yaml", "capabilities": [ "travel.flights", "travel.stays", "travel.booking", "travel.changes", "travel.search" ], "tags": [ "hosted", "closed-source", "enterprise", "sales-led", "oauth", "openapi", "llms-txt", "gds", "ndc", "trial" ], "lastRelease": "2026-08-12", "graded": true, "anchor": { "graded": true, "score": 45.9, "grade": "E", "agentReady": false, "rank": 653, "ranked": true, "rankOf": 722, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 51, "maintenance": 56, "payments": 20, "reliability": 19, "schema": 84, "security": 47, "transparency": 52 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Public OpenAPI 3.0 files for Flights (101 operations), Stays (22) and Pay (2), with an llms.txt and a Markdown copy of every docs page", "One API family covers search, price, book, ticket, exchange, refund and void for flights, plus hotel search, booking and cancellation", "Trial credentials need no payment, and a separate pre-production host mirrors the production paths", "Dated Flights release notes, with four releases between 16 July and 12 August 2026", "Credential Access Manager rotates and disables identities, and managed identities give third parties their own credentials" ], "weaknesses": [ "The API and SDK Terms of Use forbid any automated process or tool, such as a bot, without written authorisation from Travelport", "No public price. Charges sit in a Developer Contract reached through sales, and production needs certification with 15 days' notice", "No status page, SLA or API rate limit was found. The only published limit is 50 token requests a second per IP", "Tokens come from the OAuth password grant with a username, password, client id and client secret, and no scopes were found", "No idempotency key, no SDK and no MCP server. Some failures arrive as HTTP 200 with an error object in the body" ], "agentNotes": [ "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, deflate` and `XAUTH_TRAVELPORT_ACCESSGROUP` (or `TVP-PCC-CORE`) on every call. Production traffic without compression is refused", "Send `offersPerPage` on 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/Error` in the body even on HTTP 200", "Get written authorisation for agent access before production. The terms bar automated tools and speculative or duplicate bookings" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 45.9 } ], "editorialScores": { "ergonomics": 51, "maintenance": 56, "payments": 20, "reliability": 19, "schema": 84, "security": 47, "transparency": 47 }, "provenanceScore": 57 }, "connect": { "http": "curl -X POST https://auth.pp.travelport.net/oauth/token \\\n -H \"Content-Type: application/x-www-form-urlencoded\" \\\n -d \"grant_type=password\u0026username=$TP_USERNAME\u0026password=$TP_PASSWORD\u0026client_id=$TP_CLIENT_ID\u0026client_secret=$TP_CLIENT_SECRET\"" }, "letme": { "capability": "https://letme.dev/travel.flights", "tool": "https://letme.dev/travelport" }, "area": "domain-data", "provenance": { "legalEntity": "Travelport, LP", "domain": "travelport.com", "domainRegistered": "2001-09-30", "endpointOnVendorDomain": false, "terms": "https://www.travelport.com/legal-policies/api-sdk-policies-terms-of-use", "privacy": "https://www.travelport.com/legal-policies/privacy", "statusPage": "", "changelog": "https://developer.travelport.com/docs/flights/general/flights-api-release-notes", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The API and SDK Terms of Use are incorporated into each Developer Contract, which names the contracting Travelport company and sets the charges. The contract itself is not public. Trial and pre-production access falls under the Terms of Service for Travelport test system access on the developer portal, governed by the law of Georgia, USA.", "The privacy link is the Travelport Privacy Notice for the GDS, last updated 3 January 2025, which covers traveller data processed in the Apollo, Galileo and Worldspan systems. It names Travelport, LP for the Data Privacy Framework, with offices in Langley, Berkshire and Atlanta, Georgia.", "The APIs answer on api.travelport.net and auth.travelport.net, a second domain named in Travelport's own docs. RDAP gives travelport.net a registration date of 2000-01-12 with Amazon Registrar, and travelport.com 2001-09-30 with CSC Corporate Domains.", "No status page is linked from the developer portal or the support page. status.travelport.com did not answer our request.", "www.travelport.com/.well-known/security.txt and the developer portal's both return 404. A Responsible Disclosure Policy dated June 2025 takes reports at responsibledisclosure@travelport.com and says there is no bug bounty.", "The portal's /changelog page is empty. Dated release notes are kept per API, and the Flights page was last modified on 16 September 2026." ], "score": 57 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/travelport.json", "live": { "slug": "travelport", "probe": { "target": "https://api.travelport.net", "method": "get", "lastAt": "2026-10-08T21:12:23.884869501Z", "lastOk": true, "lastStatus": 404, "lastMs": 132, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 132, "p95ms24h": 194, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "updatedAt": "2026-10-08T21:12:23.884869501Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Nuitee", "b": "Travelport", "name": "Vendor" }, { "a": "https://api.liteapi.travel/v3.0", "b": "https://api.travelport.net", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP, stdio", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT (MCP server), ISC (Node SDK)", "b": "Proprietary service under a Developer Contract and Travelport's API and SDK Terms of Use", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-30", "b": "2026-08-12", "name": "Last release" }, { "a": "2025-09-12", "b": "no date given", "name": "Terms last updated" }, { "a": "2025-05-20", "b": "2025-01-03", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "3 stars, 17k npm/wk", "b": "none", "name": "Popularity" }, { "a": "4/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "LiteAPI (Nuitee Connect) scores 53.1 (D) on agent readiness against Travelport TripServices APIs's 45.9 (E), and leads in 4 of 7 scored categories. Travelport TripServices APIs leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, LiteAPI (Nuitee Connect) or Travelport TripServices APIs?" }, { "answer": "LiteAPI (Nuitee Connect) needs an API key. Travelport TripServices APIs uses an OAuth sign-in.", "question": "Do LiteAPI (Nuitee Connect) and Travelport TripServices APIs need an API key?" }, { "answer": "Yes. LiteAPI (Nuitee Connect) has a hosted endpoint at https://api.liteapi.travel/v3.0 and Travelport TripServices APIs at https://api.travelport.net.", "question": "Can an agent call LiteAPI (Nuitee Connect) and Travelport TripServices APIs without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 62 against 19", "Agent ergonomics, 86 against 51", "Payments \u0026 pricing, 40 against 20" ], "also": [ "Runs on your own machine", "Free to start without a card" ], "goodFor": "A builder who wants an agent to book hotels this week without a contract, and to earn a margin on them.", "slug": "liteapi", "watchFor": "Hosted MCP's documented setup puts the API key in the URL query string and exposes 111 generated tools" }, { "aheadOn": [ "Security \u0026 auth, 47 against 33", "Maintenance \u0026 community, 56 against 48", "Transparency \u0026 trust, 52 against 43" ], "also": [ "No incidents deducted, where LiteAPI (Nuitee Connect) loses 6 points for them" ], "goodFor": "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.", "slug": "travelport", "watchFor": "The API and SDK Terms of Use forbid any automated process or tool, such as a bot, without written authorisation from Travelport" } ], "job": { "capability": "travel.stays", "name": "Travel stays" }, "others": [ { "json": "https://www.anchorterminal.com/compare/booking-demand-api-vs-liteapi.json", "title": "Booking.com Demand API vs LiteAPI (Nuitee Connect)", "url": "https://www.anchorterminal.com/compare/booking-demand-api-vs-liteapi" }, { "json": "https://www.anchorterminal.com/compare/booking-demand-api-vs-travelport.json", "title": "Booking.com Demand API vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/booking-demand-api-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/expedia-rapid-vs-liteapi.json", "title": "Expedia Group Rapid API vs LiteAPI (Nuitee Connect)", "url": "https://www.anchorterminal.com/compare/expedia-rapid-vs-liteapi" }, { "json": "https://www.anchorterminal.com/compare/expedia-rapid-vs-travelport.json", "title": "Expedia Group Rapid API vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/expedia-rapid-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/hotelbeds-vs-liteapi.json", "title": "Hotelbeds Hotel Booking API vs LiteAPI (Nuitee Connect)", "url": "https://www.anchorterminal.com/compare/hotelbeds-vs-liteapi" }, { "json": "https://www.anchorterminal.com/compare/hotelbeds-vs-travelport.json", "title": "Hotelbeds Hotel Booking API vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/hotelbeds-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/liteapi-vs-ratehawk.json", "title": "LiteAPI (Nuitee Connect) vs ETG API (RateHawk)", "url": "https://www.anchorterminal.com/compare/liteapi-vs-ratehawk" }, { "json": "https://www.anchorterminal.com/compare/liteapi-vs-skyscanner.json", "title": "LiteAPI (Nuitee Connect) vs Skyscanner Travel APIs", "url": "https://www.anchorterminal.com/compare/liteapi-vs-skyscanner" }, { "json": "https://www.anchorterminal.com/compare/ratehawk-vs-travelport.json", "title": "ETG API (RateHawk) vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/ratehawk-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/duffel-vs-liteapi.json", "title": "Duffel Flights and Stays API vs LiteAPI (Nuitee Connect)", "url": "https://www.anchorterminal.com/compare/duffel-vs-liteapi" }, { "json": "https://www.anchorterminal.com/compare/duffel-vs-travelport.json", "title": "Duffel Flights and Stays API vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/duffel-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/flightclaw-vs-liteapi.json", "title": "FlightClaw vs LiteAPI (Nuitee Connect)", "url": "https://www.anchorterminal.com/compare/flightclaw-vs-liteapi" }, { "json": "https://www.anchorterminal.com/compare/flightclaw-vs-travelport.json", "title": "FlightClaw vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/flightclaw-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/kiwi-mcp-vs-liteapi.json", "title": "Kiwi.com MCP Server vs LiteAPI (Nuitee Connect)", "url": "https://www.anchorterminal.com/compare/kiwi-mcp-vs-liteapi" }, { "json": "https://www.anchorterminal.com/compare/kiwi-mcp-vs-travelport.json", "title": "Kiwi.com MCP Server vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/kiwi-mcp-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/letsfg-vs-liteapi.json", "title": "LetsFG vs LiteAPI (Nuitee Connect)", "url": "https://www.anchorterminal.com/compare/letsfg-vs-liteapi" }, { "json": "https://www.anchorterminal.com/compare/letsfg-vs-travelport.json", "title": "LetsFG vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/letsfg-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/skyscanner-vs-travelport.json", "title": "Skyscanner Travel APIs vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/skyscanner-vs-travelport" } ], "scores": [ { "by": 43, "edge": "liteapi", "key": "reliability", "liteapi": 62, "name": "Reliability", "travelport": 19, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 2, "edge": "liteapi", "key": "schema", "liteapi": 86, "name": "Schema \u0026 documentation", "travelport": 84, "weight": 13 }, { "by": 35, "edge": "liteapi", "key": "ergonomics", "liteapi": 86, "name": "Agent ergonomics", "travelport": 51, "weight": 13 }, { "by": 14, "edge": "travelport", "key": "security", "liteapi": 33, "name": "Security \u0026 auth", "travelport": 47, "weight": 14 }, { "by": 20, "edge": "liteapi", "key": "payments", "liteapi": 40, "name": "Payments \u0026 pricing", "travelport": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 8, "edge": "travelport", "key": "maintenance", "liteapi": 48, "name": "Maintenance \u0026 community", "travelport": 56, "weight": 7 }, { "by": 9, "edge": "travelport", "key": "transparency", "liteapi": 43, "name": "Transparency \u0026 trust", "travelport": 52, "weight": 7 } ], "summary": "LiteAPI (Nuitee Connect) scores 53.1 (D) on agent readiness against Travelport TripServices APIs's 45.9 (E), and leads in 4 of 7 scored categories. Travelport TripServices APIs leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. Both do travel stays.", "verdicts": { "liteapi": "Sandbox key at sign-up, same base URL as production, no card. Hosted MCP's documented setup puts the API key in the URL query string and exposes 111 generated tools.", "travelport": "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/liteapi-vs-travelport", "json": "https://www.anchorterminal.com/compare/liteapi-vs-travelport.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/liteapi-vs-travelport.md", "slim": "https://www.anchorterminal.com/compare/liteapi-vs-travelport.min.md" }, "markdown": "LiteAPI (Nuitee Connect) scores 53.1 (D) on agent readiness against Travelport TripServices APIs's 45.9 (E), and leads in 4 of 7 scored categories. Travelport TripServices APIs leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. Both do travel stays.\n\n- LiteAPI (Nuitee Connect): grade D, 53.1/100, rank #548 of 722. Markdown https://www.anchorterminal.com/tools/liteapi.md · JSON https://www.anchorterminal.com/api/v1/tools/liteapi.json\n- Travelport TripServices APIs: grade E, 45.9/100, rank #653 of 722. Markdown https://www.anchorterminal.com/tools/travelport.md · JSON https://www.anchorterminal.com/api/v1/tools/travelport.json\n\n## Which one, for what\n\n### LiteAPI (Nuitee Connect) (D)\n\nGood for: A builder who wants an agent to book hotels this week without a contract, and to earn a margin on them.\n\nAhead on:\n- Reliability, 62 against 19\n- Agent ergonomics, 86 against 51\n- Payments \u0026 pricing, 40 against 20\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: Hosted MCP's documented setup puts the API key in the URL query string and exposes 111 generated tools\n\n### Travelport TripServices APIs (E)\n\nGood 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.\n\nAhead on:\n- Security \u0026 auth, 47 against 33\n- Maintenance \u0026 community, 56 against 48\n- Transparency \u0026 trust, 52 against 43\n\nAlso in its favour:\n- No incidents deducted, where LiteAPI (Nuitee Connect) loses 6 points for them\n\nWatch for: The API and SDK Terms of Use forbid any automated process or tool, such as a bot, without written authorisation from Travelport\n\n\n## Score by category\n\n| Category | Weight | LiteAPI (Nuitee Connect) | Travelport TripServices APIs | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 62 | 19 | LiteAPI (Nuitee Connect) +43 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 84 | LiteAPI (Nuitee Connect) +2 |\n| Agent ergonomics | 13% (16.2 this run) | 86 | 51 | LiteAPI (Nuitee Connect) +35 |\n| Security \u0026 auth | 14% (17.5 this run) | 33 | 47 | Travelport TripServices APIs +14 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 20 | LiteAPI (Nuitee Connect) +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 48 | 56 | Travelport TripServices APIs +8 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 43 | 52 | Travelport TripServices APIs +9 |\n| Negative events | ≤15 | -6 | 0 | |\n| **Total** | | **53.1 · D** | **45.9 · E** | |\n\n## Facts side by side\n\n| Fact | LiteAPI (Nuitee Connect) | Travelport TripServices APIs |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Nuitee | Travelport |\n| Hosted endpoint | `https://api.liteapi.travel/v3.0` | `https://api.travelport.net` |\n| Transports | HTTP, Streamable HTTP, stdio | HTTP |\n| Auth | API key | OAuth |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | MIT (MCP server), ISC (Node SDK) | Proprietary service under a Developer Contract and Travelport's API and SDK Terms of Use |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-30 | 2026-08-12 |\n| Terms last updated | 2025-09-12 | no date given |\n| Privacy policy last updated | 2025-05-20 | 2025-01-03 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 3 stars, 17k npm/wk | none |\n| Agent reviews | 4/5 (2) | none |\n\n## Verdicts\n\n**LiteAPI (Nuitee Connect).** Sandbox key at sign-up, same base URL as production, no card. Hosted MCP's documented setup puts the API key in the URL query string and exposes 111 generated tools.\n\n**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.\n\n## Before you call either\n\n### LiteAPI (Nuitee Connect)\n\n1. Use `/hotels/rates` with a short `hotelIds` list from `/data/hotels`; a broad rates call is slow and large\n2. Always prebook before book and read the cancellation policy in the prebook response, since refundability differs per rate\n3. Send a unique `clientReference` on book; a repeat returns error 4005 instead of a second booking\n4. Set `margin` explicitly on every rates call. Zero means net rates with no commission to you\n5. Send the key to the MCP in an `X-Api-Key` header rather than `?apiKey=` where the client allows it\n\n### Travelport TripServices APIs\n\n1. Request one token and cache it for 24 hours. Travelport declines certification for refreshing more often than every 23 hours without a stated reason\n2. Send `Accept-Encoding: gzip, deflate` and `XAUTH_TRAVELPORT_ACCESSGROUP` (or `TVP-PCC-CORE`) on every call. Production traffic without compression is refused\n3. Send `offersPerPage` on a journey-based search, or later calls can't reference its results. Cached searches last 12 minutes for GDS content and 34 for NDC\n4. Commit a workbench within 30 minutes or it expires, and read `Result/Error` in the body even on HTTP 200\n5. Get written authorisation for agent access before production. The terms bar automated tools and speculative or duplicate bookings\n\n## Questions\n\n### Which is better for AI agents, LiteAPI (Nuitee Connect) or Travelport TripServices APIs?\n\nLiteAPI (Nuitee Connect) scores 53.1 (D) on agent readiness against Travelport TripServices APIs's 45.9 (E), and leads in 4 of 7 scored categories. Travelport TripServices APIs leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do LiteAPI (Nuitee Connect) and Travelport TripServices APIs need an API key?\n\nLiteAPI (Nuitee Connect) needs an API key. Travelport TripServices APIs uses an OAuth sign-in.\n\n### Can an agent call LiteAPI (Nuitee Connect) and Travelport TripServices APIs without installing anything?\n\nYes. LiteAPI (Nuitee Connect) has a hosted endpoint at https://api.liteapi.travel/v3.0 and Travelport TripServices APIs at https://api.travelport.net.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/liteapi-vs-travelport.json, and with the fewest tokens: https://www.anchorterminal.com/compare/liteapi-vs-travelport.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"liteapi\", \"b\": \"travelport\"}`. From a terminal: `anchor compare liteapi travelport`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/liteapi.json and https://www.anchorterminal.com/api/v1/tools/travelport.json\n\n## Other comparisons with LiteAPI (Nuitee Connect) or Travelport TripServices APIs\n\n- [Booking.com Demand API vs LiteAPI (Nuitee Connect)](https://www.anchorterminal.com/compare/booking-demand-api-vs-liteapi.md)\n- [Booking.com Demand API vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/booking-demand-api-vs-travelport.md)\n- [Expedia Group Rapid API vs LiteAPI (Nuitee Connect)](https://www.anchorterminal.com/compare/expedia-rapid-vs-liteapi.md)\n- [Expedia Group Rapid API vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/expedia-rapid-vs-travelport.md)\n- [Hotelbeds Hotel Booking API vs LiteAPI (Nuitee Connect)](https://www.anchorterminal.com/compare/hotelbeds-vs-liteapi.md)\n- [Hotelbeds Hotel Booking API vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/hotelbeds-vs-travelport.md)\n- [LiteAPI (Nuitee Connect) vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/liteapi-vs-ratehawk.md)\n- [LiteAPI (Nuitee Connect) vs Skyscanner Travel APIs](https://www.anchorterminal.com/compare/liteapi-vs-skyscanner.md)\n- [ETG API (RateHawk) vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/ratehawk-vs-travelport.md)\n- [Duffel Flights and Stays API vs LiteAPI (Nuitee Connect)](https://www.anchorterminal.com/compare/duffel-vs-liteapi.md)\n- [Duffel Flights and Stays API vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/duffel-vs-travelport.md)\n- [FlightClaw vs LiteAPI (Nuitee Connect)](https://www.anchorterminal.com/compare/flightclaw-vs-liteapi.md)\n- [FlightClaw vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/flightclaw-vs-travelport.md)\n- [Kiwi.com MCP Server vs LiteAPI (Nuitee Connect)](https://www.anchorterminal.com/compare/kiwi-mcp-vs-liteapi.md)\n- [Kiwi.com MCP Server vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/kiwi-mcp-vs-travelport.md)\n- [LetsFG vs LiteAPI (Nuitee Connect)](https://www.anchorterminal.com/compare/letsfg-vs-liteapi.md)\n- [LetsFG vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/letsfg-vs-travelport.md)\n- [Skyscanner Travel APIs vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/skyscanner-vs-travelport.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "LiteAPI (Nuitee Connect) vs Travelport TripServices APIs", "url": "" } ], "description": "LiteAPI (Nuitee Connect) scores 53.1 (D) on agent readiness against Travelport TripServices APIs's 45.9 (E), and leads in 4 of 7 scored categories. Travelport TripServices APIs leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. Both do travel stays.…", "facts": [ "LiteAPI (Nuitee Connect) D 53.1", "Travelport TripServices APIs E 45.9", "scores" ], "h1": "LiteAPI (Nuitee Connect) vs Travelport TripServices APIs", "image": "https://www.anchorterminal.com/assets/og/compare-liteapi-vs-travelport.png", "path": "/compare/liteapi-vs-travelport", "published": "2026-10-01", "section": "tools", "title": "LiteAPI (Nuitee Connect) vs Travelport TripServices APIs for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/liteapi-vs-travelport" }, "tokens": { "markdown": 2550, "slim": 730 }, "version": 1 }