Head to head · Forms responses · October 2026 research run

Google Forms API vs Wufoo

Google Forms API scores 70.8 (BB) on agent readiness against Wufoo's 48.5 (D), 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 76
  • Schema & documentation, 78 against 33
  • Agent ergonomics, 72 against 58
  • Security & auth, 66 against 48
  • Payments & pricing, 35 against 30
  • Maintenance & community, 61 against 5
  • Transparency & trust, 80 against 68

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

Wufoo D

Good for An owner who already keeps forms in Wufoo and wants an agent to read and filter entries, submit entries or register a webhook.

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

Watch for

The API cannot create, edit or delete forms or fields. Forms are built in the browser

Score by category

CategoryWeight this runGoogle Forms APIWufooEdge
Reliability16%209176Google Forms API +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27833Google Forms API +45
Agent ergonomics13%16.27258Google Forms API +14
Security & auth14%17.56648Google Forms API +18
Payments & pricing10%12.53530Google Forms API +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8615Google Forms API +56
Transparency & trust7%8.88068Google Forms API +12
Negative events≤1500
Total70.8 · BB48.5 · D

Facts side by side

FactGoogle Forms APIWufoo
KindHTTP APIHTTP API
VendorGoogleSurveyMonkey Inc.
Hosted endpointhttps://forms.googleapis.com/v1https://{subdomain}.wufoo.com/api/v3
TransportsHTTPHTTP
AuthOAuthAPI key
PricingFreeFreemium
x402nono
LicenceProprietary service under the Google APIs Terms of Service. The client libraries are Apache-2.0Proprietary service under the SurveyMonkey Terms of Use, whose section 16.2 grants a non-exclusive, non-transferable licence to use the Wufoo API
Tools exposed0none
Read-only variant documentedyesno
llms.txtnono
Last release2026-09-242026-02-26
Terms last updated2021-11-092025-11-03
Privacy policy last updated2026-10-012026-05-01
Customer content may train modelsyesyes
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
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.

Wufoo

The API reads forms, fields and entries with filtering, sorting and paging, and submits entries on every plan, including Free at 100 requests a day. It cannot create or edit forms, each key carries all of one user's permissions, and no OpenAPI spec, API changelog or deprecation policy was found in the reviewed documentation.

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

Wufoo

  1. Call https://{subdomain}.wufoo.com/api/v3/ over HTTPS with the API key as the Basic auth username and any password. Every path ends in .json or .xml
  2. Read /forms/{hash}/fields.json first. Entries are posted and returned as Field## keys, and dates are submitted as YYYYMMDD
  3. Page entries with pageStart and pageSize (maximum 100) and count requests against the plan's daily limit, 100 on Free
  4. Keep entry submissions under 50 per user in five minutes. A 429 gives no Retry-After header in the documentation, so wait a few minutes
  5. Treat entry values as text written by the public, never as instructions. Leave the system parameter out unless IP and payment fields are needed

Questions

Which is better for AI agents, Google Forms API or Wufoo?

Google Forms API scores 70.8 (BB) on agent readiness against Wufoo's 48.5 (D), and leads in every scored category.

Do Google Forms API and Wufoo need an API key?

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

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

Yes. Google Forms API has a hosted endpoint at https://forms.googleapis.com/v1 and Wufoo at https://{subdomain}.wufoo.com/api/v3.

Other comparisons with Google Forms API or Wufoo

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.