Convex vs Neon for AI agents
As of 2 Oct 2026, Convex 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: Runs locally: Can't sign up for one.
- Use: 70% of the work.
- Pay: Payment not reached.
- Leave: Leaves on its own: Nothing to cancel, made nothing to delete.
Got in; payment not reached. Next: let an agent sign up for an account on its own (without one it does 70% of the core work)
Gets in on its own, L3 · Does the work: a documented no-account route provisions a local deployment, where our agent pushed schema and functions, inserted and patched documents, ran an HTTP action, a cron and a scheduler, and set env vars, each checked back. The cloud side stopped at sign-up: a visible Cloudflare "Verify you are human" challenge blocked account creation, so no cloud project, deploy key or MCP session followed. Core backend work, plus file storage, text and vector search, custom-JWT auth and live subscriptions, ran on the local deployment; cloud paying and account deletion stayed out of reach, since both sit behind that same human checkpoint and the dashboard.
Gets furtherDriven 2 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: 45% of the work.
- Pay: Payment not reached.
- Leave: Leaves on its own: Nothing to cancel, what it made goes after 3 days.
Got in; payment not reached. Next: do half of the core work (now 45%)
Gets in on its own, L3 · Does the work is out of reach: this stays L2 · Gets in. A documented no-account route hands over a working database. Our agent called the claimable identity endpoint from auth.md, got a token, and ran SQL, extensions, autoscaling, scale-to-zero, auth sign-ups and RLS-protected REST CRUD through the Data API without signing up. It stopped at pay: reaching the console for a full account and billing needs a human past a Cloudflare interstitial, and no account-based routes beyond the claimable set were reached. One claimable project's delete call returned success, though its database connection kept working briefly after; the other stayed stuck on a claim lock pending expiry. No account existed, so there was none to delete.
Driven 2 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.
ConvexGot in; payment not reached
NeonGot in; payment not reached
| Checkpoint | Convex | Neon |
|---|---|---|
| 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 | Headless |
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
| Convex | Neon | |
|---|---|---|
| Headless (checkpoints) | 3 | 5 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 1 | 0 |
| Not tested (checkpoints) | 1 | 1 |
| Work done | 70% of the core | 45% of the core |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | Yes |
| SDK | Yes | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Convex | Neon | |
|---|---|---|
| Bot check | Cloudflare human check on the sign-up page; it got in another way | Cloudflare interstitial on the console sign-up page; it got in another way |
| Wall type | A check of our network and browser | A check of our network and browser |
| First wall | Got in; payment not reached | Got in; payment not reached |
| A person helped | No | No |
A check of our network and browser: It judged where our agent connects from and its browser, not a person. An agent that works on its own from a data center doesn't get through unless the owner lets signed agents in. How agents in a person's own browser fare isn't measured yet. Where we drive from.
Level and part scores.
| Convex | Neon | |
|---|---|---|
| Level | L3 · Does the work | L2 · Gets in |
| Agent-ready setup | 100 of 100, good | 100 of 100, good |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Convex | Neon | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not needed | Not needed |
| Delete the account | Blocked | Headless |
How each one takes payment
- Convex: Payment not reached.
- Neon: Payment not reached.
Convex vs Neon: the short answers.
Which can an AI agent use, Convex or Neon?
Convex gets an AI agent further: L3 · Does the work against L2 · Gets in. With Convex our agent got in (payment not reached); with Neon it got in (payment not reached). Both driven 2 Oct 2026.
Can an AI agent sign up for Convex and Neon on its own?
Convex: not needed. Neon: not needed.
Do Convex and Neon have an MCP server?
Convex: yes (official). Neon: yes (official).
Can an AI agent delete its Convex or Neon account?
Convex: blocked. Neon: yes, headless.
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.