rudderstack.com agentic web readiness
B Manifest validity: 100% (3/3 valid, 0 errors, 4 warnings) · Surface score 35 (coverage 20 + breadth 0 + conformance 15). 2 standards observed across 2 of 9 steps; 3 manifests present, 0 errors, 4 warnings. Checked 2026-10-23 15:54:55 UTC via www.rudderstack.com. This grades the agent-facing files published at rudderstack.com, not the organisation's products.
Coverage by step
Manifests
| Manifest | Result | Findings |
|---|---|---|
Agentic Resource Discovery/.well-known/ard.json | absent HTTP 404 | |
AI Catalog well-known file/.well-known/ai-catalog.json | valid | |
MCP Server Cards (SEP-2127)/mcp/server-card | absent HTTP 404 | |
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 | absent HTTP 404 | |
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs/.well-known/api-catalog | absent HTTP 404 | |
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 | absent HTTP 404 | |
Open Knowledge Format/okf/index.md | absent HTTP 404 |
What an agent can call
- MCP endpoint
https://mcp.rudderstack.com/mcp(streamable-http) — from/.well-known/ai-catalog.json - llms.txt: rudderstack.com, 36 links
- robots.txt AI policy: unlisted crawlers partial
Standards observed
- llms.txt https://rudderstack.com/llms.txt
- AI Catalog well-known file https://rudderstack.com/.well-known/ai-catalog.json
Cheapest next steps
- Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch
- AGENTS.md: instructions for coding agents working on or with the site
- api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs: an RFC 9727 linkset pointing at your OpenAPI description
Agent pre-flight & practical readiness
Preferred mode: mcp (fallback llms_txt). Call the MCP endpoint at https://mcp.rudderstack.com/mcp first. Do not scrape the HTML when a tool can answer.
Fetch: POST https://mcp.rudderstack.com/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 no, render ssr_rich, HTML quality high, first content at byte 218597, JSON-LD Organization, ImageObject, PostalAddress, ContactPoint, Person, QuantitativeValue, OfferCatalog, Offer, WebSite, BreadcrumbList, ListItem.
AI crawler posture: open_to_all · Assistant access: OpenAI partial, Anthropic partial, Google partial, Perplexity partial, Exa partial.
Readiness subscores: reach 19/20, readability 22/30, capabilities 19/35, conformance 15/15, total 75/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