Paperform

# Fix list: Paperform

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/paperform, the October 2026 research run, assessed 8 October 2026. Grade C, 56 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on Paperform: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Security & auth, 40 out of 100, up to 10.5 more on the total

Why it scored 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 2. Payments & pricing, 25 out of 100, up to 9.4 more on the total

Why it scored 25: 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 3. Agent ergonomics, 60 out of 100, up to 6.5 more on the total

Why it scored 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 4. Maintenance & community, 41 out of 100, up to 5.2 more on the total

Why it scored 41: The latest dated product change is 16 September 2026, an update to spaces across Paperform, Papersign and Stepper (30). We found two dated product posts in the last 90 days (1 and 16 September 2026) and no changelog, 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). 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## 5. Schema & documentation, 69 out of 100, up to 5 more on the total

Why it scored 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 6. Transparency & trust, 54 out of 100, up to 4 more on the total

Made of editorial 39, provenance 69.

Why it scored 54: 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Terms of service: read, states 6 of the 7 things a reader expects, and has 4 clauses that cost points (1.1 of 10)
- Privacy policy: read, states 8 of the 8 things a reader expects, and has 1 clause that costs points (8 of 10)
- Changelog: not found (0 of 10)
- security.txt: not found (0 of 10)

## 7. Reliability, 83 out of 100, up to 3.4 more on the total

Why it scored 83: Read with the hosted lines and scored on the REST API. paperform.statuspage.io lists the API as its own component with an incident history (20). The feed's latest incident is 22 March 2026, so the last 90 days are clean (30). The docs describe a per-minute limit and four headers and give no figure. A live unauthenticated response carried `x-ratelimit-limit: 60` (8 of 15). 429 handling is documented through `Retry-After` and `X-RateLimit-Reset`. No idempotency key or retry guidance for writes was found (10 of 15). An SLA is sold on Enterprise, and its terms are not published (5 of 10). The API is version 1.0.0 with no beta label (10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- unchecked: the Trust Centre at trust.paperform.co, including the sub-processor list and the SOC 2 report. The page is a Paperform form drawn by script and returned no text.
- unchecked: the data processing agreement at paperform.co/data-processing-agreement, drawn by script.
- unchecked: the API key page at paperform.co/account/developer, which needs sign-in. Whether keys can be revoked, rotated or held more than one at a time is not established.
- unchecked: whether API keys work during the 7-day Pro trial. The pricing page calls the trial unrestricted and we did not create an account.
- unchecked: the `PUT /translations/{id}` reference page, which returned an error page. The other 60 definitions were read.
- unchecked: NVD and other advisory databases for Paperform.
- The rate limit figure of 60 a minute comes from one unauthenticated response. The limit for an authenticated key may differ by plan and is not published.
- The terms name the company only as Paperform. Paperform Pty. Ltd. appears in the privacy policy, which also says Paperform is domiciled in the United States.
- No single OpenAPI file was found, so the listing's `openapi` field is empty.

## Weaknesses

- No endpoint creates or deletes a form. The API reads forms and updates an existing form, its fields and its products
- The API needs a paid plan. Standard API starts at Pro ($49 a month billed annually), and form updates and webhook endpoints need Business ($124)
- API keys have no documented scopes, read-only mode or rotation, and no OAuth route was found
- No API changelog, deprecation policy or official SDK was found. The reference has read version 1.0.0 with no dated history
- Webhooks have no documented signature. Paperform says it doesn't record whether a delivery succeeded

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- 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`
- 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
- Address forms by ID, not slug. The docs warn that a custom slug can change
- 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
- Treat submission answers as untrusted text. Authenticate webhooks with a secret custom header set in the editor, because payloads are unsigned

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.