Formspree vs Typeform for AI agents
As of 6 Oct 2026, both reach L1 · Needs a person, and our agent got as far with each: with Formspree it was stopped at sign up (needs a human), with Typeform it was stopped at sign up (blocked).
- 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 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.
FormspreeStopped at sign up: needs a human
TypeformStopped at sign up: blocked
| Checkpoint | Formspree | Typeform |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | Blocked |
| 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
| Formspree | Typeform | |
|---|---|---|
| Headless (checkpoints) | 1 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 1 | 0 |
| Blocked (checkpoints) | 0 | 1 |
| Not tested (checkpoints) | 7 | 7 |
| Work done | Not measured | Not measured |
| API | Yes | Yes |
| OpenAPI | No | No |
| MCP server | No | Yes (official) |
| CLI | Yes | No |
| SDK | Yes | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Formspree | Typeform | |
|---|---|---|
| Bot check | Google reCAPTCHA v2 stopped it at sign up, with a visible challenge | 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 | A challenge on the form | A check of our network and browser |
| First wall | reCAPTCHA picture puzzle on the sign-up form | Sign-up denied by registration hook, no reason |
| 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. 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.
| Formspree | Typeform | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 60 of 100, fair | 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.
| Formspree | Typeform | |
|---|---|---|
| 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
- Formspree: Payment not reached.
- Typeform: Payment not reached.
Formspree vs Typeform: the short answers.
Which can an AI agent use, Formspree or Typeform?
Both reach L1 · Needs a person, and our agent got as far with each: with Formspree it was stopped at sign up (needs a human), with Typeform it was stopped at sign up (blocked). Both driven 6 Oct 2026.
Can an AI agent sign up for Formspree and Typeform on its own?
Formspree: no, needs a human. Typeform: no, blocked.
Do Formspree and Typeform have an MCP server?
Formspree: none found. Typeform: yes (official).
Can an AI agent delete its Formspree or Typeform account?
Formspree: not reached. 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.