Niches · Forms, surveys & structured intake
Trust the answers without parsing text
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
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 9
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.
| Listing | Why |
|---|---|
| Alchemer F 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. source |
| Formbricks D 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. source |
| Formstack E 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. source |
| Jotform E 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. source |
| Paperform C 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. source |
| SurveyMonkey D 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. source |
| Tally C 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. source |
| Typeform C 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. source |
| Wufoo D 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. source |
Doesn't do this job 2
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Fillout E 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. source |
| Google Forms API BB 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. source |
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)
The same as data: /api/v1/use-cases/forms.validate-answers.json, or the MCP tool get_use_case with id forms.validate-answers. Other jobs in this category: /api/v1/niches?category=forms.
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.