Fillout vs Typeform for AI agents
As of 6 Oct 2026, Fillout gets an AI agent further: L4 · Runs on its own against L1 · Needs a person.
- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Sign-up in a browser.
- Use: 83% of the work.
- Pay: Reaches the checkout: Stopped at the card form.
- Leave: Leaves on its own: Nothing to cancel, deletes its account.
Through every checkpoint. Next: pay without a person
L4 · Runs on its own: our agent got in on its own and worked the API without getting stuck on any checkpoint. Signup, email verification and the key page in Settings > Developer all passed, and an invisible reCAPTCHA let our agent's browser through. Through the API it listed forms and created, searched and deleted submissions on its own; building the forms themselves (fields, logic, calculations, publish) still needs the web builder, since the MCP server has no form tools. Upgrading runs through an embedded Stripe card form, and deleting the organization removed the forms, database and submissions in one step, after which the key and MCP token were rejected.
Gets furtherDriven 2 Oct 2026 · The drive and its evidence- Find: Some docs for agents: llms.txt 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: blocked. Next: let an agent sign up on its own
A person has to set this up: L1 · Needs a person. Our agent stopped at signup, not at a visible challenge. The Okta form carries an invisible reCAPTCHA. Typeform's own registration hook denied the attempt with "Registration denied," and the app showed a misleading message suggesting an account already existed. Docs, the REST API and the official MCP server are all well documented and reachable without a browser. With no account there was no token, so no form, response or analytics work could be driven. Paying, cancelling and deleting an account were all out of reach for the same reason.
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.
FilloutThrough every checkpoint
TypeformStopped at sign up: blocked
| Checkpoint | Fillout | Typeform |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | In a browser | Blocked |
| Verify | In a browser | Not reached |
| Key | In a browser | Not reached |
| First call | Headless | Not reached |
| First action | In a browser | Not reached |
| Pay | In a browser | 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
| Fillout | Typeform | |
|---|---|---|
| Headless (checkpoints) | 2 | 1 |
| In a browser (checkpoints) | 6 | 0 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 0 | 1 |
| Not tested (checkpoints) | 0 | 7 |
| Work done | 83% of the core | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | No |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | No |
| SDK | No | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Fillout | Typeform | |
|---|---|---|
| Bot check | reCAPTCHA (invisible, v3-style) let it through at sign up | Google reCAPTCHA (invisible) on the Okta sign-up form, plus Typeform's registration inline hook stopped it at sign up, without a visible challenge |
| Wall type | No bot-check wall | A check of our network and browser |
| First wall | None | Sign-up denied by registration hook, no reason |
| 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.
| Fillout | Typeform | |
|---|---|---|
| Level | L4 · Runs on its own | L1 · Needs a person |
| Agent-ready setup | 90 of 100, good | 75 of 100, fair |
| Standards | None recorded | MCP client registration (current) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Fillout | Typeform | |
|---|---|---|
| Pay | Reaches the checkout | Payment not reached |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not needed | Not reached |
| Delete the account | In a browser | Not reached |
How each one takes payment
- Fillout: Reaches the checkout: stopped at the card form.
- Typeform: Payment not reached.
Fillout vs Typeform: the short answers.
Which can an AI agent use, Fillout or Typeform?
Fillout gets an AI agent further: L4 · Runs on its own against L1 · Needs a person. With Fillout our agent went through every checkpoint; with Typeform it was stopped at sign up (blocked). Driven 2 Oct 2026 (Fillout) and 6 Oct 2026 (Typeform).
Can an AI agent sign up for Fillout and Typeform on its own?
Fillout: yes, in a browser. Typeform: no, blocked.
Do Fillout and Typeform have an MCP server?
Fillout: yes (official). Typeform: yes (official).
Can an AI agent delete its Fillout or Typeform account?
Fillout: yes, in a browser. Typeform: 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.