Shutterstock is Poor to agents.

Item: Shutterstock API
Rating: 52
Author: Discry

Discry independently scored how well an AI agent can discover and understand the Shutterstock API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.

Discry your API — free View the docs ↗

SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.

Discovery

45% of score · 24/100

OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Pass

llms.txtAn llms.txt index that points agents to the docs that matter.Fail

llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Fail

llms-full.txtA full-text bundle agents can load in one request.Fail

AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Fail

.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail

MCP registryThe API is listed in a public MCP registry.Fail

robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Fail

SitemapA sitemap so agents can enumerate the docs surface.Fail

Comprehension

55% of score · 75/100

Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Pass

Realistic examplesRunnable, real-world request/response examples.Pass

Multi-step workflowsDocs that chain calls into complete jobs an agent can follow.Partial

Error-recovery guidanceDocumented failure modes and how to recover from them.Partial

Answer-first formatThe answer leads; preamble does not bury it.Pass

Capability boundariesClear limits — what the API can and cannot do.Partial

Naming consistencyConsistent, predictable naming across endpoints.Pass

Heading hierarchyClean heading structure agents can navigate.Pass

Markdown docsDocs available as clean markdown, not JS-rendered HTML only.Partial

Token efficiencyDocs are concise enough to fit an agent context window.Partial

What we found

Shutterstock has a publicly accessible OpenAPI spec at api-explorer.shutterstock.com/openapi.json — a strong foundation for agent integration
The developer site is behind Captcha/DataDome protection (403 responses), making automated agent discovery extremely difficult
No MCP servers found in any major registry for Shutterstock despite the media API being useful for content creation agents
The API Explorer at api-explorer.shutterstock.com provides interactive documentation built from Swagger specs
robots.txt is inaccessible due to the same Captcha protection that blocks the rest of the developer site

What to change

Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.

01Remove or whitelist Captcha/DataDome protection for robots.txt, llms.txt, and API documentation pages
02Add llms.txt covering image search, licensing, and media management API capabilities
03Fix the developer site to be accessible without JavaScript execution and Captcha solving
04Create a Shutterstock MCP server for AI-assisted media search and licensing
05Add sitemap.xml listing API documentation pages for crawler discovery

Execution coverage · INFORMATIONAL, UNSCORED

Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.

OAuth2API key✓ Error format documented✓ Rate limits documented✓ Pagination documented✕ Idempotency documented

Shutterstock uses OAuth2 and basic auth. JSON error responses. Rate limits documented. Offset-based pagination.

See your own Discry Score.

Drop your API docs URL. See what an agent sees — in 60 seconds, free.

Discry your API — free