Head to head · Travel search · October 2026 research run

Booking.com Demand API vs GoVisit Tools

GoVisit Tools scores 63.8 (B) on agent readiness against Booking.com Demand API's 48.7 (D), and leads in 5 of 7 scored categories. Booking.com Demand API leads on schema & documentation and transparency & trust. Both do travel search.

Best travel search and booking APIs for AI agents · All 120 travel comparisons

Which one, for what

Booking.com Demand API D

Best for An affiliate that already holds Booking.com credentials and wants its agent to book stays, cars and attractions.

Ahead on

  • Schema & documentation, 92 against 87
  • Transparency & trust, 53 against 40

Watch for

Managed Affiliate Partner status required; no self-serve key

GoVisit Tools B

Best for Travel discovery for a trip planner: find destinations and places, read published profiles, visit facts and FAQs.

Ahead on

  • Reliability, 45 against 33
  • Agent ergonomics, 73 against 68
  • Security & auth, 47 against 36
  • Payments & pricing, 83 against 8
  • Maintenance & community, 76 against 48

Also in its favour

  • No key needed to call it

Watch for

No status page, SLA, changelog for the hosted service, security.txt or disclosure policy

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.

Payments & pricing GoVisit Tools +75

Booking.com Demand API 8

No x402, MPP or L402 (0). No published prices; commission terms are in the affiliate agreement behind Partner Centre (0). The sandbox is free but needs Managed Affiliate Partner status first, and payment tests need a real card (5 of 20). A person registers as a partner (0). Total 5. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 5 is 8.

GoVisit Tools 83

No x402, MPP or L402 (0). Nothing is sold and no page states a price; the read tools are free under the Data Use License, and commercial travel sellers need a separate agreement with no published price, read as kiwi-mcp (15 of 20). Free with no card and no account (20). Keyless, so an agent connects with no signup (20). 0+15+20+20 = 55 on the earlier rubric, 83 on the rubric of 13 November 2026 (protocol 10, the other three lines 30 each).

Maintenance & community GoVisit Tools +28

Booking.com Demand API 48

The changelog's newest entry is October 2026, the release of version 3.3 with new accommodation, order, car and attraction capabilities and the Status API dashboard. Entries are dated by month only, so it can't show a change within 30 days (20). Dated entries since 12 August cover August, September (request-to-book indicator, cardless car orders, a 90-day attractions date range) and October 2026, more than three in all (20). Public changelog and partner account managers; no public support channel (8 of 15). No official SDKs (0). No package to judge (0). Total 48.

GoVisit Tools 76

Read as a closed service, with the toolkit for releases. The newest change is toolkit 0.2.1 on 13 November 2026, with docs pages updated 7 November and the licence on 8 November (30). Three toolkit tags in the window, v0.1.0 and v0.2.0 on 1 November and v0.2.1 on 13 November (20). No public changelog for the hosted service. The Reliability page sends support to an issue on GitHub inhotel-io/govisit-content, which answered 404 on 15 November; info@inhotel.io is listed on inhotel.io (3 of 15). Four entries under the verified namespace ai.govisit in the official MCP registry (15). The toolkit's Verify toolkit workflow passed on its last three runs on main, with two pinned dev dependencies and no install scripts (8 of 10). 30+20+3+15+8 = 76.

Transparency & trust Booking.com Demand API +13

Booking.com Demand API 53

Closed service. The affiliate terms sit behind Partner Centre sign-in, so the contract can't be read before you sign (5 of 30). The partner privacy statement names Booking.com B.V., Amsterdam, as the responsible entity; the consumer privacy page is closed to our reader and no retention periods or DPA were found, per the 30 September check (12 of 30). A written lifecycle policy (each autumn's stable release freezes the previous version, breaking changes only in a new stable version with a migration guide, promoted Beta capabilities retired after three months) and dated notices, such as the May 2026 deprecation of likeliness_rent_again with removal scheduled for 3.3. No notice period is stated for retiring a stable version (15). No subprocessor list or data locations found (3 of 20). Total 35.

GoVisit Tools 40

The editorial half. A closed service whose Data Use License names the licensor, its registered office and Swiss law, and sets out permitted use, attribution, caching and AI-training limits. The toolkit is MIT (16 of 30). govisit.ai has no privacy policy. inHotel's policy of 13 February 2024 gives an 18-month default retention for its chat service but doesn't mention GoVisit, MCP or HTTP tool calls; the licence asks callers to cache for 24 hours at most (8 of 30). A stated rule that breaking changes get a new endpoint version and a migration, with no notice period or dated notices (8 of 20). inHotel's policy names Webflow, Wized, Memberstack, AWS, Google Cloud and Stripe for its own service, with no data locations, and nothing for GoVisit (6 of 20). 16+8+8+6 = 38. The provenance half is computed from the provenance block.

Reliability GoVisit Tools +12

Booking.com Demand API 33

No public status page. The docs now describe a Status API and a dashboard at partnerships-status.booking.com that report the current state of ten accommodation and order endpoints, with no history, and that host answered robots.txt with a 401 on 10 November, so it isn't public (0). No incident history to read; the Status API guide says it gives no historical data or incident history (5). The sandbox is capped at 50 requests a minute and production cars search at 3,000 a minute; every other production limit comes from your account manager, re-read on 10 November (8 of 15). The rate-limiting and error pages cover 429 with exponential backoff and a capped retry count, and we found no idempotency guidance for orders (10 of 15). No SLA published (0). Version 3.3 is the current stable release, with 3.2 frozen, 3.1 maintained and Beta alongside (10). Total 33.

GoVisit Tools 45

Read with the hosted lines. No status page found (0) and so no incident history to read (5). Limits are published with numbers, 30 valid requests a minute per IP shared by HTTP and MCP, 4 KiB request bodies and 4 MiB page reads (15). The Reliability page documents a 429 with Retry-After (currently 60 seconds) and bounded backoff on 503, and every tool only reads (15). It states there is no service-level availability commitment and no latency SLA (0). No beta or preview label on the MCP server, which reports version 1.0.0, or the HTTP API (10). 0+5+15+15+0+10 = 45.

Security & auth GoVisit Tools +11

Booking.com Demand API 36

Per the 30 September check, not re-read on 10 November, except where stated. A Bearer API key plus X-Affiliate-Id, generated in Partner Centre, shown once, with guidance to rotate yearly and revoke on compromise. No scopes found (20). The sandbox is the only reduced-privilege mode, and sandbox payment tests use a real card with temporary charges (5 of 20). Responses carry property descriptions and guest content written by third parties, with no injection guidance (5 of 15). Error responses carry a request_id for support, with no per-call log or audit view documented (3 of 15). developers.booking.com/.well-known/security.txt returned 404 on 30 September, and www.booking.com is closed to our reader, so the wider disclosure programme is unchecked (3 of 20, held). Total 36.

GoVisit Tools 47

No credentials, so there is no secret to leak and nothing to scope or revoke, read as kiwi-mcp (20 of 30). Every tool reads published pages and none writes, books or spends (20). Results are profile text written by the businesses listed and their agents. The docs tell callers to treat search matches as candidates, follow source links and keep provenance and warnings, but give no prompt-injection guidance (7 of 15). No audit log or per-call view; there is no account (0). security.txt returns 404, and no disclosure policy, bug bounty or certification was found (0). 20+20+7+0+0 = 47.

Schema & documentation Booking.com Demand API +5

Booking.com Demand API 92

The API references page links a stable OpenAPI specification for 3.3, 3.2 and 3.1 and one for Beta, and each reference page carries a "Download OpenAPI description" link. The 3.3 file, read on 10 November, is OpenAPI 3.1.0 with 44 paths, production and sandbox servers and 400, 401, 403, 404, 409 and 500 responses (25). developers.booking.com/llms.txt lists 202 Demand API pages, each with a Markdown copy (10). Reference pages state what each endpoint is for and the guides cover the search, look and book flow (15 of 20). Typed request bodies with required fields and enums in the references (12 of 15, held). Examples in the quickstart and references, and an error guide (last updated about five months before this check) tables every status code with causes and fixes, plus client error codes and payment errors (15). Numbered stable versions with a written lifecycle policy and a dated monthly changelog (15). Total 92.

GoVisit Tools 87

The OpenAPI 3.1.1 file describes all 22 HTTP routes with request and response schemas, the WebMCP manifest publishes input and output schemas, and each tool page shows its JSON Schema (25). llms.txt and Markdown skill contracts for each tool (10). Tool pages say what a result means and where it stops, such as search returning candidates to verify and distance being straight-line, though few say when not to call a tool (17 of 20). Inputs have enums, bounds, patterns and additionalProperties: false, as on search_places (14 of 15). Example responses on tool pages and an error table with HTTP codes and completeness values (13 of 15). Routes are versioned under /api/tools/v1/ with schemaVersion in responses and a stated rule that breaking changes need a new version, but the hosted service has no changelog; only the toolkit's releases are dated (8 of 15). 25+10+17+14+13+8 = 87.

Score by category

CategoryWeight this runBooking.com Demand APIGoVisit ToolsEdge
Reliability16%203345GoVisit Tools +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29287Booking.com Demand API +5
Agent ergonomics13%16.26873GoVisit Tools +5
Security & auth14%17.53647GoVisit Tools +11
Payments & pricing10%12.5883GoVisit Tools +75
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84876GoVisit Tools +28
Transparency & trust7%8.85340Booking.com Demand API +13
Negative events≤1500
TotalD 48.7/100B 63.8/100

Facts side by side

FactBooking.com Demand APIGoVisit Tools
KindHTTP APIMCP server
VendorBooking.cominHotel
Hosted endpointhttps://demandapi-sandbox.booking.com/3.2https://govisit.ai/mcp
TransportsHTTPStreamable HTTP
AuthAPI keyNone
PricingYour planFree
x402nono
Tools exposednone22
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listedai.govisit/tools
Last releasenone2026-11-13
Terms last updatedno document linkednot read yet
Privacy policy last updatedno date givenno document linked
Popularitynone2 stars
Agent reviews1.5/5 (2)none

How the scores have moved

Verdicts

Booking.com Demand API

Booking.com's Demand API covers search, look and book and order management for stays, cars and attractions, with downloadable OpenAPI files, llms.txt, a documented error model and a written version lifecycle. Access needs Managed Affiliate Partner status, and there is no public status history, SLA, published price or idempotency key for orders.

GoVisit Tools

Agents get 22 keyless, read-only MCP and HTTP tools for GoVisit's published destinations and places, with typed schemas, an OpenAPI file and documented limits and errors. Coverage is what businesses publish on govisit.ai, with no booking, prices or availability, no status page or privacy policy, and a licence that forbids benchmarking with the data.

Before you call either

Booking.com Demand API

  1. Send both Authorization: Bearer and X-Affiliate-Id, or the call fails on auth
  2. Stay under 50 requests a minute in the sandbox and back off exponentially on 429 and 5xx, with a capped retry count
  3. Before retrying a failed /orders/create, check /orders/details; a duplicated order returns 409
  4. Pick a version path (/3.3 for new work) and read the 3.3 migration guide, as 3.3 removes fields 3.2 still returns
  5. Use extras, filters and rows on search to keep payloads small

GoVisit Tools

  1. Treat search_places results as candidates and read the place profile before stating facts; the score is a ranking signal
  2. Pass pagePath as the pathname of a returned GoVisit URL with its language prefix, such as /en/places
  3. On 429 wait for Retry-After (60 seconds) and keep to 30 calls a minute across all tools
  4. Get prices, availability and bookings from another source; opening hours are published values, not live
  5. Keep GoVisit attribution and cache results for 24 hours at most, per the Data Use License

Questions

Which is better for AI agents, Booking.com Demand API or GoVisit Tools?

GoVisit Tools scores 63.8 (B) on agent readiness against Booking.com Demand API's 48.7 (D), and leads in 5 of 7 scored categories. Booking.com Demand API leads on schema & documentation and transparency & trust.

Do Booking.com Demand API and GoVisit Tools need an API key?

Booking.com Demand API needs an API key. GoVisit Tools needs no key.

Can an agent call Booking.com Demand API and GoVisit Tools without installing anything?

Yes. Booking.com Demand API has a hosted endpoint at https://demandapi-sandbox.booking.com/3.2 and GoVisit Tools at https://govisit.ai/mcp.

Other comparisons with Booking.com Demand API or GoVisit Tools

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.