◎ Discry Score
webflow.com
cms · API
A
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 96 (A)
Discry your API →
CMS · RANK #1 OF 13

Webflow is Agent-Ready to agents.

Discry independently scored how well an AI agent can discover and understand the Webflow 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 — freeView 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 · 95/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.Pass
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Pass
llms-full.txtA full-text bundle agents can load in one request.Pass
AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Pass
.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail
MCP registryThe API is listed in a public MCP registry.Pass
robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Pass
SitemapA sitemap so agents can enumerate the docs surface.Pass

Comprehension

55% of score · 96/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.Pass
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.Pass
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.Pass
Token efficiencyDocs are concise enough to fit an agent context window.Pass

What we found

  • An agent discovering this API would find it immediately via llms.txt, llms-full.txt, OpenAPI spec, MCP registries, and AGENTS.md — Webflow has invested heavily in every major discovery channel.
  • The llms.txt architecture is exceptionally well-designed: a root index links to per-product llms.txt files, and any documentation URL can be converted to markdown by appending .md — purpose-built for LLM consumption.
  • Multi-step workflow documentation is strong: dedicated guides walk through create-collection → add-fields → create-items → publish with realistic examples at each step.
  • The only meaningful discovery gap is the absence of .well-known/mcp.json despite having an official MCP server — agents cannot auto-discover tool declarations via the standard well-known path.
  • Error recovery guidance is the weakest comprehension area: rate limit recovery is well-documented (Retry-After header, SDK backoff), but other error scenarios (400, 401, 404) lack actionable fix steps.

What to change

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

  1. 01Add .well-known/mcp.json to developers.webflow.com with tool declarations and auth information, enabling agents to auto-discover the MCP server without searching registries.
  2. 02Create a dedicated error handling reference page (the current /data/reference/error-handling URL redirects to webhooks) with actionable recovery steps for each error code — especially 400 validation errors explaining which fields failed and why.
  3. 03Add idempotency key documentation for write operations (POST/PATCH) to help agents safely retry failed requests without creating duplicates.
  4. 04Consider adding the official webflow/mcp-server to Smithery.ai for broader MCP registry coverage.
  5. 05Add per-endpoint error examples showing the exact JSON error response shape for common failure modes (invalid field data, scope mismatch, rate limit exceeded).

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.

Bearer token (Site Token)Bearer token (Workspace Token)OAuth 2.0✓ Error format documented✓ Rate limits documented✓ Pagination documented✕ Idempotency documented

Webflow documents three auth methods (Site Token, Workspace Token, OAuth 2.0), machine-parseable JSON error responses with codes, specific rate limits per plan (60-120 RPM) with Retry-After headers, and offset-based pagination (limit/offset up to 100 items). Idempotency keys are not documented.

See your own Discry Score.

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

Discry your API — free