# Booking.com — API Agent Score

> Score: 82/100 (Grade: A) | Domain: booking.com | Rubric: 1.0.0 | Checked: July 24, 2026

Booking.com scored 82/100 (A), classified "ai-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/booking)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 82/100 (A)
- Classification: ai-ready

## Category Scores

- API Design: 96/100 (A+)
- Developer Experience: 79/100 (B)
- Agent Discovery: 79/100 (B)
- Agent Understanding: 73/100 (B)
- Agent Usability: 84/100 (A)

## Check Results

### API Design

- [pass] Schema coverage & depth — 289/289 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%, spec 83%.
- [pass] Auth declared & discoverable — authentication documented in the docs site at https://developers.booking.com/connectivity/docs/authentication-best-practices. Investigated: docs 100%, spec 50%.
- [warn] Machine-readable, versioned contract — info.version="1.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 80%, docs 60%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 50%.
- [pass] Example coverage — Code samples present on 3/20 pages across 2 language(s); broader multi-language coverage missing. Investigated: docs 100%, sdk 100%, spec 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://booking.com/signup; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples present on 3/20 pages across 2 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [pass] Description completeness — 50% description completeness. Investigated: spec 100%, sdk 92%.
- [pass] Changelog published — changelog documented in the docs site at https://developers.booking.com/connectivity/docs/changelog/changelog-archive. Investigated: spec 100%, docs 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (wpmanageninja/fluent-booking, 171 snippets). Investigated: docs 100%, sdk 92%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/48 sampled pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 50%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap present (1062 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — error codes documented in the docs site at https://developers.booking.com/connectivity/docs/codes-err. Investigated: docs 100%, sdk 100%, spec 50%.
- [warn] Operation purpose clarity — 83% of operations are agent-inferable (target 90%+). Investigated: spec 90%.
- [warn] Agent-navigable, token-efficient docs — 10 of 47 pages have substantive content differences between markdown and HTML (avg 13% missing). Investigated: docs 56%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 20 sampled pages — likely a CSR-only docs site. Investigated: docs 0%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Rate-limit signaling — rate-limit behavior documented in the docs site at https://developers.booking.com/demand/docs/development-guide/rate-limiting. Investigated: spec 100%, docs 100%.
- [pass] Pagination documented & consistent — pagination documented in the docs site at https://developers.booking.com/demand/docs/development-guide/pagination. Investigated: docs 100%, sdk 67%, spec 63%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%, spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Booking.com's API program shows real strengths in API design and core discoverability, but two areas are holding back partner and agent adoption. The most urgent gaps are in agent understanding — there is no structured agent instruction file or machine-readable doc surface, which means AI coding agents cannot reliably interpret or act on the API without manual effort. Close behind, partners lack a runnable, test-backed collection, so the first call takes far longer than it should and agents have no verified, executable context to build against. Prioritizing these two areas will unlock self-serve partner onboarding and make the API meaningfully usable by AI agents.