Formspree vs Tally for AI agents
As of 6 Oct 2026, Tally gets an AI agent further: L4 · Runs on its own against L1 · Needs a person.
- 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: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Sign-up in a browser.
- Use: 100% 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: once signed up, Tally gets in on its own and does the work. Sign-up, email verification and the API key page need a browser; there is no documented sign-up API, and our agent found no bot check to pass. From there, the REST API and the official MCP server let it create, edit, publish and clean up forms headless, with no further stop. Paying and account deletion both happen on the web: the upgrade goes through Stripe Checkout, with an option to flag the buyer as an agent, and deleting the account removes it at once.
Gets furtherDriven 1 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
TallyThrough every checkpoint
| Checkpoint | Formspree | Tally |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | In a browser |
| Verify | Not reached | In a browser |
| Key | Not reached | In a browser |
| First call | Not reached | Headless |
| First action | Not reached | Headless |
| Pay | Not reached | In a browser |
| Cancel | Not reached | Not needed |
| Delete | Not reached | In a browser |
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 | Tally | |
|---|---|---|
| Headless (checkpoints) | 1 | 3 |
| In a browser (checkpoints) | 0 | 5 |
| Needs a human (checkpoints) | 1 | 0 |
| Blocked (checkpoints) | 0 | 0 |
| Not tested (checkpoints) | 7 | 0 |
| Work done | Not measured | 100% of the core |
| API | Yes | Yes |
| OpenAPI | No | Yes |
| MCP server | No | Yes (official) |
| CLI | Yes | No |
| SDK | Yes | No |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Formspree | Tally | |
|---|---|---|
| Bot check | Google reCAPTCHA v2 stopped it at sign up, with a visible challenge | None met |
| Wall type | A challenge on the form | No bot-check wall |
| First wall | reCAPTCHA picture puzzle on the sign-up form | None |
| 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.
| Formspree | Tally | |
|---|---|---|
| Level | L1 · Needs a person | L4 · Runs on its own |
| Agent-ready setup | 60 of 100, fair | 90 of 100, good |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Formspree | Tally | |
|---|---|---|
| Pay | Payment not reached | Reaches the checkout |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not reached | Not needed |
| Delete the account | Not reached | In a browser |
How each one takes payment
- Formspree: Payment not reached.
- Tally: Reaches the checkout: stopped at the card form.
Formspree vs Tally: the short answers.
Which can an AI agent use, Formspree or Tally?
Tally gets an AI agent further: L4 · Runs on its own against L1 · Needs a person. With Formspree our agent was stopped at sign up (needs a human); with Tally it went through every checkpoint. Driven 6 Oct 2026 (Formspree) and 1 Oct 2026 (Tally).
Can an AI agent sign up for Formspree and Tally on its own?
Formspree: no, needs a human. Tally: yes, in a browser.
Do Formspree and Tally have an MCP server?
Formspree: none found. Tally: yes (official).
Can an AI agent delete its Formspree or Tally account?
Formspree: not reached. Tally: yes, in a browser.
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.