AgentsReady
Verified deep dive · Devtools

Railway

Run the agent liveReport a change
3 minTime to key
YesNo-human path
0Gates to a test key
9/10Onboarding score
Live keys only:Email verification

Fastest path to a key

  1. Card before first call
    zero-account compute: `ssh railway.new` gives a free VM + preview URL with no account or card, keyed by SSH key; claim within 24h
  2. `curl -fsSL agents.railway.com | sh` (CLI + agent config) then `railway login`: browser flow (device code over SSH) that signs in OR creates the account. `railway up -y` signs up and deploys in one step
  3. optional: connect GitHub at railway.com/verify for the Full Trial (unverified = Limited Trial with restricted outbound network)
  4. API token: railway.com/account/tokens (account / workspace) or project settings (project token)
  5. MCP: `claude mcp add railway --transport http https://mcp.railway.com` then OAuth (DCR)
  6. Working API key

Biggest gap

No anonymous or claimable project deploy (only a VM). Unverified trials get restricted networking. Tokens can only be minted in the dashboard

Worth copying

auth.md + RFC 9727 api-catalog + RFC 9728/8414 metadata: one 401 from the MCP teaches a client the whole auth chain, and the doc tells agents which credential type to use

Sources (10) · checked 2026-10-11
95Readiness score / 100
L4 Agent-nativeBeats 99% of 1,846 companies
Access20/20
Context17/20
Interfaces32/32
Onboarding19/19
Trust7/9
llms.txt · root
MCP · https://mcp.railway.app/mcp
OpenAPI · https://railway.com/openapi.json

Biggest gains

  1. +3 llms-full.txt exists. Publish /llms-full.txt with the whole docs corpus in one file.
  2. +2 security.txt. Publish /.well-known/security.txt with a contact.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • PASSllms.txt exists8
  • FAILllms-full.txt exists3
  • PASSDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • PASSMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • PASSSDKs and a CLI4
  • PASSOAuth discovery metadata5
  • PASSAgents can self-register OAuth clients6
  • PASSSelf-serve API keys5
  • PASSFree tier or test mode3
  • PASSAgent manifests4
  • FAILsecurity.txt2
  • PASSPublic status page3

Your fix pack: 3 changes, up to +5 points

Each change is ready to paste, filled in for railway.app, with a command to check it worked. Or hand the whole list to your coding agent.

One file with your whole docs lets an agent load everything in a single request instead of crawling.

Where: https://railway.app/llms-full.txt, regenerated on every docs deploy
# Mintlify, Fern, GitBook and ReadMe generate this automatically; turn it on in settings.
# Self-hosted docs: concatenate the markdown sources at build time
{ echo "# Railway documentation"; for f in $(find docs -name "*.md*" | sort); do echo; echo "---"; echo "source: $f"; echo; cat "$f"; done; } > public/llms-full.txt
Check it worked:curl -s https://railway.app/llms-full.txt | wc -c # expect well over 2000

Add the badge to your README

AgentsReady badge for railway.app
[![AgentsReady](https://agentsready.dev/badge/railway.app)](https://agentsready.dev/c/railway.app)