# ZoomInfo — API Agent Score

> Score: 67/100 (Grade: C) | Domain: zoominfo.com | Rubric: 1.0.0 | Checked: August 20, 2026

ZoomInfo scored 67/100 (C), classified "partially-ready".

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

## Summary

- Overall: 67/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 88/100 (A)
- Developer Experience: 75/100 (B)
- Agent Discovery: 71/100 (B)
- Agent Understanding: 88/100 (A)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — The API declares version "1.0" and uses url-based versioning, so an agent can pin to a stable contract. Investigated: spec 100%, docs 100%.
- [pass] Auth declared & discoverable — Authentication is required across the API (declared globally or on every operation), so an agent knows credentials are needed. Investigated: spec 100%, docs 100%, wellknown 0%.
- [warn] Schema coverage & depth — Operations take 1.9 parameters each on average and some use nested-object or request-body schemas, which are harder for an agent to fill correctly. Investigated: spec 83%, sdk 0%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, sdk 100%, wellknown 0%.
- [fail] Example coverage — Only 12% of parameters and responses (15 of 126) include example values, so an agent has little grounding in real payload shapes. Investigated: spec 0%, sdk 0%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup available at https://www.zoominfo.com/free-trial, but no free tier or sandbox is documented, so an agent may hit a paywall before the first call. Investigated: docs 100%.
- [pass] Description completeness — 97% of operations and parameters carry substantive descriptions (17 of 18 ops, 34 of 34 params), the main semantic cue an agent relies on. Investigated: spec 100%.
- [pass] Changelog published — Newest official SDK activity 13 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Quickstart present — No quickstart or getting-started page found at the conventional docs paths, so new developers and agents have no obvious first step. Investigated: docs 0%.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/api-docs_zoominfo, 7 snippets). Investigated: docs 100%, sdk 75%, cli 0%, mcp 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — Could not test any pages; 1 failed to fetch. Investigated: docs 50%.
- [warn] Docs reachable, not hard auth-gated — 1 JavaScript redirect(s) detected across 1 pages. Investigated: docs 50%.
- [warn] Crawlable / AEO — No sitemap found via robots.txt or /sitemap.xml on the docs host, so AI search engines have no crawl map for your docs. Investigated: wellknown 50%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Documents 5 distinct 4xx/5xx error response codes, so an agent can branch on specific failures instead of guessing. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 100% of operations (18 of 18) have both a clear summary and a descriptive name, so an agent can pick the right endpoint. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 69%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [skip] Docs structured data — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [fail] Idempotency documented — Only 0% of mutating operations (0 of 14) document idempotency, so an agent's retries can create duplicate writes. Investigated: spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers are documented, so an agent can't tell when it is approaching a limit and will get throttled. Investigated: spec 0%, docs 0%.
- [fail] Sandbox separation — None of the 1 declared server(s) is a sandbox/test host, and no test-key prefixes are documented, so agents can only hit production. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No README found. Investigated: sdk 0%, platform 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Zoominfo's API program shows strength in agent understanding and schema design, but faces critical gaps that block partner and agent adoption at scale. The most urgent issues are in agent usability — no sandbox environment, no idempotency or rate-limit documentation across 14 mutating operations, and no runnable collection — meaning partners and their AI agents can only hit production, have no safe way to experiment, and have no grounded starting point for integration. Alongside these, sparse example coverage (only 12% of parameters and responses) and the absence of a quickstart leave both human developers and AI agents without the concrete payload shapes and first-step guidance needed to build confidently. Prioritize making the API safe and executable to run first, then layer in richer examples and onboarding.