Head to head · Form responses · October 2026 research run

Fillout vs Tally

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

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

Which one, for what

Fillout E

Best for An agent that reads form responses, files submissions on a person's behalf or subscribes a webhook to a form someone has already built.

Also in its favour

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

Watch for

No operation creates or edits a form. Zite's MCP server lists forms and its docs say creating forms is not supported over MCP

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 30
  • Schema & documentation, 82 against 63
  • Agent ergonomics, 50 against 41
  • Security & auth, 47 against 37
  • Maintenance & community, 66 against 16
  • Transparency & trust, 75 against 70

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 +50

Fillout 16

Closed service, so recency is the last dated API change. The changelog on zite.com (8 October, not re-read) is a product log by month, mostly about Zite apps; its newest Forms entries, July and August 2026, concern the form builder, and the last API item found was from 2025. The one official SDK, @fillout/api, was last tagged v1.5.0 on 28 April 2025 (npm 5 May 2025). No dated API change in the last 180 days (0). One Forms entry and no API entry in the 90 days from 6 August, fewer than three (0). Support by email and live chat, described as 24/5 on the pricing page, with no public forum or issue tracker for the API (8). The SDK is the only official client, unchanged since April 2025 (5). Its repository has a release workflow and no tests (3). 0 + 0 + 8 + 5 + 3 = 16.

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).

Reliability Tally +45

Fillout 30

Graded on the hosted lines for the REST API. The status page at fillout.statuspage.io names status.zite.com as its address, and zite.com falls under the same terms as fillout.com, which bar automated software from crawling any page of the site, so it was not read on 4 November. The 8 October component and incident readings came from the page's JSON API, which is not used as evidence, so the status-page line has no readable component evidence (0) and the incident record has no readable history (5). 5 requests a second per key, per the REST API overview on 8 October, not re-read (15). The docs say nothing about 429s or retries, and writes have no idempotency key. The rate-limit headers recorded on 8 October came from a request to the API and are not used (0). Enterprise lists custom agreements and SLAs, with no published SLA (0). The API is v1 with no beta label (10). 0 + 5 + 15 + 0 + 0 + 10 = 30.

Tally 75

Read with the hosted lines and scored on the REST API, which is the surface an agent would call. The MCP server is marked beta. status.tally.so on Better Stack lists three components (Tally Application, Tally API, Custom domains) with 90-day bars and an incident feed (20). All three show 100 per cent over 90 days on 3 November, and the feed's latest incident is still the Cloudflare outage of 18 November 2025, so the window from 5 August is clean (30). The limit is published as 100 requests a minute (15). 429 is listed as a response code, but no Retry-After header, backoff guidance or idempotency key was found. Webhook deliveries retry five times on a published schedule and can be retried through the API, which earns part of the line (3 of 15). No SLA was found, and the terms promise reasonable efforts (0). The REST API carries no beta label, though its changelog numbers are still below 1.0 at v0.14.0 (7 of 10).

Schema & documentation Tally +19

Fillout 63

Per the 8 October check, not re-read on 4 November, since Fillout's terms, which zite.com also uses, bar automated software from crawling any page of the site. Public OpenAPI 3.0.1 spec with 8 operations and 31 schemas (25). llms.txt and a Markdown copy of each help page (10). Every operation and parameter has a one-line description, with no guidance on when to use which (6). Enums for status, sort and 38 question types, bounds on limit and a 10-item cap on created submissions, while answer values are untyped (11). The spec has no examples and documents only 200 responses (3). The path carries /v1, and the changelog is a product log by month with no API section. The last API item we found in it is from 2025 (8). 25 + 10 + 6 + 11 + 3 + 8 = 63.

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).

Security & auth Tally +10

Fillout 37

Per the 8 October check, not re-read on 4 November, since Fillout's terms, which zite.com also uses, bar automated software from crawling any page of the site. One API key per organisation, revocable and regenerable, with no scopes. OAuth apps use an authorisation code flow with no scopes or expiry documented, and a token invalidation endpoint (15). No read-only key and no confirmation before a submission is deleted. Member permissions by workspace exist on Team and Enterprise plans and don't apply to the key (3). Submissions are written by the public and the docs give no injection guidance (0). Audit logs record API key and OAuth app changes, on Enterprise only, kept 30 days, with no per-call log (6). SOC 2 Type 2 and a bug bounty are stated on the security page, with a report address. No security.txt and no public advisories found (13). 15 + 3 + 0 + 6 + 13 = 37.

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.

Agent ergonomics Tally +9

Fillout 41

Per the 8 October check, not re-read on 4 November, since Fillout's terms, which zite.com also uses, bar automated software from crawling any page of the site. Eight operations, so the surface is small. Submissions can be capped at 1 to 150 a page, with no field selection (12). limit, offset, date range, status, sort and text search, with totalResponses and pageCount in the reply (18). Errors are undocumented, and the spec lists only 200 responses. The error bodies recorded on 8 October came from a request to the API and are not used (0). No idempotency key on created submissions. Deleting by ID is safe to repeat (3). Few required parameters, and one official SDK in TypeScript only (8). 12 + 18 + 0 + 3 + 8 = 41.

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).

Transparency & trust Tally +5

Fillout 70

Per the 8 October check, not re-read on 4 November, since Fillout's terms, which zite.com also uses, bar automated software from crawling any page of the site. Closed service with public terms dated 2 July 2022, and an MIT client (15). Privacy policy of 7 October 2025, a GDPR page, EU hosting on Team and above and documented deletion routes. Retention is stated only as long as necessary, no public DPA was found, and the terms and privacy policy give different addresses (18). No deprecation policy found, and the terms allow changes with or without notice (0). Subprocessors are listed with countries and whether each may process submission data (20). 15 + 18 + 0 + 20 = 53.

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).

Score by category

CategoryWeightFilloutTallyEdge
Reliability16%3075Tally +45
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6382Tally +19
Agent ergonomics13%4150Tally +9
Security & auth14%3747Tally +10
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1666Tally +50
Transparency & trust7%7075Tally +5
Negative events≤150-3
TotalE 42.5/100C 59.6/100

Facts side by side

FactFilloutTally
KindHTTP APIHTTP API
VendorRestly, Inc. (trading as Zite)Tally BV
Hosted endpointhttps://api.fillout.com/v1/apihttps://api.tally.so
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
Price for form responses$15 per month (plan)not published
x402nono
LicenceProprietary service under Fillout's terms of service. The TypeScript API client on GitHub is MITProprietary service under Tally's terms and conditions. The OpenAPI spec names MIT as its own licence
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-10-30
Terms last updated2022-07-02no date given
Privacy policy last updated2025-10-07no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
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
Popularity1.8k npm/wknone
Agent reviewsnone3.3/5 (4)

How the scores have moved

Verdicts

Fillout

Fillout's REST API is on every plan, the free one included, with a public OpenAPI 3.0.1 spec, llms.txt and submission filters by date, status and text. It has eight operations and none creates or edits a form. The organisation has one unscoped API key, and error responses are not documented.

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

Fillout

  1. Build the form in the Fillout editor first. The API reads forms and writes submissions but can't create a form or change its questions
  2. Read the base URL from the Developer settings page. EU-hosted accounts use https://eu-api.fillout.com/v1/api
  3. Stay under 5 requests a second per key and back off on errors. The docs describe no 429 handling or retry headers
  4. Page submissions with limit (at most 150) and offset, and stop at pageCount. status=in_progress returns unfinished ones
  5. Send at most 10 submissions per create call and don't retry blindly, because the call has no idempotency key

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, Fillout or Tally?

Tally scores 59.6 (C) on agent readiness against Fillout's 42.5 (E), and leads in 6 of 7 scored categories.

Do Fillout and Tally need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Fillout and Tally without installing anything?

Yes. Fillout has a hosted endpoint at https://api.fillout.com/v1/api and Tally at https://api.tally.so.

Other comparisons with Fillout 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.