# Amadeus — API Agent Score

> Score: 67/100 (Grade: C) | Domain: amadeus.com | Rubric: 1.0.0 | Checked: July 24, 2026

Amadeus scored 67/100 (C), classified "partially-ready".

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

## Summary

- Overall: 67/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 76/100 (B)
- Developer Experience: 65/100 (C)
- Agent Discovery: 67/100 (C)
- Agent Understanding: 80/100 (A)
- Agent Usability: 51/100 (D)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — Versioning declared (info.version="2.9.1") and url-versioning detected. Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — 5 of 19 public signatures use loose types (anyTypeRatio=0.263). Investigated: sdk 86%, spec 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 100%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Auth declared & discoverable — No securitySchemes declared. Investigated: spec 0%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://amadeus.com/signup; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Description completeness — 100% of operations + parameters have substantive descriptions. Investigated: spec 100%, sdk 50%.
- [warn] Quickstart present — Quickstart page reachable (12 variants scanned starting at https://developers.amadeus.com/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Code samples in docs — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.
- [fail] Changelog published — No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/ama_one, 235 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — 32 of 32 pages return 200 for non-existent URLs (soft 404). Investigated: docs 38%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developers.amadeus.com/llms.txt, https://developers.amadeus.com/docs/llms.txt). Investigated: docs 33%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap present (32 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Only 1 distinct 4xx/5xx codes documented (plus 0 "default" catch-all responses). Investigated: spec 100%, docs 100%, sdk 100%.
- [pass] Operation purpose clarity — 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/32 tested). Investigated: docs 86%.
- [warn] Docs structured data — OpenGraph/meta tags only across 20 assessed pages — no JSON-LD for answer engines to cite. Investigated: docs 50%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, sdk) is 4% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.

### Agent Usability

- [pass] Sandbox separation — Sandbox server (https://test.api.amadeus.com/v2) declared in spec with distinguishable test credentials. Investigated: spec 100%, docs 100%, sdk 100%.
- [warn] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 50%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Amadeus demonstrates strong API understanding and documentation quality, but two areas are holding back the partner program: operational reliability for agent-driven integrations is critically incomplete, and the developer onboarding experience lacks the runnable, always-current artifacts partners need to get productive fast. Prioritize closing the agent usability gaps first — idempotency and rate-limit signaling are table-stakes for any partner or AI agent building reliable travel workflows — then shore up the missing changelog, auth discoverability, and code samples that slow partners' path from evaluation to live integration.