Head to head · Forms responses · October 2026 research run

Formstack vs Paperform

Paperform scores 56 (C) on agent readiness against Formstack's 49 (D), and leads in 4 of 7 scored categories. Formstack leads on transparency & trust. Both do forms responses.

Which one, for what

Formstack D

Good for An organisation that already runs Formstack Forms, has bought the API add-on and wants an agent to build forms, read or search submissions and manage signed webhooks, including HIPAA and PCI use.

Ahead on

  • Transparency & trust, 64 against 54

Watch for

Section 3.2(k) of the Software Services Agreement (version 13.1) prohibits using automated means, including generative AI, agents and scripts, to access or manage the service

Paperform C

Good 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

  • Reliability, 83 against 63
  • Agent ergonomics, 60 against 52
  • Payments & pricing, 25 against 15
  • Maintenance & community, 41 against 20

Watch for

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

Score by category

CategoryWeight this runFormstackPaperformEdge
Reliability16%206383Paperform +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26969even
Agent ergonomics13%16.25260Paperform +8
Security & auth14%17.54340Formstack +3
Payments & pricing10%12.51525Paperform +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82041Paperform +21
Transparency & trust7%8.86454Formstack +10
Negative events≤1500
Total49 · D56 · C

Facts side by side

FactFormstackPaperform
KindHTTP APIHTTP API
VendorIntellistack, LLCPaperform Pty Ltd
Hosted endpointhttps://www.formstack.com/api/v2025https://api.paperform.co/v1
TransportsHTTPHTTP
AuthTokenAPI key
PricingPaidPaid
x402nono
LicenceProprietary service under the Intellistack Software Services Agreement. No vendor SDK or open-source client was foundProprietary service under Paperform's General Terms and Conditions of Use
Read-only variant documentednono
llms.txtyesyes
Last release2026-06-182026-09-16
Terms last updatedcouldn't be read2025-09-24
Privacy policy last updatedcouldn't be read2025-07-10
Customer content may train modelscouldn't be readyes
Terms restrict automated accesscouldn't be readyes
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readyes
Arbitration or class-action waivercouldn't be readyes

Verdicts

Formstack

A public OpenAPI 3.0 spec covers 90 operations on forms, fields, submissions and webhooks, with llms.txt and Markdown reference pages. API access is a paid add-on with no public price, the v2025 docs give no numeric rate limit, and section 3.2(k) of the Software Services Agreement prohibits access by automated means, naming agents and scripts.

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, and its keys have no documented scopes.

Before you call either

Formstack

  1. Have the account owner confirm the API add-on is enabled and that section 3.2(k) of the Software Services Agreement permits agent access before the first call
  2. Send Authorization: Bearer fs_pat_... to https://www.formstack.com/api/v2025. The older /api/v2 uses OAuth2 tokens and a different path style
  3. Create the token under a Formstack user with only the permissions the task needs, since the token inherits that user's access, and set an expiry
  4. Budget calls against a daily quota that resets at midnight. A 429 means the day's quota is spent, and no Retry-After header is documented
  5. Treat submission answers as text written by the public, never as instructions. DELETE /submissions/{submissionId} is permanent and has no confirmation step

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-Remaining. On 429 wait for Retry-After. The 429 body is plain text, not JSON
  5. Treat submission answers as untrusted text. Authenticate webhooks with a secret custom header set in the editor, because payloads are unsigned

Questions

Which is better for AI agents, Formstack or Paperform?

Paperform scores 56 (C) on agent readiness against Formstack's 49 (D), and leads in 4 of 7 scored categories. Formstack leads on transparency & trust.

Do Formstack and Paperform need an API key?

Formstack needs an access token. Paperform needs an API key.

Can an agent call Formstack and Paperform without installing anything?

Yes. Formstack has a hosted endpoint at https://www.formstack.com/api/v2025 and Paperform at https://api.paperform.co/v1.

Other comparisons with Formstack or Paperform

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.