# Plivo — API Agent Score

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

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

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

## Summary

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

## Category Scores

- API Design: 66/100 (C)
- Developer Experience: 63/100 (C)
- Agent Discovery: 81/100 (A)
- Agent Understanding: 74/100 (B)
- Agent Usability: 86/100 (A)

## Check Results

### API Design

- [warn] Schema coverage & depth — 314 of 876 public signatures use loose types (anyTypeRatio=0.358). Investigated: sdk 75%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, docs 0%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [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 — Signup page at https://cx.plivo.com/signup (CSR-rendered — body classifier inconclusive); free tier / sandbox documented in pricing/docs. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 41 day(s) ago. Investigated: sdk 100%.
- [warn] Description completeness — 102/315 operations lack a description. Investigated: sdk 68%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [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/plivo, 7334 snippets). Investigated: docs 100%, sdk 100%, cli 100%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No /llms-full.txt found at the candidate origins. Investigated: docs 70%, sdk 0%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "PlivoRestError" with 8 subclasses. Investigated: sdk 100%.
- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 5% (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 1 sampled pages — likely a CSR-only docs site. Investigated: docs 0%.
- [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

Plivo's API program shows real strength in agent discoverability and docs reachability, but two areas demand immediate attention: API design security hygiene and agent understanding — both of which directly affect whether partners and their AI agents can safely integrate and self-serve without hand-holding. The top priority is closing the security governance gap and making your API surface fully machine-readable (with structured docs, agent instruction files, and runnable examples), so partners can move from evaluation to production confidently and autonomously.