# Verizon — API Agent Score

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

Verizon scored 74/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 87/100 (A)
- Developer Experience: 75/100 (B)
- Agent Discovery: 69/100 (C)
- Agent Understanding: 57/100 (D)
- Agent Usability: 86/100 (A)

## Check Results

### API Design

- [warn] Schema coverage & depth — 530/532 (100%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 100%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, docs 0%.
- [warn] Security & governance hygiene — security.txt present but missing Contact; missing or expired Expires. Investigated: wellknown 50%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://www.verizon.com/content/wcms/404.html; free tier / sandbox documented. Investigated: docs 100%.
- [warn] Description completeness — 227/232 operations carry a description. Investigated: sdk 98%.
- [pass] Changelog published — Newest official SDK activity 77 day(s) ago. Investigated: sdk 100%.
- [warn] Quickstart present — Quickstart page reachable (12 variants scanned starting at https://developers.verizon.com/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/thingspace_verizon, 18 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — 1 of 1 pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developers.verizon.com/llms.txt, https://developers.verizon.com/docs/llms.txt). Investigated: docs 33%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap present (0 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 1 of 1 pages appear to be client-side rendered SPA shells (root detected); agents using HTTP fetches will see no content. Investigated: docs 64%.
- [warn] Docs structured data — OpenGraph/meta tags only across 1 assessed pages — no JSON-LD for answer engines to cite. Investigated: docs 50%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 10% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Verizon's API program shows strength in API design fundamentals and developer experience basics, but two areas are holding back partner and agent success: Agent Understanding is critically weak, meaning AI agents cannot reliably interpret or act on your API surface without guessing, and Agent Usability lacks the runnable, verified context agents need to integrate correctly. Closing these gaps — starting with machine-readable agent instructions and executable collections with test coverage — is the highest-leverage investment to make your partner program self-serve for both humans and AI agents.