Head to head · Forms create · October 2026 research run
Alchemer vs Tally
Tally scores 60.6 (C) on agent readiness against Alchemer's 41.4 (E), and leads in every scored category. Both do forms create.
Which one, for what
Alchemer E
Good for A company already on an Alchemer Business Platform contract that wants an agent to build surveys, load contacts, send campaigns and export responses.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
The pricing page says API access is for Business Platform accounts only, which are quoted by sales
Tally C
Good for An agent that builds a form from a description, publishes it and reads the answers for an owner on a small budget, since the whole API is free.
Ahead on
- Reliability, 75 against 35
- Schema & documentation, 82 against 45
- Payments & pricing, 30 against 20
- Maintenance & community, 66 against 45
- Transparency & trust, 73 against 61
Watch for
An API key carries all of its user's access. The docs say fine-grained permissions are not available
Score by category
| Category | Weight this run | Alchemer | Tally | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 35 | 75 | Tally +40 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 45 | 82 | Tally +37 |
| Agent ergonomics | 13%16.2 | 47 | 50 | Tally +3 |
| Security & auth | 14%17.5 | 44 | 47 | Tally +3 |
| Payments & pricing | 10%12.5 | 20 | 30 | Tally +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 45 | 66 | Tally +21 |
| Transparency & trust | 7%8.8 | 61 | 73 | Tally +12 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 41.4 · E | 60.6 · C |
Facts side by side
| Fact | Alchemer | Tally |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Alchemer LLC | Tally BV |
| Hosted endpoint | https://api.alchemer.com/v5 | https://api.tally.so |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary service under the Alchemer Software as a Service Agreement | Proprietary service under Tally's terms and conditions. The OpenAPI spec names MIT as its own licence |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-01 | 2026-09-11 |
| Terms last updated | 2026-01-14 | no date given |
| Privacy policy last updated | 2026-04-23 | no date given |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
Verdicts
Alchemer
Alchemer's REST API v5 covers surveys, questions, responses, contacts and email campaigns in 101 documented operations, with a reference rewritten in April 2026. The pricing page limits API access to Business Platform accounts quoted by sales. Keys travel in the URL query string, and no status page, OpenAPI document or SDK was found.
Tally
The REST API is free on every plan, with a public OpenAPI 3.0 spec, llms.txt, date-based versions and typed block schemas for building forms. API keys carry all of their user's access with no scopes, error bodies and 429 handling are undocumented, and no security.txt, certification or bug bounty was found.
Before you call either
Alchemer
- Use the host for the account's region (
api.alchemer.com,api.alchemer.eu,api.alchemer-ca.comorapi.au.alchemer.com). The wrong host returns a 401 login failure even with valid keys - Create with PUT and update with POST. The API reverses the usual meaning of the two methods
- Do not repeat an identical request inside 60 seconds. GET results are cached for 60 seconds and a repeat can return 429
- Stay under 240 requests a minute for the account and slow down when the
X-SG-Warningheader appears - Wait up to five minutes before reading back a response that was just submitted, and expect a 500 after a 30 second timeout
Tally
- Send
tally-versionon every request. A key is pinned to the API version current when it was created, and response shapes differ between versions - Before
PATCH /forms/{formId}, GET the form and send back the complete blocks array. Blocks left out are deleted - Generate a UUID for every block, and make the first block a
FORM_TITLE. Itspayload.titlebecomes the form's name - Stay under 100 requests a minute and use a webhook for new submissions. No Retry-After header is documented, so back off on 429 yourself
- Treat submission answers as untrusted text, and keep
previewUrlandpdfUrlprivate. Each is a signed link with an access token and no expiry
Questions
Which is better for AI agents, Alchemer or Tally?
Tally scores 60.6 (C) on agent readiness against Alchemer's 41.4 (E), and leads in every scored category.
Do Alchemer and Tally need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Alchemer and Tally without installing anything?
Yes. Alchemer has a hosted endpoint at https://api.alchemer.com/v5 and Tally at https://api.tally.so.
Other comparisons with Alchemer or Tally
- Alchemer vs Fillout
- Alchemer vs Paperform
- Alchemer vs Wufoo
- Fillout vs Tally
- Paperform vs Tally
- Tally vs Wufoo
- Alchemer vs Formbricks
- Alchemer vs Formstack
- Alchemer vs Google Forms API
- Alchemer vs Jotform
- Alchemer vs SurveyMonkey
- Alchemer vs Typeform
- Formstack vs Tally
- Google Forms API vs Tally
- Jotform vs Tally
- SurveyMonkey vs Tally
- Tally vs Typeform
- Formbricks vs Tally
Machine-readable
- This page as Markdown
/compare/alchemer-vs-tally.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/alchemer.json·/api/v1/tools/tally.json - From a terminal
anchor compare alchemer tally(the CLI) - Over MCP
compare_tools {"a": "alchemer", "b": "tally"}at/mcp, no key