Netlify vs Vercel for AI agents
As of 16 Oct 2026, both reach L2 · Gets in, and our agent got as far with each: with Netlify it got in (payment not reached), with Vercel it got in and met its first wall at pay (blocked).
- 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; 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.
NetlifyGot in; payment not reached
VercelGot in; first wall at pay (blocked)
| Checkpoint | Netlify | Vercel |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Not needed | Not needed |
| Verify | Not needed | Not needed |
| Key | Not needed | 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
| Netlify | Vercel | |
|---|---|---|
| Headless (checkpoints) | 3 | 2 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 1 | 2 |
| Not tested (checkpoints) | 1 | 0 |
| Work done | 10% of the core | 0% of the core |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | Yes |
| SDK | Yes | – |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Netlify | Vercel | |
|---|---|---|
| Bot check | Invisible reCAPTCHA silently drops 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.
| Netlify | Vercel | |
|---|---|---|
| Level | L2 · Gets in | L2 · Gets in |
| 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 (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.
| Netlify | Vercel | |
|---|---|---|
| Pay | Payment not reached | Needs a person to buy |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not needed | Not needed |
| Delete the account | Blocked | Blocked |
How each one takes payment
- Netlify: Payment not reached.
- Vercel: A person has to buy: a phone number at checkout.
Netlify vs Vercel: the short answers.
Which can an AI agent use, Netlify or Vercel?
Both reach L2 · Gets in, and our agent got as far with each: with Netlify it got in (payment not reached), with Vercel it got in and met its first wall at pay (blocked). Driven 11 Oct 2026 (Netlify) and 16 Oct 2026 (Vercel).
Can an AI agent sign up for Netlify and Vercel on its own?
Netlify: not needed. Vercel: not needed.
Do Netlify and Vercel have an MCP server?
Netlify: yes (official). Vercel: yes (official).
Can an AI agent delete its Netlify or Vercel account?
Netlify: 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.