netlify.com agentic web readiness
A+ Manifest validity: 100% (8/8 valid, 0 errors, 4 warnings) · Surface score 70 (coverage 40 + breadth 15 + conformance 15). 11 standards observed across 4 of 9 steps; 8 manifests present, 0 errors, 4 warnings. Checked 2026-10-25 08:53:10 UTC via www.netlify.com. This grades the agent-facing files published at netlify.com, not the organisation's products.
Coverage by step
Manifests
| Manifest | Result | Findings |
|---|---|---|
Agentic Resource Discovery/.well-known/ard.json | valid | |
AI Catalog well-known file/.well-known/ai-catalog.json | valid | |
MCP Server Cards (SEP-2127)/.well-known/mcp/server-card.json | valid |
|
Agent2Agent Protocol/.well-known/agent-card.json | absent HTTP 404 | |
llms.txt/llms.txt | valid | |
AGENTS.md/AGENTS.md | absent HTTP 404 | |
Agent Skills/.well-known/agent-skills/index.json | valid | |
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs/.well-known/api-catalog | valid | |
AI Crawler User-Agent Tokens in robots.txt/robots.txt | valid |
|
security.txt (RFC 9116)/.well-known/security.txt | absent HTTP 404 | |
auth.md/auth.md | valid | |
Open Knowledge Format/okf/index.md | absent HTTP 404 |
What an agent can call
- MCP endpoint
https://netlify-mcp.netlify.app/mcp(streamable-http) — from/.well-known/ard.json - MCP endpoint
https://netlify-mcp.netlify.app/mcp(streamable-http) — from/.well-known/ai-catalog.json - MCP endpoint
https://netlify-mcp.netlify.app/mcp(streamable-http) — from/.well-known/mcp/server-card.json - API description
https://open-api.netlify.com/swagger.json(application/vnd.oai.openapi+json) - API description
https://www.netlify.com/.well-known/api-catalog(application/linkset+json) - API description
https://open-api.netlify.com/swagger.json(application/vnd.oai.openapi+json) - API description
https://www.netlify.com/.well-known/api-catalog(application/linkset+json) - API description
https://open-api.netlify.com/swagger.json(application/json) - API description
https://docs.netlify.com/api/get-started/(text/html) - API description
https://netlify-mcp.netlify.app/mcp/server-card(application/mcp-server-card+json) - API description
https://docs.netlify.com/build/build-with-ai/netlify-mcp-server/(text/html) - llms.txt: Netlify, 28 links
- robots.txt AI policy: allows GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-Web, Google-Extended, PerplexityBot; unlisted crawlers allowed
- ARD bridge (
/.well-known/ard.json): 2/4 valid, 0 legacy, 0 dead/broken
Standards observed
- llms.txt https://netlify.com/llms.txt
- Content Signals Policy https://netlify.com/robots.txt
- Agentic Resource Discovery https://netlify.com/.well-known/ard.json
- AI Catalog well-known file https://netlify.com/.well-known/ai-catalog.json
- api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://netlify.com/.well-known/api-catalog
- auth.md https://netlify.com/auth.md
- AI Crawler User-Agent Tokens in robots.txt https://netlify.com/robots.txt
- Agent Skills https://netlify.com/.well-known/agent-skills/index.json
- Markdown for Agents https://netlify.com/
- MCP Server Cards (SEP-2127)
- Model Context Protocol
Cheapest next steps
- AGENTS.md: instructions for coding agents working on or with the site
Generate starter
/AGENTS.mdfor netlify.com# Netlify for agents Netlify and what it offers to agents ## Read the data, not the HTML - Index: https://netlify.com/llms.txt - API description: https://netlify.com/openapi.json - Discovery catalog: https://netlify.com/.well-known/ard.json ## Calling - MCP server (Streamable HTTP): https://netlify.com/mcp - Rate limits and authentication: describe them here ## Conventions - How to cite or attribute content - What not to do (no scraping of /account/, no automated sign-ups, etc.) Contact: security@netlify.com
- security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people
Generate starter
/.well-known/security.txtfor netlify.comContact: mailto:security@netlify.com Expires: 2027-09-20T23:42:18Z Canonical: https://netlify.com/.well-known/security.txt Preferred-Languages: en Policy: https://netlify.com/security-policy
Agent pre-flight & practical readiness
Preferred mode: mcp (fallback openapi). Call the MCP endpoint at https://netlify-mcp.netlify.app/mcp first. Do not scrape the HTML when a tool can answer.
Fetch: POST https://netlify-mcp.netlify.app/mcp POST a JSON-RPC tools/list, or server/discover on the 2026-07-28 revision, before reading HTML.
Practical readability: exa_parsable yes, markdown negotiation yes, render markdown_native, HTML quality high, first content at byte 0, HTML-to-llms.txt token ratio 3.121×.
AI crawler posture: open_to_all · Assistant access: OpenAI allowed, Anthropic allowed, Google allowed, Perplexity allowed, Exa allowed.
Readiness subscores: reach 20/20, readability 30/30, capabilities 35/35, conformance 15/15, total 100/100, grade A+.
How the grade is made
+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). Lifecycle grade: A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Strict 100-point composite (subscores.total_100 / subscores.grade_100): reach_and_policy (20) + readability (30) + capabilities (35) + conformance (15), where A+ >= 80, A >= 65, B >= 45, C >= 28, D >= 15. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.
JSON · Markdown · probe rules