Baserow vs Turso for AI agents
As of 6 Oct 2026, both reach L1 · Needs a person, and with each our agent was stopped at sign up (needs a human).
- 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 to get in: L1 · Needs a person. Our agent read the user docs, the ReDoc API reference and llms.txt on its own, then stopped at signup: the documented account endpoint answers an error demanding a Cloudflare Turnstile token, and the web form shows the same visible challenge. With no account, the key page, the first call and the first piece of work in the API or the official MCP server were never reached. Paying stays card-only through the signed-in web UI once a person sets up the account; the UI also handles cancelling, though the docs name an API route for deleting the account.
Driven 6 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.
BaserowStopped at sign up: needs a human
TursoStopped at sign up: needs a human
| Checkpoint | Baserow | Turso |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | Needs a human |
| Verify | Not reached | Not reached |
| Key | Not reached | Not reached |
| First call | Not reached | Not reached |
| First action | Not reached | Not reached |
| Pay | Not reached | Not reached |
| Cancel | Not reached | Not reached |
| Delete | Not reached | 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
| Baserow | Turso | |
|---|---|---|
| Headless (checkpoints) | 1 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 1 | 1 |
| Blocked (checkpoints) | 0 | 0 |
| Not tested (checkpoints) | 7 | 7 |
| Work done | Not measured | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | Yes |
| SDK | No | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Baserow | Turso | |
|---|---|---|
| Bot check | Cloudflare Turnstile stopped it at sign up, with a visible challenge | 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 | Cloudflare Turnstile on the sign-up form | 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.
| Baserow | Turso | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 90 of 100, good | 100 of 100, good |
| Standards | OpenAPI 3.0.3 (2 versions behind) | 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.
| Baserow | Turso | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not reached | Not reached |
| Delete the account | Not reached | Not reached |
How each one takes payment
- Baserow: Payment not reached.
- Turso: Payment not reached.
Baserow vs Turso: the short answers.
Which can an AI agent use, Baserow or Turso?
Both reach L1 · Needs a person, and with each our agent was stopped at sign up (needs a human). Both driven 6 Oct 2026.
Can an AI agent sign up for Baserow and Turso on its own?
Baserow: no, needs a human. Turso: no, needs a human.
Do Baserow and Turso have an MCP server?
Baserow: yes (official). Turso: yes (official).
Can an AI agent delete its Baserow or Turso account?
Baserow: not reached. 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.