Railway vs Vercel for AI agents
As of 16 Oct 2026, Railway gets an AI agent further: L3 · Does the work against L2 · Gets in.
- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Try first, claim later.
- Use: 60% of the work.
- Pay: Payment not reached.
- Leave: Leaves on its own: Nothing to cancel, what it made goes after 24 hours.
Got in; payment not reached. Next: do 80% of the core work (now 60%)
L3 · Does the work: our agent gets in on its own, no account needed. `ssh railway.new` issued a project token headless, and the first API call with it succeeded. From there it ran `railway add -d postgres`, creating a Postgres service with a successful deployment, plus variables, logs and metrics on that same token. No 402 route existed anywhere, and checkout sits behind that same sign-in wall. No plan was started, so there was nothing to cancel, and the anonymous project could not be deleted: Railway's docs say unclaimed boxes expire after the claim window instead.
Gets furtherDriven 6 Oct 2026 · The drive and its evidence- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server; a docs page for each core task.
- Access: No key needed.
- Use: 0% of the work.
- Pay: Needs a person to buy: A phone number at checkout.
- Leave: Nothing to cancel: Can't delete what it made.
Got in; first wall at pay (blocked). Next: do half of the core work (now 0%)
Vercel is a cloud hosting platform with very agent-friendly documentation, but an agent could not actually use it on its own: creating an account by email was refused for no stated reason, and signing up with GitHub worked but then demanded a phone number for a text-message code on every login.
Driven 16 Oct 2026 · The drive and its evidenceThe two summaries: written by our agents from each product's drive. How we write.
Where each one stops.
RailwayGot in; payment not reached
VercelGot in; first wall at pay (blocked)
| Checkpoint | Railway | Vercel |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Not needed | Not needed |
| Verify | Not needed | Not needed |
| Key | Headless | Not needed |
| First call | Headless | Headless |
| First action | Headless | Not needed |
| Pay | Not reached | Blocked |
| Cancel | Not needed | Not needed |
| Delete | Blocked | Blocked |
Headless or in a browser.
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| Railway | Vercel | |
|---|---|---|
| Headless (checkpoints) | 4 | 2 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 1 | 2 |
| Not tested (checkpoints) | 1 | 0 |
| Work done | 60% of the core | 0% of the core |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | Yes |
| SDK | No | – |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Railway | Vercel | |
|---|---|---|
| Bot check | Cloudflare Turnstile on the email sign-up; it got in another way | None met |
| Wall type | A challenge on the form | No bot-check wall |
| First wall | Got in; payment not reached | Got in; first wall at pay (blocked) |
| A person helped | No | No |
A challenge on the form: It asks every visitor to prove they are human. It stops every agent on any network, and a signature doesn't help: a person does this step, or the owner opens it for agents. Where we drive from.
Level and part scores.
| Railway | Vercel | |
|---|---|---|
| Level | L3 · Does the work | L2 · Gets in |
| Agent-ready setup | 100 of 100, good | 100 of 100, good |
| Standards | MCP client registration (current) · OpenAPI 3.1.0 (1 version behind) | MCP client registration (behind) · OpenAPI 3.0.3 (2 versions behind) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Railway | Vercel | |
|---|---|---|
| Pay | Payment not reached | Needs a person to buy |
| Free plan or trial | Trial, no card | Free plan |
| Cancel | Not needed | Not needed |
| Delete the account | Blocked | Blocked |
How each one takes payment
- Railway: Payment not reached.
- Vercel: A person has to buy: a phone number at checkout.
Railway vs Vercel: the short answers.
Which can an AI agent use, Railway or Vercel?
Railway gets an AI agent further: L3 · Does the work against L2 · Gets in. With Railway our agent got in (payment not reached); with Vercel it got in and met its first wall at pay (blocked). Driven 6 Oct 2026 (Railway) and 16 Oct 2026 (Vercel).
Can an AI agent sign up for Railway and Vercel on its own?
Railway: not needed. Vercel: not needed.
Do Railway and Vercel have an MCP server?
Railway: yes (official). Vercel: yes (official).
Can an AI agent delete its Railway or Vercel account?
Railway: blocked. Vercel: blocked.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.