monday.com

no link to documentation found in the homepage HTML

Fix: Link your docs from the homepage with visible anchor text ("Docs", "Documentation", "Developers"). An agent that cannot find your docs from your homepage will guess your API.

no link to an API reference in the homepage HTML

Fix: If you have an API, link its reference from the homepage. If you don't, this check is safe to ignore.

https://monday.com

163 characters

'The AI Work Platform for People & Agents | monday.com' (53 chars)

og:title and og:description present

all 6 agent crawlers may fetch /

HTTP 200, 2701 bytes

robots.txt has a Sitemap: line

616 URL(s) listed

search-based checks are deferred — excluded from the score

registry lookup not implemented in v1 — excluded from the score rather than guessed

3 of 5 sampled links broken: https://api.monday.com/v2/get_schema?format=sdl → 404, https://api.monday.com/v2/get_schema → 404, https://api.monday.com/v2/get_schema?version=2026-04 → 404

Fix: Fix the dead links in /llms.txt. Pointing an agent at a 404 is worse than not pointing it anywhere.

/llms-full.txt not served

Fix: Optional but cheap: publish /llms-full.txt with your docs inlined as one markdown file, so an agent can read everything in a single fetch.

Accept: text/markdown → text/html; charset=utf-8

Fix: Optional but increasingly expected: honour `Accept: text/markdown` by serving a markdown rendering of the page, so agents skip HTML parsing entirely.

ratio 0.0261 — 15508 readable chars in 593500 bytes of HTML

Fix: Most of what you serve is markup and inline script rather than content. Reduce inline payloads or server-render more text so the signal-to-noise ratio favours readers.

HTTP 200 for / (agent UA)

https://monday.com/

1 valid block(s)

HTTP 200, 9901 bytes

has headings and markdown links

both User-Agents got HTTP 200

15508 characters of text in the served HTML

0 redirect(s)

/docs not served (HTTP 404) — docs may live on another path or host

HTTP 403 — the endpoint requires credentials to initialize

Fix: Let unauthenticated clients complete `initialize` and `tools/list`, and require auth only on `tools/call`. An agent that cannot see your tools cannot decide to use them.

/agents.md not served (HTTP 404)

Fix: Publish /agents.md: what an agent may do here, which endpoints matter, auth requirements, and rate limits. It is the agent-facing counterpart to a README.

/docs → HTTP 404

Fix: Serve docs at the conventional /docs path, or redirect it to wherever they live. Agents try conventional paths first.

404 returns HTML, not a machine-readable body

Fix: Content-negotiate your errors: return a JSON body with a stable `code` (and a `next_action` where recovery exists) to clients that ask for JSON.

3 error response(s) documented, none with a schema

Fix: Give your 4xx/5xx responses a response body schema with a stable machine-readable error code. An agent needs to branch on the code, not parse your prose.

1 scheme(s): bearerAuth

2/2 operations described (100%)

HTTP 200, 8857 bytes of JSON

OpenAPI 3.1.0, 2 path(s)

HTTP 200, valid JSON

/api → HTTP 404 (no API at the conventional root)

no listed MCP tools to inspect

no listed MCP tools to inspect

handshake did not complete, so tools/list was not reached

no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.

no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.

no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.