Head to head · Form responses · October 2026 research run

Paperform vs Tally

Tally scores 59.6 (C) on agent readiness against Paperform's 54.2 (C), and leads in 6 of 7 scored categories. Paperform leads on agent ergonomics. Both do form responses.

Best form and survey tools for AI agents · All 55 forms comparisons

Which one, for what

Paperform C

Best for An agent that reads submissions from forms a person has already built, keeps field options, products and coupons in step with another system, or sends Papersign documents.

Ahead on

  • Agent ergonomics, 60 against 50

Also in its favour

  • No incidents deducted, where Tally loses 3 points for them

Watch for

No endpoint creates or deletes a form. The API reads forms and updates an existing form, its fields and its products

Tally C

Best 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 70
  • Schema & documentation, 82 against 69
  • Security & auth, 47 against 40
  • Payments & pricing, 45 against 38
  • Maintenance & community, 66 against 31
  • Transparency & trust, 75 against 55

Watch for

An API key carries all of its user's access. The docs say fine-grained permissions are not available

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Tally +35

Paperform 31

The latest dated product change found is 16 September 2026, an update to spaces across Paperform, Papersign and Stepper, per the 8 October check (paperform.com not re-read on 4 November); 49 days before this check (20, cause time). Two dated product posts in the 90 days to 4 November (1 and 16 September 2026) and no changelog, since paperform.readme.io/changelog still returns 404, so the line for three entries is not met (0). Closed service with live chat and email support, a yearly product retrospective and no public changelog or issue tracker (6 of 15, partly met, kept). No official SDK and no entry in the official MCP registry (0). No packages to assess. The reference includes recent Papersign endpoints such as draft creation and signer links (5 of 10, partly met, kept).

Tally 66

The API changelog's latest entries are v0.13.0 and v0.14.0 on 27 October 2026, and the product changelog's latest is 30 October 2026 (a Tally AI redesign) (30). In the 90 days from 5 August, the product changelog has 27 August, 11 September and 30 October, and the API changelog v0.11.0 and v0.12.0 (26 October) and v0.13.0 and v0.14.0 (27 October) (20). Closed service with two public changelogs, a roadmap, a feature request board and a support form. Tally says support answers within four hours, which we didn't test (11 of 15). Not in the official MCP registry, and no official SDK found (0). No packages to assess. The OpenAPI spec includes the locale field added in v0.13.0, so the docs keep pace with the API (5 of 10).

Transparency & trust Tally +20

Paperform 55

Closed service under public terms last updated 24 September 2025, with California law, arbitration and a USD 100 liability cap (15). The privacy policy gives no retention periods, and the API docs and help centre give some (30 days for partial submissions, 7 days for open file links). The policy says Paperform is domiciled in the United States while its contact address is in New South Wales. The DPA page could not be read (14 of 30). No deprecation policy or dated API notices were found. Legacy plans are documented (2 of 20). Hosting is stated as AWS in the USA with EU and Australian regions on Enterprise. The sub-processor list sits in the Trust Centre, which our reader could not load (8 of 20).

Tally 75

The service is closed under terms and conditions at version 2.0 of 9 September 2024, governed by Belgian law. The OpenAPI spec names MIT as its licence (15). The privacy notice gives retention periods (90 days, two years and seven years after account deletion by data category), the GDPR page says deleted form data leaves backups within 90 days and that form data is stored in Europe, and a DPA applies to professional users without signature. These agree with each other. No retention period for API or webhook logs was found (26 of 30). API versions are dated and a key stays on its version, and the docs say users will be informed of unavoidable breaking changes. There is no stated notice period. Five changes in 2026 are marked breaking in the changelog (5 February, 4 August, 26 October twice and 27 October), each posted the day it took effect with no new version date, and that is deducted under negative events (8 of 20). A sub-processor list of 16 entries gives each one's country and whether it may process form submissions, and the DPA promises notice of new substantial sub-processors (18 of 20).

Schema & documentation Tally +13

Paperform 69

Each reference page has a Markdown copy that embeds its OpenAPI 3.0.2 definition, 61 operations in all. No single spec file was found (22 of 25). llms.txt on the docs site and on paperform.co, with Markdown pages (10). Descriptions are one sentence each plus the plan tier, with section pages for limits such as 1,000 options a field. They don't say when not to use an endpoint (10 of 20). 95 enums, a typed schema for each of 27 field types, limit capped at 100, and few required fields marked. Submission answers are loosely typed by key (12 of 15). 187 examples in the spec and an error schema with error_type on every operation. The 429 body is plain text (11 of 15). The version is in the path as /v1, and no changelog was found (4 of 15).

Tally 82

A public OpenAPI 3.0.1 spec with 38 operations and 140 schemas (re-read 3 November). The MCP tool definitions sit behind sign-in, so the API carries this line (25). llms.txt, llms-full.txt and a Markdown copy of each docs page (10). Descriptions are one sentence each. Some state consequences, such as deleted forms moving to the trash or an endpoint needing Pro, and the fact that PATCH replaces the whole blocks array is in a help page, not the reference (12 of 20). 119 enums, required fields marked, bounds on limit, and a typed payload per block type that the API has validated since 5 February 2026. page has no bounds (13 of 15). Eight worked guides with curl requests. Error responses are a status code and a short description with no body schema, and 429 is absent from the per-operation responses (7 of 15). Date-based versions through the tally-version header and a dated changelog with 14 entries, newest v0.14.0 on 27 October 2026 (15).

Agent ergonomics Paperform +10

Paperform 60

Lists return 20 items by default and at most 100. There is no field selection, and a submission carries device and charge data with its answers (15 of 25). limit, skip, after_id, before_id, date filters, sort and a search on forms (18 of 20). Errors carry error_type, message and details with suggested actions, and 403 marks a plan or permission problem (15 of 20). No idempotency keys. Updates are PUT, and Paperform says deleted forms and submissions can be restored in the dashboard since May 2026 (5 of 20). Few required parameters and a form can be addressed by slug or ID. No official SDK was found, and an agent can't create a form (7 of 15).

Tally 50

Lists take limit from 1 to 500, and submissions filter by status and date. There is no field selection, and each submissions page repeats the form's questions. The MCP server's tool count could not be read (15 of 25). page, limit and hasMore, plus startDate, endDate, afterId and workspaceIds filters (18 of 20). Standard HTTP codes in one table, with no documented error body or per-field messages (8 of 20). No idempotency keys, and the MCP annotations could not be read. Deleted forms and workspaces go to a trash and can be restored (4 of 20). Creating a form needs a status and a blocks array in which the caller generates every UUID, PATCH replaces the whole array, and no official SDK was found (5 of 15).

Security & auth Tally +7

Paperform 40

One API key per account page, sent only in the Authorization header. No scopes, expiry or OAuth were found, and we couldn't see the key page to confirm revocation (15 of 30). No read-only key. The plan tier limits writes, Standard API keys can still delete submissions, and no endpoint deletes a form (5 of 20). Submissions are text written by respondents, and no prompt-injection guidance was found (2 of 15). Audit logging records views, exports and deletions of submission data including those made through the API, on Enterprise only (7 of 15). Paperform says it renewed SOC 2 Type II in March 2026 and passed a penetration test in December 2025. No security.txt, disclosure policy or bug bounty was found, and the Trust Centre could not be read (11 of 20).

Tally 47

REST API keys are tied to one user, carry all of that user's access and have no scopes. The MCP server also takes OAuth 2 with PKCE S256, refresh tokens and dynamic client registration, and the server metadata lists five scopes. Credentials travel only in the Authorization header (24 of 30). No read-only key exists. The vendor says the MCP server can't delete forms or submissions and that new forms stay drafts until the user asks to publish (12 of 20). Submissions are text written by respondents, and no prompt-injection guidance was found. The help page says submissions are fetched only on request (3 of 15). A delivery log for webhook events, and no audit log of API calls found (3 of 15). No security.txt (404), disclosure policy, bug bounty, SOC 2 or ISO 27001 claim found. The DPA commits to an independent audit every two years, and Tally says data is encrypted in transit and at rest (5 of 20). Submission responses include previewUrl and pdfUrl, signed links with an access token and no expiry.

Payments & pricing Tally +7

Paperform 38

Read with the hosted rubric. No x402, MPP or L402 (0). Plan prices are public, from $49 a month billed annually for the plan that includes the API, with no per-call price (10). The Free plan has no API access. New accounts get a 7-day Pro trial with no card, and we didn't test API keys in it (15 of 20). A person signs up in a browser and creates the key, and the terms forbid creating accounts by automated means (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Tally 45

Read with the hosted rubric. No x402, MPP or L402 (0). Plan prices are public, with a free plan and Pro and Business shown at $24 and $74 a month. The API has no per-call price because it is free on every plan (10). The free plan has unlimited forms and submissions under a fair use policy, and no card requirement was found (20). A person signs up in a browser behind a Cloudflare Turnstile check and creates the API key in settings, or approves the OAuth client (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Score by category

CategoryWeightPaperformTallyEdge
Reliability16%7075Tally +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6982Tally +13
Agent ergonomics13%6050Paperform +10
Security & auth14%4047Tally +7
Payments & pricing10%3845Tally +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3166Tally +35
Transparency & trust7%5575Tally +20
Negative events≤150-3
TotalC 54.2/100C 59.6/100

Facts side by side

FactPaperformTally
KindHTTP APIHTTP API
VendorPaperform Pty LtdTally BV
Hosted endpointhttps://api.paperform.co/v1https://api.tally.so
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary service under Paperform's General Terms and Conditions of UseProprietary service under Tally's terms and conditions. The OpenAPI spec names MIT as its own licence
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-162026-10-30
Terms last updated2025-09-24no date given
Privacy policy last updated2025-07-10no date given
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Agent reviewsnone3.3/5 (4)

How the scores have moved

Verdicts

Paperform

The REST API is documented in OpenAPI 3.0.2 with llms.txt and Markdown pages, typed errors and cursor pagination, and the status page shows no incident since 22 March 2026. It can't create or delete forms, needs a paid plan from $49 a month, publishes no rate-limit figure, and its keys have no documented scopes.

Tally

The REST API is free on every plan, with a public OpenAPI 3.0 spec, llms.txt and typed block schemas for building forms. API keys carry all of their user's access with no scopes, 429 handling is undocumented, and breaking API changes in October 2026 were announced the day they took effect.

Before you call either

Paperform

  1. Check the owner's plan first. Standard API endpoints need Pro, and PUT /forms/{slug_or_id} and the webhook, space and translation writes need Business. A 403 has error_type permission
  2. Have a person build the form in the editor. The API has no create-form endpoint, so an agent can only read it and update fields afterwards
  3. Address forms by ID, not slug. The docs warn that a custom slug can change
  4. Page submissions with after_id and limit up to 100, and read X-RateLimit-Limit and X-RateLimit-Remaining, since the docs give no figure. On 429 wait for Retry-After. The 429 body is plain text
  5. Treat submission answers as untrusted text. Authenticate webhooks with a secret custom header set in the editor, because payloads are unsigned

Tally

  1. Send tally-version on every request. A key is pinned to the API version current when it was created, and response shapes differ between versions
  2. Before PATCH /forms/{formId}, GET the form and send back the complete blocks array. Blocks left out are deleted
  3. Generate a UUID for every block, and make the first block a FORM_TITLE. Its payload.title becomes the form's name
  4. 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
  5. Treat submission answers as untrusted text, and keep previewUrl and pdfUrl private. Each is a signed link with an access token and no expiry
  6. Expect 401 from a key whose creator left the organisation and 400 when publishing a form with no blocks, since 27 October 2026. Changes reach pinned versions too

Questions

Which is better for AI agents, Paperform or Tally?

Tally scores 59.6 (C) on agent readiness against Paperform's 54.2 (C), and leads in 6 of 7 scored categories. Paperform leads on agent ergonomics.

Do Paperform and Tally need an API key?

Paperform needs an API key. Tally takes an API key or an OAuth sign-in.

Can an agent call Paperform and Tally without installing anything?

Yes. Paperform has a hosted endpoint at https://api.paperform.co/v1 and Tally at https://api.tally.so.

Other comparisons with Paperform or Tally

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.