# Cloudinary — API Agent Score

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

Cloudinary scored 76/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 91/100 (A+)
- Developer Experience: 49/100 (F)
- Agent Discovery: 93/100 (A+)
- Agent Understanding: 76/100 (B)
- Agent Usability: 70/100 (B)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%, wellknown 0%.
- [warn] Schema coverage & depth — 91% of operations have documented schemas (target 95%+). Investigated: spec 81%, sdk 50%.
- [warn] Machine-readable, versioned contract — info.version="0.7.4" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 79%, docs 58%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, spec 8%, docs 0%.

### Developer Experience

- [pass] Description completeness — 56% description completeness. Investigated: spec 100%, sdk 42%.
- [pass] Changelog published — Newest official SDK activity 15 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Self-service developer portal — Signup page is sales-gated (contact-sales/request-access language detected). Investigated: 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 19 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 50 sampled pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/cloudinary, 31691 snippets). Investigated: docs 100%, cli 100%, mcp 100%, sdk 67%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — llms.txt covers 30/795 sitemap doc pages (4%); 765 missing. Investigated: docs 75%, sdk 0%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 5 distinct 4xx/5xx response codes documented. Investigated: docs 100%, sdk 100%, spec 50%.
- [warn] Operation purpose clarity — 89% of operations are agent-inferable (target 90%+). Investigated: spec 92%.
- [warn] Agent-navigable, token-efficient docs — 33 of 50 pages have substantive content differences between markdown and HTML (avg 25% missing). Investigated: docs 70%.
- [warn] Docs structured data — OpenGraph/meta tags only across 4 assessed pages — no JSON-LD for answer engines to cite. Investigated: docs 50%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 3% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Pagination documented & consistent — 1 list endpoint(s) exist but no pagination params found. Investigated: spec 75%, docs 75%.
- [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

Cloudinary's API program shows strong foundations in API design, agent discovery, and documentation quality — partners and agents can find and read the surface well. The critical gaps are in onboarding and agent operability: there is no self-service developer portal with quickstart content or multi-language code samples, and no runnable collection or agent instruction file for AI agents to act on. Closing the onboarding gap must come first, as it directly determines whether new partners reach a first successful integration — everything else builds on that foundation.