Fillout vs Formspree 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.
- 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 start: L1 · Needs a person. Our agent stopped first at sign-up, where Register raised a Google reCAPTCHA picture puzzle that stood unsolved. Every path to a form (dashboard, claim URL, formspree deploy with a key) runs through that account, so our agent never reached verification, a key or a form of its own; an unauthenticated POST just returned FORM_NOT_FOUND. Paying and cancelling were never reached either, since Formspree sells Professional and Business only after the same gated sign-up, with no cancel API documented. Docs stand out for an agent reading them: llms.txt with a claim-URL guide, and help articles served as Markdown.
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
FormspreeStopped at sign up: needs a human
| Checkpoint | Fillout | Formspree |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | In a browser | Needs a human |
| 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 | Formspree | |
|---|---|---|
| Headless (checkpoints) | 2 | 1 |
| In a browser (checkpoints) | 6 | 0 |
| Needs a human (checkpoints) | 0 | 1 |
| Blocked (checkpoints) | 0 | 0 |
| Not tested (checkpoints) | 0 | 7 |
| Work done | 83% of the core | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | No |
| MCP server | Yes (official) | No |
| CLI | No | Yes |
| SDK | No | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Fillout | Formspree | |
|---|---|---|
| Bot check | reCAPTCHA (invisible, v3-style) let it through at sign up | Google reCAPTCHA v2 stopped it at sign up, with a visible challenge |
| Wall type | No bot-check wall | A challenge on the form |
| First wall | None | reCAPTCHA picture puzzle on the sign-up form |
| 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.
| Fillout | Formspree | |
|---|---|---|
| Level | L4 · Runs on its own | L1 · Needs a person |
| Agent-ready setup | 90 of 100, good | 60 of 100, fair |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Fillout | Formspree | |
|---|---|---|
| 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.
- Formspree: Payment not reached.
Fillout vs Formspree: the short answers.
Which can an AI agent use, Fillout or Formspree?
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 Formspree it was stopped at sign up (needs a human). Driven 2 Oct 2026 (Fillout) and 6 Oct 2026 (Formspree).
Can an AI agent sign up for Fillout and Formspree on its own?
Fillout: yes, in a browser. Formspree: no, needs a human.
Do Fillout and Formspree have an MCP server?
Fillout: yes (official). Formspree: none found.
Can an AI agent delete its Fillout or Formspree account?
Fillout: yes, in a browser. Formspree: 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.