# Vodafone — API Agent Score

> Score: 70/100 (Grade: B) | Domain: vodafone.com | Rubric: 1.0.0 | Checked: August 1, 2026

Vodafone scored 70/100 (B), classified "partially-ready".

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

## Summary

- Overall: 70/100 (B)
- Classification: partially-ready

## Category Scores

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

## Check Results

### API Design

- [pass] Schema coverage & depth — package.json "types" → dist/index.d.ts. Investigated: sdk 100%, spec 67%.
- [warn] Machine-readable, versioned contract — info.version="1.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 85%, docs 70%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [warn] Auth declared & discoverable — No securitySchemes declared. Investigated: docs 55%, spec 36%, wellknown 0%.
- [pass] Example coverage — 72% example coverage (target 80%+). Investigated: spec 100%, sdk 50%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://developer.vodafone.com/docs/get-started (CSR-rendered — body classifier inconclusive); free tier / sandbox documented in pricing/docs. Investigated: docs 100%.
- [pass] Description completeness — 35% description completeness. Investigated: spec 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.
- [fail] Changelog published — No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%, sdk 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (chemelli74/aiovodafone, 21 snippets). Investigated: docs 100%, cli 100%, sdk 17%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.vodafone.com/llms.txt, https://developer.vodafone.com/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — No 4xx/5xx response codes (or default error response) documented anywhere in the spec. Investigated: docs 100%, spec 50%.
- [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/1 tested). Investigated: docs 79%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 3 surfaces (spec, docs, sdk) is 3% (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 1 assessed pages (1 JS-rendered). Investigated: docs 0%.

### Agent Usability

- [pass] Pagination documented & consistent — Pagination params detected on 2 list endpoint(s). Investigated: spec 100%, docs 100%.
- [pass] Sandbox separation — Sandbox server declared but no distinguishable test credentials in scheme descriptions. Investigated: spec 100%, docs 100%, sdk 50%.
- [warn] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 40%, docs 40%.
- [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%.

## Executive Summary

Vodafone's API program shows genuine strength in API design — the contract is machine-readable and auth is well-handled — but two areas are holding back partner success. Developer experience is severely undermined by missing onboarding shortcuts and no public changelog, making it hard for partners to get started quickly or trust that they're building against a stable surface. Agent discoverability and understanding are equally weak: without an llms.txt, an AGENTS.md, or structured metadata on the docs, neither human partners nor their AI agents can find or confidently act on Vodafone's APIs without a manual introduction. Prioritizing a discoverable, agent-ready documentation portal with runnable onboarding assets will unlock self-serve partner growth and lay the foundation for AI-native integrations.