# Trust the answers without parsing text

> Trust the answers without parsing text: 0 companies fully do it, 8 with a limit, 12 carry the tag. Every listing in Forms, surveys & structured intake with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/forms.validate-answers/
- Markdown: https://www.anchorterminal.com/niches/forms.validate-answers/index.md (~1,150 tokens)
- Slim: https://www.anchorterminal.com/niches/forms.validate-answers/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/forms.validate-answers/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 8 | 12 | 11 | 3 |

## What counts as done

Rules (required, min and max selections, formats) are readable from the API and enforced server side, and a retried submission is stored once.

How agents ask for it: make sure the date is valid; only accept one response per person; pick two to three options

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Alchemer (Alchemer LLC)**: Question properties set required, soft-required, min and max numbers, minimum responses and a regex inputmask, readable by GET. Whether API-created responses are checked against them isn't stated, and no idempotency is documented.
- **Formbricks (Formbricks GmbH)**: Validation rules per question type are readable in the survey and validate_response checks an answer set. The rules page describes checks at the respondent's submit, and acc-12 (required skipped via API) and acc-08 (duplicate on retry) were fixed only in July and October.
- **Formstack (Intellistack, LLC)**: Fields carry required and unique flags readable through GET fields. Server-side enforcement for API-posted submissions isn't stated, and no idempotency key exists.
- **Jotform (Jotform Inc.)**: Questions take required and validation values readable through the questions endpoints, but server-side enforcement on API submissions isn't stated, there's no idempotency, and acc-24 shows a POST accepted with nothing stored.
- **Paperform (Paperform Pty Ltd)**: Field objects are typed by a discriminator and readable by GET, but the pages read show no required or format rules in the field schema and there is no submission endpoint to retry.
- **SurveyMonkey (SurveyMonkey Inc.)**: Questions carry required and a validation object with type, min, max and sum, readable through the API. Server enforcement on API-created responses and idempotency aren't documented.
- **Tally (Tally BV)**: Blocks carry isRequired and per-type settings readable by fetching the form, but whether they are enforced server side isn't stated, and there's no submission API for a retried submit.
- **Typeform (Typeform SL)**: Fields take validations on create, but acc-13 shows min_selection and max_selection not returned when reading a form, so rules aren't fully readable, and there's no submission API to dedupe.
- **Wufoo (SurveyMonkey Inc.)**: Fields expose IsRequired and type, and API submissions must still pass field validation and form limits, returning FieldErrors. Selection and format rules beyond type aren't readable, and no idempotency key exists.

- not this job: Fillout (Restly, Inc.): The Question schema returns only id, name and type, so required flags and limits aren't readable through the API, and submissions have no idempotency key.
- not this job: Google Forms API (Google LLC): Questions carry only a required flag in the API; text, number and selection validation aren't in the resource, and there is no submission call to dedupe.

## What stops agents finishing

- validation only client side
- rules not readable through the API

## Around it

Before: forms.build-from-description. After: forms.read-responses.

## Where this comes from

Weight 11 of 100 in Forms, surveys & structured intake: 3 of 25 accounts (Formbricks duplicates and required bypass, Typeform validation not exposed)

As data: https://www.anchorterminal.com/api/v1/use-cases/forms.validate-answers.json, or the MCP tool get_use_case with id forms.validate-answers. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
