# Read back every response, labelled

> Read back every response, labelled: 2 companies fully do it, 8 with a limit, 10 carry the tag. Every listing in Forms, surveys & structured intake with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/forms.read-responses/
- Markdown: https://www.anchorterminal.com/niches/forms.read-responses/index.md (~1,200 tokens)
- Slim: https://www.anchorterminal.com/niches/forms.read-responses/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/forms.read-responses/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

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 8 | 10 | 19 | 5 |

## What counts as done

Every response since a point in time, each answer labelled with its question and typed value, with no duplicates or gaps across pages, using cursor or since parameters.

How agents ask for it: how many people signed up; export all responses since Monday; who answered no to question 3

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Fillout (Restly, Inc.)**: GET submissions returns each answer with question id, name, type and value, filters with afterDate, beforeDate, status and search, and pages by limit and offset with sort, on the free plan.
- **Tally (Tally BV)**: Listing submissions returns responses with the form's questions array for labels, filters by startDate and status, and afterId fetches only submissions after a known one, so a since read has no gaps.

## 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)**: surveyresponse lists with page and resultsperpage and filters on date_submitted and status, but paging is by page number, GETs cache for 60 seconds, and the plan gate applies.
- **Formbricks (Formbricks GmbH)**: list_responses and the v2 responses API read answers, but v2 pages by limit and skip, an offset that can shift as responses arrive, and labels depend on question codes added in 6.2.
- **Formstack (Intellistack, LLC)**: Submissions list by pageNumber and pageSize with minTime and maxTime and prettyName for labelled answers. Page-number paging can shift as submissions arrive, and the API is Enterprise-gated.
- **Google Forms API (Google LLC)**: responses.list pages by pageToken with filter timestamp > N, so a since read has no gaps, but answers are keyed by questionId only and must be labelled from a forms.get (acc-19, acc-21).
- **Jotform (Jotform Inc.)**: GET form submissions pages by offset and limit with filter and orderby, and each answer carries its question text, type and prettyFormat. Paging is by offset, and acc-16 shows a client dropping the paging parameters so the first page repeated.
- **Paperform (Paperform Pty Ltd)**: Submissions list with after_id and before_id cursors and limit up to 100, with data keyed by field key and a fields endpoint for labels. The API needs the Pro plan or above, and labels take a second call.
- **SurveyMonkey (SurveyMonkey Inc.)**: Responses page by page and per_page with start_created_at and start_modified_at filters, but bulk answers carry question and choice ids only, and Basic accounts get error 1005 after 25 responses a survey.
- **Typeform (Typeform SL)**: Retrieve responses takes since, until, before and after with page_size, but the reference points to webhooks for real-time data, answers are keyed by field id and ref so labels need the form, and acc-13 (open) shows min and max selection missing from the form read.
- **Wufoo (SurveyMonkey Inc.)**: Entries page by pageStart and pageSize up to 100 with Filter by field or date, but answers come as Field## keys labelled by a separate fields call, and offset paging can shift as entries arrive.

## What stops agents finishing

- pagination repeats pages
- answers only keyed by question id
- API access only on a higher plan

## Around it

Before: forms.build-from-description. After: spreadsheets.append-rows, crm.update-contact, forms.summarise-results.

## Where this comes from

Weight 19 of 100 in Forms, surveys & structured intake: 5 of 25 accounts (Jotform pagination, Google Forms question-id mapping, Typeform backfill)

As data: https://www.anchorterminal.com/api/v1/use-cases/forms.read-responses.json, or the MCP tool get_use_case with id forms.read-responses. 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
