Head to head · Forms responses · October 2026 research run

Google Forms API vs Paperform

Google Forms API scores 70.8 (BB) on agent readiness against Paperform's 56 (C), and leads in every scored category. Both do forms responses.

Which one, for what

Google Forms API BB

Good for Agents that build forms and quizzes in a Google account and read the answers back, where people already use Google Forms.

Ahead on

  • Reliability, 91 against 83
  • Schema & documentation, 78 against 69
  • Agent ergonomics, 72 against 60
  • Security & auth, 66 against 40
  • Payments & pricing, 35 against 25
  • Maintenance & community, 61 against 41
  • Transparency & trust, 80 against 54

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Push notifications go only to a Cloud Pub/Sub topic in the caller's project, which needs Cloud billing, and they carry no form or response data

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.

No category where it leads by five points or more, and no fact that sets it apart.

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 runGoogle Forms APIPaperformEdge
Reliability16%209183Google Forms API +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27869Google Forms API +9
Agent ergonomics13%16.27260Google Forms API +12
Security & auth14%17.56640Google Forms API +26
Payments & pricing10%12.53525Google Forms API +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86141Google Forms API +20
Transparency & trust7%8.88054Google Forms API +26
Negative events≤1500
Total70.8 · BB56 · C

Facts side by side

FactGoogle Forms APIPaperform
KindHTTP APIHTTP API
VendorGooglePaperform Pty Ltd
Hosted endpointhttps://forms.googleapis.com/v1https://api.paperform.co/v1
TransportsHTTPHTTP
AuthOAuthAPI key
PricingFreePaid
x402nono
LicenceProprietary service under the Google APIs Terms of Service. The client libraries are Apache-2.0Proprietary service under Paperform's General Terms and Conditions of Use
Tools exposed0none
Read-only variant documentedyesno
llms.txtnoyes
Last release2026-09-242026-09-16
Terms last updated2021-11-092025-09-24
Privacy policy last updated2026-10-012025-07-10
Customer content may train modelsyesyes
Terms restrict automated accessyesyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity32k npm/wknone

Verdicts

Google Forms API

Six OAuth scopes separate form structure from responses, and batchUpdate applies a batch atomically with a revision check. Notifications go only to a Cloud Pub/Sub topic and carry no response data, the API can't list forms or create file upload questions, and the release notes were last updated on 8 April 2025.

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

Google Forms API

  1. Call forms.create with a title only, then add items with forms.batchUpdate. Any other field in the create body is disallowed
  2. Publish with forms.setPublishSettings before sharing. Google's notice says forms created through the API after 30 June 2026 start unpublished
  3. Pass pageSize on forms.responses.list. With none set a page can hold up to 5,000 responses. Use filter=timestamp > N to fetch only new ones
  4. After a Pub/Sub notification, call forms.responses.list yourself. The message holds only formId, watchId and eventType. Renew each watch within seven days
  5. Send writeControl.requiredRevisionId on forms.batchUpdate, and read the form before retrying a timed-out forms.create, which has no idempotency key

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, Google Forms API or Paperform?

Google Forms API scores 70.8 (BB) on agent readiness against Paperform's 56 (C), and leads in every scored category.

Do Google Forms API and Paperform need an API key?

Google Forms API uses an OAuth sign-in. Paperform needs an API key.

Can an agent call Google Forms API and Paperform without installing anything?

Yes. Google Forms API has a hosted endpoint at https://forms.googleapis.com/v1 and Paperform at https://api.paperform.co/v1.

Other comparisons with Google Forms API 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.