~/CLIRank

Agent-Friendliness Report

Plivo API

SMS and voice APIs, often cheaper than Twilio.

60/100

Fair

CLI Readiness 8/10 · Quality 3/10

CLI Readiness

8/10
  • ✓Official SDK available+2
  • ✓Env var authentication+2
  • ✓Headless / CI compatible+2
  • ✗CLI tool available+1
  • ✓JSON responses+1
  • ✓curl / CLI doc examples+1
  • ✓Reasonable rate limits+1
  • ✗Machine-readable pricing+1

Quality Score

3/10
  • npm weekly downloads30K
  • GitHub stars1K
  • Days since last release72
  • Issue close ratio42%
  • TypeScript support✗
  • Docs qualityBasic
  • Breaking changesOccasional

Context7 Docs Benchmark

0.0

Trust Score

9.6/10

Snippets

19

Tokens

4K

Library ID

/plivo/plivo-node

Want to improve your score? Here's how

  • ->Make pricing machine-readable - Expose pricing as markdown, JSON, or a static table instead of JS widgets
View full API details →

How we calculate this score

The Agent-Friendliness Score measures how well an API works when used by AI coding agents (Claude Code, Cursor, Copilot) rather than humans in browsers.

CLI Readiness (60%) scores 8 signals that matter for headless, automated use: official SDK availability, env var auth (no browser OAuth), headless compatibility, CLI tooling, JSON responses, curl examples in docs, rate limits, and machine-readable pricing. Each signal is weighted by how much it blocks or enables agent workflows.

Quality (40%) covers SDK maturity and maintenance: npm download volume, GitHub stars, release freshness, issue close rate, TypeScript support, docs quality, and breaking change frequency.

Docs Benchmark (where available) is sourced from Context7, which tests how well an LLM can answer practical questions using the library's documentation.

Coming soon: live agent benchmarks that measure tokens burned, success rate, and time to first working API call using real integration tasks.

How agent-friendly is YOUR API?

Check your score at clirank.dev/score