Booking.com Partner Hub — can an agent use it?
Booking.com's API is closed to new connectivity partners, blocks all AI crawlers, and renders public pages as JS-only shells — agents cannot find, read, or act on this platform.
FIND & RETRIEVE · 3.2
ACT & TRANSACT · 1.7
TRUST & DURABILITY · 3.0
FIND & RETRIEVE3.2/10Can an agent get correct information?
Machine-readable surface2.5/10
Partner Hub pages are JS-rendered shells (82 words in raw HTML per Site Scan). No llms.txt, no JSON-LD structured data, no markdown negotiation. robots.txt blocks all AI crawlers (GPTBot, ClaudeBot, PerplexityBot all inherit the blanket Disallow: / for unlisted user-agents). Sitemap exists but points to content that is invisible to non-JS crawlers. source
Information retrieval quality3/10
The Partner Hub publishes help articles on pricing strategy (mobile rates, country rates, Genius programme) but not the actual commission rate Booking.com charges partners — that is only visible inside the authenticated Extranet. No public machine-readable pricing, availability, or booking data. An agent cannot answer 'what does it cost to list here?' from the public surface. source
Documentation for machines4/10
A developer portal exists at developers.booking.com with Connectivity API documentation covering Rates & Availability, Reservations, and Connections APIs. However, the documentation is gated behind partner approval and the portal is currently not accepting new registrations. Public-facing doc pages render as mostly CSS/JS with minimal readable content for non-authenticated visitors. source
ACT & TRANSACT1.7/10Can an agent do the job?
Action coverage3.5/10
The Connectivity API covers core actions for property managers: update availability, set rates, manage reservations, and handle guest communications. However, API access is restricted exclusively to approved Connectivity Partners — there is no public API. New partner applications are paused indefinitely. An independent agent or SMB cannot get API credentials. source
Agent protocol support0.5/10
No official MCP server, no entry in the MCP registry, no mention of MCP or any agent protocol anywhere on the Partner Hub or developer portal. No .well-known/mcp.json (returns 403). No community MCP server found. Agent access is only possible through the closed Connectivity Partner programme. source
Access & auth friction1.5/10
API credentials are only granted after a formal multi-stage application process through the Connectivity Partner Programme, which requires a project proposal, approval from Booking.com, and assignment of a dedicated support manager. The programme is currently paused and not accepting new registrations. No self-serve API keys, no OAuth discovery, no sandbox signup. This is the most gated access model in the ARI index. source
Agent payment capability1/10
Booking.com handles guest payments through its own 'Payments by Booking.com' system. No agent payment protocols (ACP, AP2, MPP, x402) are supported. Payouts to property partners are managed internally. An agent cannot initiate, modify, or verify a financial transaction programmatically without being an approved Connectivity Partner. source
Cost & rate fairness2/10
The API itself is free for approved Connectivity Partners (no per-call charges), but the commission Booking.com charges on bookings (typically 15–25%) is not published on any machine-readable surface. Rate limits are undocumented — excessive API calls trigger access suspension. Since access is gated behind partner approval, cost fairness for agents is moot: you cannot reach the API at any price without programme membership. source
TRUST & DURABILITY3.0/10Will it still work next quarter?
Permission & ToS stance2/10
robots.txt blocks all AI crawlers via a blanket Disallow: / for the default user-agent. The Partner Hub terms page returns 404. The Connectivity Partner Programme's terms and conditions are currently being updated, which is the stated reason for pausing new partner applications. Automation is neither explicitly permitted nor prohibited in any publicly accessible document — but the crawler-blocking and closed-API stance signals a hostile posture toward unsanctioned automation. source
Reliability & continuity4/10
No public status page was found at status.partner.booking.com or status.booking.com (DNS does not resolve). The developer portal publishes a Connectivity Public Roadmap, which is a positive transparency signal. The platform itself (booking.com) has been operational for over two decades and is part of Booking Holdings (BKNG), providing strong business continuity. However, the pause on new partner registrations and the terms-update limbo introduce uncertainty about API stability for new entrants. source
Sources
Point-in-time assessment — services change terms, prices and APIs often. That volatility is itself scored under Reliability & continuity. Re-verified at least quarterly.
- partner.booking.com/en-gb — Partner Hub home page (accessed 2026-09-23)
- partner.booking.com/en-gb/pricing — Pricing help articles (not actual commission rates) (accessed 2026-09-23)
- partner.booking.com/robots.txt — robots.txt — blanket Disallow: / for unlisted bots, blocks all AI crawlers (accessed 2026-09-23)
- partner.booking.com/sitemap.xml — Sitemap index, 30 locale sub-sitemaps (accessed 2026-09-23)
- developers.booking.com/connectivity/docs — Connectivity API documentation portal (gated) (accessed 2026-09-23)
- connectivity.booking.com/s — Connectivity Partner Programme — currently paused for new registrations (accessed 2026-09-23)
- developers.booking.com/connectivity/roadmap — Public roadmap for Connectivity APIs (accessed 2026-09-23)
- elfsight.com/blog/how-to-get-and-use-booking-com-ap… — Third-party guide on API access requirements (2026) (accessed 2026-09-23)