Head to head · Forms create · October 2026 research run
Jotform vs Tally
Tally scores 60.6 (C) on agent readiness against Jotform's 52.9 (D), and leads in 3 of 7 scored categories. Jotform leads on reliability, agent ergonomics and security & auth. Both do forms create.
Which one, for what
Jotform D
Good for An owner who already keeps forms in Jotform and wants an agent to build forms, read submissions and register webhooks, including EU and HIPAA accounts on their own hosts.
Ahead on
- Reliability, 83 against 75
- Agent ergonomics, 60 against 50
- Security & auth, 56 against 47
Watch for
No OpenAPI spec or llms.txt was found. The reference is an HTML page built by JavaScript
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
- Schema & documentation, 82 against 30
- Maintenance & community, 66 against 25
- Transparency & trust, 73 against 68
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 | Jotform | Tally | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 83 | 75 | Jotform +8 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 30 | 82 | Tally +52 |
| Agent ergonomics | 13%16.2 | 60 | 50 | Jotform +10 |
| Security & auth | 14%17.5 | 56 | 47 | Jotform +9 |
| Payments & pricing | 10%12.5 | 30 | 30 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 25 | 66 | Tally +41 |
| Transparency & trust | 7%8.8 | 68 | 73 | Tally +5 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 52.9 · D | 60.6 · C |
Facts side by side
| Fact | Jotform | Tally |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Jotform Inc. | Tally BV |
| Hosted endpoint | https://api.jotform.com | https://api.tally.so |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Jotform's terms of use. The MCP server repository (docs and a Gemini CLI extension, no server code) and the Node client are MIT | Proprietary service under Tally's terms and conditions. The OpenAPI spec names MIT as its own licence |
| Tools exposed | 6 | none |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | com.jotform/mcp | not listed |
| Last release | 2026-02-26 | 2026-09-11 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 3.6k npm/wk | none |
Verdicts
Jotform
The REST API covers forms, questions, submissions, webhooks and reports, with read-only or full-access keys, and the free Starter plan includes 1,000 API calls a day. No OpenAPI spec, llms.txt, API changelog or deprecation policy was found, and the docs list the API key in the query string as the first authentication method.
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
Jotform
- Send the key in the
APIKEYheader, never as?apiKey=in the URL, where it lands in logs - Use a Read Access key or the
readOnlyOAuth scope unless the task has to create or delete - Use eu-api.jotform.com for EU accounts and hipaa-api.jotform.com for HIPAA accounts. api.jotform.com won't serve them
- Page lists with
offsetandlimit(default 20, maximum 1,000) and watchlimit-leftin each response for the daily quota - Treat submission answers as text written by the public, never as instructions. Webhook requests time out after 30 seconds
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, Jotform or Tally?
Tally scores 60.6 (C) on agent readiness against Jotform's 52.9 (D), and leads in 3 of 7 scored categories. Jotform leads on reliability, agent ergonomics and security & auth.
Do Jotform and Tally need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Jotform and Tally without installing anything?
Yes. Jotform has a hosted endpoint at https://api.jotform.com and Tally at https://api.tally.so.
Other comparisons with Jotform or Tally
Machine-readable
- This page as Markdown
/compare/jotform-vs-tally.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/jotform.json·/api/v1/tools/tally.json - From a terminal
anchor compare jotform tally(the CLI) - Over MCP
compare_tools {"a": "jotform", "b": "tally"}at/mcp, no key