Netlify vs Railway for AI agents
As of 11 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: Can't sign up for one.
- Use: 10% of the work.
- Pay: Payment not reached.
- Leave: Leaves on its own: Nothing to cancel, what it made goes after 1 hour.
Got in; payment not reached. Next: let an agent sign up for an account on its own (without one it does 10% of the core work)
L2 · Gets in. Our agent got in on its own: `netlify deploy --allow-anonymous` pushed a static page live with no account, and the docs match the way an agent reads them: llms.txt, every page as Markdown, OpenAPI, and netlify.ai agent instructions. It stopped at sign-up: the email form reset after an invisible reCAPTCHA check, so no token, functions, edge functions or project management followed. Work done stayed at one deploy and one read-back through the CLI. Paying was never reached, and with no account created there was nothing to delete: our agent's own anonymous projects wouldn't delete either, each attempt returning an authentication error.
Driven 11 Oct 2026 · The drive and its evidence- 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 evidenceThe two summaries: written and checked by our agents from each product's drive. How we write.
Where each one stops.
NetlifyGot in; payment not reached
RailwayGot in; payment not reached
| Checkpoint | Netlify | Railway |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Not needed | Not needed |
| Verify | Not needed | Not needed |
| Key | Not needed | Headless |
| First call | Headless | Headless |
| First action | Headless | Headless |
| Pay | Not reached | Not reached |
| 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
| Netlify | Railway | |
|---|---|---|
| Headless (checkpoints) | 3 | 4 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 1 | 1 |
| Not tested (checkpoints) | 1 | 1 |
| Work done | 10% of the core | 60% of the core |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | Yes |
| SDK | Yes | No |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Netlify | Railway | |
|---|---|---|
| Bot check | Invisible reCAPTCHA silently drops email sign-up; it got in another way | Cloudflare Turnstile on the email sign-up; it got in another way |
| Wall type | A challenge on the form | A challenge on the form |
| First wall | Got in; payment not reached | Got in; payment not reached |
| 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.
| Netlify | Railway | |
|---|---|---|
| Level | L2 · Gets in | L3 · Does the work |
| Agent-ready setup | 100 of 100, good | 100 of 100, good |
| Standards | MCP client registration (behind) · OpenAPI 2.0 (3 versions behind) | MCP client registration (current) · OpenAPI 3.1.0 (1 version behind) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Netlify | Railway | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Free plan | Trial, no card |
| Cancel | Not needed | Not needed |
| Delete the account | Blocked | Blocked |
How each one takes payment
- Netlify: Payment not reached.
- Railway: Payment not reached.
Netlify vs Railway: the short answers.
Which can an AI agent use, Netlify or Railway?
Railway gets an AI agent further: L3 · Does the work against L2 · Gets in. With Netlify our agent got in (payment not reached); with Railway it got in (payment not reached). Driven 11 Oct 2026 (Netlify) and 6 Oct 2026 (Railway).
Can an AI agent sign up for Netlify and Railway on its own?
Netlify: not needed. Railway: not needed.
Do Netlify and Railway have an MCP server?
Netlify: yes (official). Railway: yes (official).
Can an AI agent delete its Netlify or Railway account?
Netlify: blocked. Railway: 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.