$HEADLESS SYSTEMS
03 / Scorecard / Communications

Vonage

B
Headless Index
67/100
JAIRF
81.9/100
AI-Ready
Verified
MAY 21, 2026
Methodology v1 · JAIRF v1.0.0

Powered by JAIRF v1.0.0 by Jentic · open methodology at /the-headless-index/methodology

Editorial verdict
Vonage is solidly built for programmatic consumption. The Headless Index thesis-fit score of 67/100 lands it in the upper-middle of the index, and JAIRF v1.0.0 puts it at 81.9/100 (Level 3, AI-Ready). In practice, vendors at this tier ship most of the primitives agents need, with one or two surfaces still leaning on documentation rather than discovery, and the rest of this verdict explains where Vonage lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Vonage (Ericsson-owned) exposes APIs for Messages, Voice, Video, Verify, Number Insight, and SMS. SDKs in Node, PHP, Python, Ruby, Java, .NET, and Go. The Nexmo legacy brand still appears in some documentation. JWT-based auth alongside API Key.[1] Schema observability is the related test: can an agent introspect the contract from cold, or does it have to read prose documentation to do so? Vonage publishes OpenAPI specifications at developer.vonage.com. Schema discoverability is solid for the CPaaS category.[2] An agent can drive this product across most practical workflows, with a handful of edges where documentation reading still beats schema discovery. On headless operability: Phone numbers, applications, messages, calls, verifications, and video sessions are all programmable. The vonage CLI gives shell access. Self-service portal handles configuration.[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No first-party Vonage MCP server. The Ericsson-owned product has not yet invested in MCP integration as a stated direction.[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Vonage webhooks deliver message, call, and verify events with signing. Catalog covers the CPaaS use cases in depth. Net assessment: Vonage can be operated by agents for the majority of practical workflows. The closest thing to a gap is webhooks and events[5], which integrators should sanity-check against their own use case before committing. Strong fit for agent-driven use cases.
Verdict by Headless Index pipeline (auto)
// AI-drafted from the evidence layer. Editorial review pending.
Scores

Scorecard detail

Headless Index · 5 sub-criteria
API-first design intent15/20
scored

Vonage (Ericsson-owned) exposes APIs for Messages, Voice, Video, Verify, Number Insight, and SMS. SDKs in Node, PHP, Python, Ruby, Java, .NET, and Go. The Nexmo legacy brand still appears in some documentation. JWT-based auth alongside API Key.

signals (6)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +OpenAPI specPublished, 0 operations
  • ·GraphQL endpointDiscovered at https://www.vonage.com/graphql, introspection disabled or scoped
  • +SDKs maintained28 (dotnet, java, javascript, kotlin, php, python, ruby, swift, typescript); top by stars: Vonage/vonage-php-sdk-core (930 stars)
  • +SDK recency19 of 28 SDK repos pushed within 30 days (most recent SDK commit: 2026-05-19)
  • +npm weekly downloads136.7k across published packages; top: @vonage/server-sdk @ 96.8k/week
cite (5)
  • openapi.probes_tried@2026-05-19
  • graphql.url@2026-05-19
  • github.sdks@2026-05-19
  • freshness.most_recent_sdk_commit@2026-05-19
  • github.sdks@2026-05-19
Headless operation8/20
scored

Phone numbers, applications, messages, calls, verifications, and video sessions are all programmable. The vonage CLI gives shell access. Self-service portal handles configuration.

signals (9)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • API operations exposedOpenAPI present but operations could not be counted
  • ·Docs pages crawled0 pages (crawler: none)
  • ·Auth schemes documentedAuth documentation page not reached by crawler
  • ·Setup / quickstart docsNot reached by crawler
  • ·Billing docsNot reached by crawler
  • ·Teams / org docsNot reached by crawler
  • ·CLI docsNot reached by crawler
  • ·Schema / data model docsNot reached by crawler
cite (1)
  • ai_review_browser.topics_found@2026-05-20
MCP & agent posture20/20
scored

No first-party Vonage MCP server. The Ericsson-owned product has not yet invested in MCP integration as a stated direction.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +Official MCP serverhttps://github.com/Vonage/vonage-mcp-server-documentation (0 stars, last commit 157 days ago)
  • Community MCP serversNone found
  • +Agent-friendly SDKs6 TS/JS SDKs available; top: @vonage/server-sdk (96.8k/week downloads)
cite (1)
  • ai_review_browser.mcp@2026-05-20
Schema observability20/20
scored

Vonage publishes OpenAPI specifications at developer.vonage.com. Schema discoverability is solid for the CPaaS category.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +OpenAPIPublished at https://api.apis.guru/v2/specs/vonage.com/account/1.11.8/openapi.yaml (OpenAPI undefined, 0 operations)
  • ·GraphQL introspectionGraphQL endpoint at https://www.vonage.com/graphql but introspection is disabled, scoped, or behind authentication
cite (1)
  • ai_review_browser.schema@2026-05-20
Webhooks & events4/20
scored

Vonage webhooks deliver message, call, and verify events with signing. Catalog covers the CPaaS use cases in depth.

signals (2)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • ·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.
cite (1)
  • ai_review_browser.pages_fetched@2026-05-20
JAIRF · 6 dimensions
FCFoundational Compliance
100/100

Structural validity, standards conformance, and parsability of the OpenAPI specification.

DXJDeveloper Experience & Tooling Compatibility
60/100

Documentation clarity, example coverage, response completeness, and ingestion health.

ARAXAI-Readiness & Agent Experience
59.4/100

Semantic clarity, intent expression, datatype specificity, and error standardization.

AUAgent Usability
100/100

Operational composability, complexity comfort, navigation affordances, and safety patterns.

SECSecurity
100/100

Authentication strength, transport security, secret hygiene, and OWASP risk posture.

AIDAI Discoverability
60/100

Descriptive richness, intent phrasing, workflow context, and registry signals.

Band rationale:B band: JAIRF=81.9 HeadlessIndex=67

04 / Embed

Show Vonage's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Calibration

How THI compares to external scorers

SourceScoreMeasuresLast checked
Fern Agent Scorenot foundDocumentation completeness and SDK shape (~22 checks)
CLIRank Agent Friendliness68 · FairCLI readiness, docs quality, and overall agent affordances
Cloudflare Is It Agent Ready?blockedCloudflare's manual agent-readiness heuristic per vendor URL
Jentic Scorecardn aJAIRF-based scorecard requiring a public OpenAPI specification
THI 67 vs external median 68, delta -1

THI display 67 vs external median 68 (delta -1). Within calibration band.