Airtable vs Supabase for AI agents
As of 16 Oct 2026, Airtable gets an AI agent further: L4 · Runs on its own against L1 · Needs a person.
- Find: Some docs for agents: llms.txt and an MCP server.
- Access: MCP sign-in, sign-up in a browser.
- Use: 100% of the work.
- Pay: Reaches the checkout: Stopped at the $24 a month charge.
- Leave: Leaves on its own: Nothing to cancel, deletes what it made.
Through every checkpoint. Next: pay without a person
Gets in on its own today, L4 · Runs on its own. Sign-up blocks headless requests, but our agent reached the browser form with no visible challenge and confirmed its email there. Personal access tokens, the first workspace and turning on automations all still need that browser UI. Once past those steps, the API and the official MCP server ran almost all of Airtable's core work: bases, records, schema, webhooks, automations, interfaces and forms. Upgrading opens a Stripe card form inside the app; our agent found no agent payment rail and stopped before paying. It started no plan, so there was nothing to cancel, and it deleted its account through account settings.
Gets furtherDriven 15 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: Signs up sometimes.
- Use: 100% of the work.
- Pay: Needs a person to buy: A CAPTCHA at checkout.
- Leave: Nothing to cancel: Deletes its data, but the login stays.
Got in; first wall at pay (blocked). Next: let an agent get in on its own in every drive
Supabase is a backend platform for databases, user accounts, file storage and serverless functions. Once the agent signed in with GitHub, it could do almost everything on its own through code: create a database, add users, store files, run functions, and more. It stopped at the very first step: creating an account by email showed a puzzle test it couldn't solve, so it had to use a GitHub sign-in instead, and upgrading to a paid plan hit the same kind of puzzle.
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.
AirtableThrough every checkpoint
SupabaseGot in; first wall at pay (blocked)
| Checkpoint | Airtable | Supabase |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | In a browser | In a browser |
| Verify | In a browser | Not needed |
| Key | In a browser | In a browser |
| First call | Headless | Headless |
| First action | Headless | Headless |
| Pay | In a browser | Blocked |
| Cancel | Not needed | Not needed |
| Delete | In a browser | 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
| Airtable | Supabase | |
|---|---|---|
| Headless (checkpoints) | 3 | 3 |
| In a browser (checkpoints) | 5 | 2 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 0 | 2 |
| Not tested (checkpoints) | 0 | 0 |
| Work done | 100% of the core | 100% of the core |
| API | Yes | Yes |
| OpenAPI | No | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | Yes |
| SDK | – | – |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Airtable | Supabase | |
|---|---|---|
| Bot check | HUMAN let it through at sign up | A challenge on the form stopped one way in (Email and password) |
| Wall type | No bot-check wall | A challenge on the form |
| First wall | None | 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.
| Airtable | Supabase | |
|---|---|---|
| Level | L4 · Runs on its own | L1 · Needs a person |
| Holds up | 78 of 100, fair | 82 of 100, fair |
| Agent-ready setup | 75 of 100, fair | 100 of 100, good |
| Standards | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) · MCP client registration (current) | MCP spec of 28 Jul 2026 (current) · MCP discovery (current) · MCP client registration (behind) · OpenAPI 3.0.0 (2 versions behind) |
| Security | No review in this drive | Reported privately to the owner |
Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Airtable | Supabase | |
|---|---|---|
| Pay | Reaches the checkout | Needs a person to buy |
| Free plan or trial | Trial, no card | Free plan |
| Cancel | Not needed | Not needed |
| Delete the account | In a browser | Blocked |
How each one takes payment
- Airtable: Reaches the checkout: stopped at the $24 a month charge.
- Supabase: A person has to buy: a CAPTCHA at checkout.
Airtable vs Supabase: the short answers.
Which can an AI agent use, Airtable or Supabase?
Airtable gets an AI agent further: L4 · Runs on its own against L1 · Needs a person. With Airtable our agent went through every checkpoint; with Supabase it got in and met its first wall at pay (blocked). Driven 15 Oct 2026 (Airtable) and 16 Oct 2026 (Supabase).
Can an AI agent sign up for Airtable and Supabase on its own?
Airtable: yes, in a browser. Supabase: yes, in a browser, but a later step stopped it.
Do Airtable and Supabase have an MCP server?
Airtable: yes (official). Supabase: yes (official).
Can an AI agent delete its Airtable or Supabase account?
Airtable: yes, in a browser. Supabase: 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.