# Vonage — API Agent Score

> Score: 76/100 (Grade: B) | Domain: vonage.com | Rubric: 1.0.0 | Checked: July 24, 2026

Vonage scored 76/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 88/100 (A)
- Developer Experience: 59/100 (D)
- Agent Discovery: 77/100 (B)
- Agent Understanding: 73/100 (B)
- Agent Usability: 80/100 (A)

## Check Results

### API Design

- [warn] Machine-readable, versioned contract — info.version="1.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 88%, docs 75%.
- [warn] Schema coverage & depth — 0/1 (0%) enum-like params are realized as constrained types (not bare strings). Investigated: sdk 86%, spec 65%.
- [warn] Auth declared & discoverable — No securitySchemes declared. Investigated: docs 81%, spec 41%.
- [warn] Security & governance hygiene — 10 credential-shaped strings detected in spec: bearer-jwt (×10). Investigated: spec 88%, wellknown 0%.
- [pass] Example coverage — 10% example coverage. Investigated: spec 100%, docs 100%, sdk 100%.

### Developer Experience

- [pass] Code samples in docs — Code samples in 10 language(s) across docs (top: curl, shell, javascript); 1/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%.
- [pass] Description completeness — 59% description completeness. Investigated: spec 100%, sdk 100%.
- [pass] Changelog published — changelog documented in the docs site at https://developer.vonage.com/en/changelogs. Investigated: spec 100%, docs 100%, sdk 100%.
- [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] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/developer_vonage_en_api, 2676 snippets). Investigated: docs 100%, sdk 100%, cli 100%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 1 pages. Investigated: docs 67%, sdk 0%.
- [warn] Docs reachable, not hard auth-gated — 1 of 1 pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] Crawlable / AEO — Sitemap present (2 entries) but carries no lastmod values. Investigated: wellknown 75%.

### 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%, sdk 100%, spec 63%.
- [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 — 1 of 1 pages appear to be client-side rendered SPA shells (__nuxt detected); agents using HTTP fetches will see no content. Investigated: docs 63%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 3 surfaces (spec, docs, 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%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 2 assessed pages (2 JS-rendered). Investigated: docs 0%.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Pagination documented & consistent — Pagination params detected on 5 list endpoint(s). Investigated: docs 100%, spec 75%, sdk 0%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 50%.
- [warn] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 13%, docs 13%.

## Executive Summary

Vonage's API program shows strong foundations in API design, operational reliability, and agent usability — partners building on this surface can trust the contract. The two areas that need urgent attention are agent understanding and developer experience: AI agents lack the structured context files and machine-readable signals needed to interpret and act on the APIs correctly, while partners face a self-service gap that slows their first successful call. Closing these two gaps will meaningfully shorten partner onboarding and make Vonage's APIs first-class citizens for the AI agent ecosystem.