# Zocdoc — API Agent Score

> Score: 70/100 (Grade: B) | Domain: zocdoc.com | Rubric: 1.0.0 | Checked: July 29, 2026

Zocdoc scored 70/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 91/100 (A+)
- Developer Experience: 59/100 (D)
- Agent Discovery: 81/100 (A)
- Agent Understanding: 82/100 (A)
- Agent Usability: 48/100 (F)

## Check Results

### API Design

- [pass] Auth declared & discoverable — authentication documented in the docs site at https://api-docs.zocdoc.com/guides/authentication. Investigated: spec 100%, docs 100%, wellknown 0%.
- [warn] Schema coverage & depth — Medium parameter complexity (avg 2.5 params/op; nested/body schemas present). Investigated: spec 83%.
- [warn] Machine-readable, versioned contract — info.version="1.177" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — Code samples present on 4/16 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%, spec 0%.

### Developer Experience

- [pass] Code samples in docs — Code samples present on 4/16 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [pass] Description completeness — 90% of operations + parameters have substantive descriptions. Investigated: spec 100%.
- [pass] Changelog published — changelog documented in the docs site at https://api-docs.zocdoc.com/changelog. Investigated: spec 100%, docs 100%.
- [fail] Self-service developer portal — No self-service signup detected: no signup link found on the homepage or docs, and no conventional signup path (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free, /join, /create-account, /account/signup, /auth/signup, /users/sign_up) resolved. Investigated: docs 0%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Discovered SDKs in 4 distinct languages. Investigated: sdk 100%, docs 0%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/14 pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 14 pages. Investigated: docs 71%.
- [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) — 6 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 9 of 14 pages have substantive content differences between markdown and HTML (avg 28% missing). Investigated: docs 90%.
- [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 assessed pages (1 JS-rendered). Investigated: docs 0%.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Sandbox separation — Sandbox server declared but no distinguishable test credentials in scheme descriptions. Investigated: spec 100%, docs 100%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Zocdoc's API program has a strong foundation in machine-readable contract design and documentation reachability, but partners and their agents face two critical blockers: the absence of runnable, self-serve onboarding materials means partners cannot get hands-on without a sales conversation, and missing reliability signals (idempotency guidance, rate-limit feedback) make it unsafe for agents to run real workflows autonomously. Closing the agent-context gaps (an AGENTS.md file and structured docs metadata) will also ensure AI coding tools can accurately discover and act on Zocdoc's API surface without guessing. Prioritize making the API executable and reliable first, then layer in the agent-readability signals.