Head to head · Forms create · October 2026 research run

Google Forms API vs Tally

Google Forms API scores 70.8 (BB) on agent readiness against Tally's 60.6 (C), and leads in 5 of 7 scored categories. Tally leads on maintenance & community. Both do forms create.

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 75
  • Agent ergonomics, 72 against 50
  • Security & auth, 66 against 47
  • Payments & pricing, 35 against 30
  • Transparency & trust, 80 against 73

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

Tally C

Good 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

  • Maintenance & community, 66 against 61

Watch for

An API key carries all of its user's access. The docs say fine-grained permissions are not available

Score by category

CategoryWeight this runGoogle Forms APITallyEdge
Reliability16%209175Google Forms API +16
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27882Tally +4
Agent ergonomics13%16.27250Google Forms API +22
Security & auth14%17.56647Google Forms API +19
Payments & pricing10%12.53530Google Forms API +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86166Tally +5
Transparency & trust7%8.88073Google Forms API +7
Negative events≤1500
Total70.8 · BB60.6 · C

Facts side by side

FactGoogle Forms APITally
KindHTTP APIHTTP API
VendorGoogleTally BV
Hosted endpointhttps://forms.googleapis.com/v1https://api.tally.so
TransportsHTTPHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingFreeFreemium
x402nono
LicenceProprietary service under the Google APIs Terms of Service. The client libraries are Apache-2.0Proprietary service under Tally's terms and conditions. The OpenAPI spec names MIT as its own licence
Tools exposed0none
Read-only variant documentedyesno
llms.txtnoyes
Last release2026-09-242026-09-11
Terms last updated2021-11-09no date given
Privacy policy last updated2026-10-01no date given
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
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.

Tally

The REST API is free on every plan, with a public OpenAPI 3.0 spec, llms.txt, date-based versions and typed block schemas for building forms. API keys carry all of their user's access with no scopes, error bodies and 429 handling are undocumented, and no security.txt, certification or bug bounty was found.

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

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

Questions

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

Google Forms API scores 70.8 (BB) on agent readiness against Tally's 60.6 (C), and leads in 5 of 7 scored categories. Tally leads on maintenance & community.

Do Google Forms API and Tally need an API key?

Google Forms API uses an OAuth sign-in. Tally takes an API key or an OAuth sign-in.

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

Yes. Google Forms API has a hosted endpoint at https://forms.googleapis.com/v1 and Tally at https://api.tally.so.

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