Neon vs Turso for AI agents
As of 6 Oct 2026, Neon gets an AI agent further: L2 · Gets in against L1 · Needs a person.
- 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.
Gets furtherDriven 2 Oct 2026 · The drive and its evidence- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: needs a human. Next: let an agent sign up on its own
Needs a person: L1 · Needs a person. Our agent read Turso's docs on its own, headless, with llms.txt and Markdown pages, then hit a Clerk web form for sign-up. Submitting it showed a visible Cloudflare Turnstile check our agent could not pass, so no account, token or cloud database followed, and every API path answered that no token was present. Through the API it reached nothing live, but the embedded engine ran locally through the official SDK with no account at all: SQL, vectors, full-text search and CDC all worked there. Paying and leaving were never reached: no plan was started and no account existed to delete.
Driven 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.
NeonGot in; payment not reached
TursoStopped at sign up: needs a human
| Checkpoint | Neon | Turso |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Not needed | Needs a human |
| Verify | Not needed | Not reached |
| Key | Headless | Not reached |
| First call | Headless | Not reached |
| First action | Headless | Not reached |
| Pay | Not reached | Not reached |
| Cancel | Not needed | Not reached |
| Delete | Headless | Not reached |
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
| Neon | Turso | |
|---|---|---|
| Headless (checkpoints) | 5 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 0 | 1 |
| Blocked (checkpoints) | 0 | 0 |
| Not tested (checkpoints) | 1 | 7 |
| Work done | 45% of the core | Not measured |
| 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.
| Neon | Turso | |
|---|---|---|
| Bot check | Cloudflare interstitial on the console sign-up page; it got in another way | Cloudflare Turnstile (via Clerk bot protection) stopped it at sign up, with a visible challenge |
| Wall type | A check of our network and browser | A check of our network and browser |
| First wall | Got in; payment not reached | Cloudflare Turnstile on the sign-up form |
| 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.
| Neon | Turso | |
|---|---|---|
| Level | L2 · Gets in | L1 · Needs a person |
| Agent-ready setup | 100 of 100, good | 100 of 100, good |
| Standards | None recorded | MCP client registration (current) · OpenAPI 3.0.1 (2 versions behind) · A2A 0.3 (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.
| Neon | Turso | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not needed | Not reached |
| Delete the account | Headless | Not reached |
How each one takes payment
- Neon: Payment not reached.
- Turso: Payment not reached.
Neon vs Turso: the short answers.
Which can an AI agent use, Neon or Turso?
Neon gets an AI agent further: L2 · Gets in against L1 · Needs a person. With Neon our agent got in (payment not reached); with Turso it was stopped at sign up (needs a human). Driven 2 Oct 2026 (Neon) and 6 Oct 2026 (Turso).
Can an AI agent sign up for Neon and Turso on its own?
Neon: not needed. Turso: no, needs a human.
Do Neon and Turso have an MCP server?
Neon: yes (official). Turso: yes (official).
Can an AI agent delete its Neon or Turso account?
Neon: yes, headless. Turso: not reached.
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.