Vodafonevodafone.com

ScoredAug 1, 2026, 08:22 AM

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.

API DesignA clean, typed, well-governed API contract agents can reason about3 pass2 warn0 fail87A

Signal	Points	Findings	Rationale
Schema coverage & depthvia sdk	25/25	package.json "types" → dist/index.d.ts. Investigated: sdk 100%, spec 67%.	Typed, complete request/response schemas are what make agent function-calling possible.
Machine-readable, versioned contractvia spec	21.3/25	info.version="1.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 85%, docs 70%.	A current OpenAPI version with a declared versioning scheme lets agents reason about the contract.
Security & governance hygienevia spec	15/15	No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.	No leaked secrets, no critical lint violations, no OWASP API Top-10 spec smells, and a published vulnerability-disclosure channel.
Auth declared & discoverablevia docs	13.8/25	No securitySchemes declared. Investigated: docs 55%, spec 36%, wellknown 0%.	Agents can only authenticate when auth is declared, scoped, and discoverable.
Example coveragevia spec	10/10	72% example coverage (target 80%+). Investigated: spec 100%, sdk 50%, docs 0%.	Examples carry shape semantics schemas under-specify — for humans and agents alike.

Developer ExperienceThe context both developers and agents need to integrate fast — onboarding, code samples, complete descriptions and worked examples2 pass0 warn3 fail58D

Signal	Points	Findings	Rationale
Self-service developer portalvia docs	29/29	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%.	Self-serve key/account creation is the fast first call for partners, with no sales gate.
Description completenessvia spec	15/15	35% description completeness. Investigated: spec 100%.	Complete descriptions are the context humans and agents need to use endpoints.
Quickstart presentvia docs	0/25	No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.	A quickstart is the fastest path from landing page to first successful call.
Code samples in docsvia docs	0/18	No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.	Multi-language samples shorten time-to-first-call.
Changelog publishedvia spec	0/13	No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%, sdk 0%.	A published changelog lets partners track changes without surprise.

Agent DiscoveryPartners and their agents can find your APIs — llms.txt, registries, crawlable and reachable docs1 pass2 warn1 fail65C

Signal	Points	Findings	Rationale
Registry & SDK presencevia docs	28/28	Indexed on Context7 (chemelli74/aiovodafone, 21 snippets). Investigated: docs 100%, cli 100%, sdk 17%.	Listing in MCP registries and publishing SDKs puts the API where agents and their tooling look.
Docs reachable, not hard auth-gatedvia docs	22.5/30	Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.	Agents can only index and fetch docs they can reach — past auth gates and over correct HTTP semantics.
Crawlable / AEOvia wellknown	6/12	No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.	Bots allowed plus a fresh sitemap make docs findable by agent crawlers.
llms.txt present, valid & comprehensivevia docs	0/30	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%.	A valid, comprehensive llms.txt is the machine-readable entry point for agents.

Agent UnderstandingAgents can correctly interpret your APIs — machine-readable errors, consistent descriptions, structured data, parseable docs2 pass2 warn2 fail76B

Signal	Points	Findings	Rationale
Machine-readable errors (RFC 9457)via docs	28/28	No 4xx/5xx response codes (or default error response) documented anywhere in the spec. Investigated: docs 100%, spec 50%.	RFC 9457 problem details and a documented error-code inventory let agents parse failures without burning tokens.
Operation purpose clarityvia spec	25/25	100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.	Agents select the right endpoint from its summary + operationId; clear, named operations make tool-selection reliable — the strongest driver of correct tool choice.
Agent-navigable, token-efficient docsvia docs	17.3/22	No pages support .md URLs (0/1 tested). Investigated: docs 79%.	Server-rendered, clean, small-footprint docs are what an agent can cheaply fetch and parse correctly.
Description consistency across surfaces	0.6/7	Mean pairwise description similarity across 3 surfaces (spec, docs, sdk) is 3% (threshold 35% for full credit).	Every surface tells the same story about what the product is.
Agent instructions file (AGENTS.md)via wellknown	0/10	No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.	An AGENTS.md gives coding agents explicit setup, auth, and usage instructions to interpret and operate the API — beyond llms.txt's link index.
Docs structured datavia docs	0/8	Neither JSON-LD nor OpenGraph/meta tags detected across 1 assessed pages (1 JS-rendered). Investigated: docs 0%.	Structured data (JSON-LD/schema.org) on docs pages gives agents an unambiguous parse target and is what answer engines cite. Detected on the JS-rendered head (Firecrawl) for a bounded page budget, so JS-injected JSON-LD is now caught; pages we can't render are excluded rather than failed.

Agent UsabilityAgents have the context to use your APIs reliably, not just find them2 pass2 warn1 fail65C

Signal	Points	Findings	Rationale
Pagination documented & consistentvia spec	22/22	Pagination params detected on 2 list endpoint(s). Investigated: spec 100%, docs 100%.	Consistent, documented pagination lets agents traverse collections.
Sandbox separationvia spec	20/20	Sandbox server declared but no distinguishable test credentials in scheme descriptions. Investigated: spec 100%, docs 100%, sdk 50%.	An isolated environment lets agents exercise destructive operations safely.
Rate-limit signalingvia spec	8.8/22	No rate-limit response headers documented. Investigated: spec 40%, docs 40%.	Machine-readable rate-limit headers let agents throttle adaptively.
Runnable collection with test scriptsvia platform	4.5/9	No test scripts found in the workspace's collections. Investigated: platform 50%.	A public, maintained collection with assertions is runnable truth agents validate against.
Idempotency documentedvia spec	0/27	0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 0%.	Documented idempotency lets agents retry safely.

Resources Discovered

The public resources we found for Vodafone — the evidence behind the score. All discovered from public sources; nothing here requires access to your systems.

Agent hints	Context7 (21)
APIs analyzed	10 — Operate (TMForum), Identity (CAMARA), Open Gateway Operate API - Product Catalog, Branded Calling, Mobile (OneAPI), Device Location (CAMARA), Quality-On-Demand, Quality-On-Demand (CAMARA), TMF936 Operate API - Product Catalog (TMForum), Call Notification AntiSpoofing (Vodafone)

Want to improve your results?