◎ Discry Score
monday.com.com
productivity · API
B
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 92 (A)
Discry your API →
PRODUCTIVITY · RANK #7 OF 24

Monday.com is Good to agents.

Discry independently scored how well an AI agent can discover and understand the Monday.com 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 · 52/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Fail
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.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.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 · 100/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.Pass
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

  • Monday.com achieves a perfect comprehension score (100/100) — every documentation check passes with task-oriented descriptions, realistic GraphQL examples, dedicated workflow guides, error recovery tables with Resolution columns, and comprehensive rate limit documentation
  • The error handling documentation is agent-optimized: a structured table maps error codes to HTTP statuses, descriptions, AND explicit resolution steps — exactly what an autonomous agent needs to self-correct
  • Rate limit documentation is exceptionally detailed with multiple limit types (complexity, daily, minute, concurrency, IP), calculation guidance, and reduction strategies — an agent can proactively plan request budgets
  • Discovery signals lag significantly behind content quality: no OpenAPI spec (GraphQL schema available instead), no llms-full.txt, no .well-known/mcp.json, no AGENTS.md despite having an official MCP server
  • The llms.txt is well-sized at 48KB with clear API-focused sections covering guides, reference objects, app development, and MCP security — one of the better implementations in this cohort

What to change

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

  1. 01Add llms-full.txt with complete API documentation in markdown — the current path returns a landing page instead of content
  2. 02Add .well-known/mcp.json pointing to the official monday.com MCP server (github.com/mondaycom/mcp) with tool declarations
  3. 03Publish the GraphQL schema in a discoverable location as a downloadable file (already available at api.monday.com/v2/get_schema but not discoverable)
  4. 04Add AGENTS.md to the mondaycom/mcp repository with guidance on how coding agents should authenticate and interact with the GraphQL API

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.

api_keyoauth2✓ Error format documented✓ Rate limits documented✓ Pagination documented✕ Idempotency documented

Personal API tokens and OAuth2 for apps. GraphQL API at single endpoint (api.monday.com/v2). JSON error responses with typed error codes, extensions object with request_id, and Retry-After header. Comprehensive rate limiting: complexity points (5M/10M per minute), daily calls (200K-2M depending on plan), 5K/min, 80 concurrent, IP limits. Cursor-based pagination for list queries.

See your own Discry Score.

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

Discry your API — free