railway.com agentic web readiness

A+ Manifest validity: 88% (7/8 valid, 1 error, 10 warnings) · Surface score 65 (coverage 40 + breadth 15 + conformance 10). 10 standards observed across 4 of 9 steps; 8 manifests present, 1 error, 10 warnings. Checked 2026-10-23 14:56:42 UTC. This grades the agent-facing files published at railway.com, not the organisation's products.

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

Coverage by step

01 DiscoverARD, AI Catalog well-known file, RFC 9727 02 Identifynothing observed 03 PermitContent Signals Policy 04 Readllms.txt, AGENTS.md, Markdown for Agents 05 Act 06 Coordinatenothing observed 07 Paynothing observed 08 Presentnothing observed 09 Accountnothing observed

Manifests

Manifest	Result	Findings
Agentic Resource Discovery `/.well-known/ard.json`	valid	specVersion is "0.91"; the published schema accepts "1.0" host block missing (displayName, identifier, documentationUrl help clients name the publisher)
AI Catalog well-known file `/.well-known/ai-catalog.json`	valid	specVersion is "0.91"; the published schema accepts "1.0" host block missing (displayName, identifier, documentationUrl help clients name the publisher)
MCP Server Cards (SEP-2127) `/.well-known/mcp/server-card.json`	valid	Content-Type is application/json; SEP-2127 says serve application/mcp-server-card+json $schema is not https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json remotes[0].supportedProtocolVersions missing; clients use it to pick a version before connecting no Access-Control-Allow-Origin: * (required for browser clients) no Cache-Control max-age; clients should be able to cache the card
Agent2Agent Protocol `/.well-known/agent-card.json`	absent HTTP 404
llms.txt `/llms.txt`	valid
AGENTS.md `/AGENTS.md`	valid
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`	valid
AI Crawler User-Agent Tokens in robots.txt `/robots.txt`	valid	no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
security.txt (RFC 9116) `/.well-known/security.txt`	absent HTTP 404
auth.md `/auth.md`	errors	none of the auth.md mechanism names found (identity_assertion, service_auth, anonymous)
Open Knowledge Format `/okf/index.md`	absent HTTP 404

What an agent can call

MCP endpoint https://mcp.railway.com (streamable-http) — from /.well-known/mcp/server-card.json
API description https://backboard.railway.com/graphql/v2 (application/graphql-response+json)
API description https://railway.com/openapi.json (application/openapi+json)
API description https://railway.com/.well-known/api-catalog (application/linkset+json)
API description https://backboard.railway.com/graphql/v2 (application/graphql-response+json)
API description https://railway.com/openapi.json (application/openapi+json)
API description https://railway.com/.well-known/api-catalog (application/linkset+json)
API description https://backboard.railway.com/graphql/v2 (application/graphql-response+json)
API description https://railway.com/openapi.json (application/openapi+json)
API description https://docs.railway.com/integrations/api (text/html)
API description https://docs.railway.com/integrations/api.md (text/markdown)
API description https://railway.com/api-reliability.md (text/markdown)
API description https://railway.com/auth.md (text/markdown)
API description https://backboard.railway.com/oauth/.well-known/openid-configuration (application/json)
API description https://docs.railway.com/ai/remote-mcp-server (text/html)
API description https://railway.com/mcp.md (text/markdown)
API description https://railway.com/.well-known/mcp/server-card.json (application/json)
API description https://mcp.railway.com/.well-known/oauth-protected-resource (application/json)
llms.txt: Railway, 40 links
robots.txt AI policy: unlisted crawlers partial

Standards observed

llms.txt https://railway.com/llms.txt
AGENTS.md https://railway.com/AGENTS.md
Content Signals Policy https://railway.com/robots.txt
Agentic Resource Discovery https://railway.com/.well-known/ard.json
AI Catalog well-known file https://railway.com/.well-known/ai-catalog.json
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://railway.com/.well-known/api-catalog
Markdown for Agents https://railway.com/
MCP Server Cards (SEP-2127)
Model Context Protocol
AI Crawler User-Agent Tokens in robots.txt

Cheapest next steps

security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people

Agent pre-flight & practical readiness

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

Fetch: POST https://mcp.railway.com 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 partial, Anthropic partial, Google partial, Perplexity partial, Exa partial.

Readiness subscores: reach 20/20, readability 30/30, capabilities 29/35, conformance 10/15, total 89/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