# Expedia Group — API Agent Score

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

Expedia Group scored 65/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 67/100 (C)
- Developer Experience: 51/100 (D)
- Agent Discovery: 62/100 (C)
- Agent Understanding: 67/100 (C)
- Agent Usability: 72/100 (B)

## Check Results

### API Design

- [warn] Schema coverage & depth — 2/8 parameters are deeply nested or free-form maps. Investigated: sdk 96%.
- [warn] Example coverage — README is present but has no runnable quickstart. Investigated: sdk 50%, docs 0%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Changelog published — Newest official SDK activity 4 day(s) ago. Investigated: sdk 100%.
- [warn] Quickstart present — Quickstart page reachable (12 variants scanned starting at https://developers.expediagroup.com/docs/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [warn] Description completeness — 4/8 operations lack a description. Investigated: sdk 50%.
- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (expediagroup/graphql-kotlin, 1216 snippets). Investigated: docs 100%, sdk 75%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — 8 of 9 pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] Crawlable / AEO — Sitemap lastmod coverage 100% or newest entry older than 90 days. Investigated: wellknown 75%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developers.expediagroup.com/docs/llms.txt, https://developers.expediagroup.com/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "ExpediaGroupApiError" with 89 subclasses. Investigated: sdk 100%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/9 tested). Investigated: docs 71%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 2% (threshold 35% for full credit).
- [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 3 assessed pages (3 JS-rendered). Investigated: docs 0%.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Expedia Group's API program shows meaningful strength in description quality and schema design, but two areas are holding back partner and agent adoption: agent understanding (missing machine-readable context files and structured metadata) and developer experience (no self-service portal, no inline code samples). Fixing discoverability and agent context first will unblock AI agents and technical evaluators immediately; layering in runnable collections and tightening security hygiene will then convert that reach into successful, trustworthy integrations at scale.