PlanetScale vs Turso for AI agents
As of 6 Oct 2026, PlanetScale 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: Sign-up by email.
- Use: Work not reached.
- Pay: Card checkout.
- Leave: Leaves on its own: Nothing to cancel, deletes its account.
Got in; first wall at first action (blocked). Next: let a trial or free plan reach the core features
Gets in on its own: L2 · Gets in. Our agent signed up headless, no CAPTCHA, confirmed by email, logged in through the CLI's device flow, and pulled a service token for both the API and a hosted MCP server. It stopped trying to create a database: the API answered that it could not verify a card, and there is no free plan to work around that. Paying needs a card through Stripe Checkout; our agent never attached one, so it never reached core database work. Deleting the account needs the web UI: no API route exists for it.
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.
PlanetScaleGot in; first wall at first action (blocked)
TursoStopped at sign up: needs a human
| Checkpoint | PlanetScale | Turso |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Headless | Needs a human |
| Verify | Headless | Not reached |
| Key | Headless | Not reached |
| First call | Headless | Not reached |
| First action | Blocked | Not reached |
| Pay | Not tried | Not reached |
| Cancel | Not needed | Not reached |
| Delete | In a browser | 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
| PlanetScale | Turso | |
|---|---|---|
| Headless (checkpoints) | 5 | 1 |
| In a browser (checkpoints) | 1 | 0 |
| Needs a human (checkpoints) | 0 | 1 |
| Blocked (checkpoints) | 1 | 0 |
| Not tested (checkpoints) | 1 | 7 |
| Work done | Paid plans only | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | Yes |
| SDK | No | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| PlanetScale | Turso | |
|---|---|---|
| Bot check | hidden honeypot field (telephone) let it through at sign up | Cloudflare Turnstile (via Clerk bot protection) stopped it at sign up, with a visible challenge |
| Wall type | No bot-check wall | A check of our network and browser |
| First wall | Got in; first wall at first action (blocked) | 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.
| PlanetScale | 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.
| PlanetScale | Turso | |
|---|---|---|
| Pay | Card checkout | Payment not reached |
| Free plan or trial | None | Free plan |
| Cancel | Not needed | Not reached |
| Delete the account | In a browser | Not reached |
How each one takes payment
- PlanetScale: Card checkout.
- Turso: Payment not reached.
PlanetScale vs Turso: the short answers.
Which can an AI agent use, PlanetScale or Turso?
PlanetScale gets an AI agent further: L2 · Gets in against L1 · Needs a person. With PlanetScale our agent got in and met its first wall at first action (blocked); with Turso it was stopped at sign up (needs a human). Driven 2 Oct 2026 (PlanetScale) and 6 Oct 2026 (Turso).
Can an AI agent sign up for PlanetScale and Turso on its own?
PlanetScale: yes, headless. Turso: no, needs a human.
Do PlanetScale and Turso have an MCP server?
PlanetScale: yes (official). Turso: yes (official).
Can an AI agent delete its PlanetScale or Turso account?
PlanetScale: yes, in a browser. 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.