docs.saleor.io agentic web readiness

A+ Manifest validity: 100% (6/6 valid, 0 errors, 8 warnings) · Surface score 60 (coverage 30 + breadth 15 + conformance 15). 8 standards observed across 3 of 9 steps; 6 manifests present (+ robots.txt), 0 errors, 8 warnings. Checked 2026-10-25 23:11:48 UTC. This grades the agent-facing files published at docs.saleor.io, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/docs.saleor.io.svg) · JSON · Markdown · Re-check now

Coverage by step

Manifests

What an agent can call

• MCP endpoint https://docs.saleor.io/mcp (streamable-http) — from /.well-known/mcp.json
• MCP endpoint https://docs.saleor.io/mcp (streamable-http), tools: search_docs, get_page, list_pages, get_navigation — from /.well-known/mcp/server-card.json
• API description https://docs.saleor.io/openapi.json (application/vnd.oai.openapi+json)
• API description https://docs.saleor.io/openapi.json (application/vnd.oai.openapi+json)
• API description https://docs.saleor.io/openapi.json (application/json)
• API description https://docs.saleor.io/ (text/html)
• API description https://docs.saleor.io/.well-known/mcp.json (application/json)
• API description https://docs.saleor.io/ (text/html)
• llms.txt: Saleor Commerce Documentation, 633 links, llms-full.txt present
• robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed
• ARD bridge (/.well-known/ard.json): 2/8 valid, 0 legacy, 0 dead/broken

Standards observed

• llms.txt https://docs.saleor.io/llms.txt
• Agentic Resource Discovery https://docs.saleor.io/.well-known/ard.json
• AI Catalog well-known file https://docs.saleor.io/.well-known/ai-catalog.json
• api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://docs.saleor.io/.well-known/api-catalog
• Agent Skills https://docs.saleor.io/.well-known/agent-skills/index.json
• Markdown for Agents https://docs.saleor.io/
• MCP Server Cards (SEP-2127)
• Model Context Protocol

Cheapest next steps

1. AGENTS.md: instructions for coding agents working on or with the site
   Generate starter /AGENTS.md for docs.saleor.io

   # Docs for agents
   
   Docs and what it offers to agents
   
   ## Read the data, not the HTML
   - Index: https://docs.saleor.io/llms.txt
   - API description: https://docs.saleor.io/openapi.json
   - Discovery catalog: https://docs.saleor.io/.well-known/ard.json
   
   ## Calling
   - MCP server (Streamable HTTP): https://docs.saleor.io/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@docs.saleor.io
   

2. security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people
   Generate starter /.well-known/security.txt for docs.saleor.io

   Contact: mailto:security@docs.saleor.io
   Expires: 2027-09-20T23:11:48Z
   Canonical: https://docs.saleor.io/.well-known/security.txt
   Preferred-Languages: en
   Policy: https://docs.saleor.io/security-policy
   

Agent pre-flight & practical readiness

Preferred mode: mcp (fallback openapi). Call the MCP endpoint at https://docs.saleor.io/mcp first. Do not scrape the HTML when a tool can answer.

Fetch: POST https://docs.saleor.io/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.

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 34/35, conformance 15/15, total 99/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