# Zendesk — API Agent Score

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

Zendesk scored 71/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 94/100 (A+)
- Developer Experience: 66/100 (C)
- Agent Discovery: 65/100 (C)
- Agent Understanding: 76/100 (B)
- Agent Usability: 56/100 (D)

## Check Results

### API Design

- [pass] Schema coverage & depth — 2/2 enums are named types (not bare strings). Investigated: sdk 100%, spec 67%.
- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [warn] Machine-readable, versioned contract — info.version="2.0.0" 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 100%.
- [pass] Example coverage — 79% example coverage (target 80%+). Investigated: spec 100%, sdk 50%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.zendesk.com/service/knowledge/?utm_source=portal-decom; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Description completeness — 87% description completeness (target 90%+). Investigated: spec 100%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [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 (zendesk/zcli, 29 snippets). Investigated: docs 100%, sdk 67%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/50 sampled pages return markdown). Investigated: docs 75%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.zendesk.com/documentation/llms.txt, https://developer.zendesk.com/llms.txt, https://developer.zendesk.com/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 9 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 99% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — No sampled pages support .md URLs (0/50 tested). Investigated: docs 57%.
- [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 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Pagination documented & consistent — Pagination params detected on 4 list endpoint(s). Investigated: spec 100%, docs 100%.
- [pass] Sandbox separation — sandbox documented in the docs site at https://www.zendesk.com/blog/customer-service/support/sandbox-environment-guide/. Investigated: spec 100%, docs 100%, sdk 50%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 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%.

## Executive Summary

Zendesk's API program has a strong machine-readable contract foundation, but partners and their AI agents face real friction at every step after discovery: there is no standard entry point for agents to find or parse the API surface, no runnable context for agents to build against, and onboarding requires too much manual effort before a partner can make a first call. Prioritize closing the agent discovery and usability gaps first — these block the self-serve partner motion entirely — then sharpen onboarding and operational reliability to reduce integration drop-off.