Agent readiness · SMS, voice and messaging
vonage.com
4 of 8 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 8 of them could not be measured from where we ask, and those are left out of the denominator rather than counted as failures.
A · Discovery
- UNMEASUREDAnswers an agent user-agentUnmeasurable: answered 403 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology) and 403 to a Chrome user-agent, so the refusal is about where we ask from, not about agentsNothing for you to do here. Whether agents are treated differently becomes measurable from a network your edge admits.
- PASSllms.txt publishedllms.txt present at https://developer.vonage.com/llms.txt, and the 12 links we sampled across the file all answer
- PASSDocs readable without JavaScript10,861 characters of text without JS
- UNMEASUREDOn-demand agents not blockedUnmeasurable: your edge answered our request for robots.txt with a refusal rather than the file, so what it permits is not something we measuredServe robots.txt to ordinary HTTP clients. Every crawler you want has to read it too.
- UNMEASUREDPaths robots.txt points at answerUnmeasurable: robots.txt was refused rather than absent, so nothing in it could be followedServe robots.txt to ordinary HTTP clients and this becomes measurable.
- UNMEASUREDNo punishing crawl delayUnmeasurable: robots.txt was refused rather than absent, so any Crawl-delay in it is unreadServe robots.txt to ordinary HTTP clients and this becomes measurable.
B · Agent entry
- UNMEASUREDAgent entry pointUnmeasurable: 9 of the 9 known agent entry paths answered with a refusal rather than a file or a 404, so what you publish there is not something we measuredLet ordinary HTTP reach these paths and this becomes measurable.
- FAILOAuth dynamic client registrationNo OAuth metadata on any of the 9 hosts probed, including the usual auth and api subdomains
- FAILMCP surfaceMCP mentioned 2x in your own files, but nothing answered at mcp.vonage.com, mcp.vonage.com/mcp, mcp.vonage.com/v1/mcp, api.vonage.com/mcp, /mcp or /api/mcp
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://vonage.com/signup is not in the server HTML, so its gates are not eitherServer-render the form, or tell us the endpoint it posts to, and the gates become visible to us and to an agent.
- UNMEASUREDSignup reachable without a browserUnmeasurable: https://vonage.com/signup answers 403 to an agent and 403 to a Chrome user-agent, so nothing gets in from here and the difference we test for cannot be seenNothing for you to do here. It becomes measurable from a network your edge admits.
D · Provisioning
- PARTProgrammatic key provisioning1 of 7 provisioning phrases across the 3 documents we read: "account api"
- UNMEASUREDFree tier or no-card trial stated in textUnmeasurable: no pricing page could be fetchedLink a pricing page from your home page, or list one in llms.txt.
E · Integration
- PASSTyped SDK on the registry@vonage/server-sdk@3.29.0 ships types, matched from the registry by who publishes it rather than by a link on your site
- FAILMachine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://developer.vonage.com/en/home, and no markdown negotiationPoint at your spec from your docs page with rel="service-desc" and an agent finds it without guessing.
Tell me when this changes
The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.
This page is the newest scan we hold for vonage.com and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.