Niches · Forms, surveys & structured intake
Fill in a form for someone
One company's docs show a full fit.
What counts as done
A submission accepted and returned with its id in one call, visible to the form owner, or a clear refusal naming the missing field.
How agents ask for it: register me for this event
, submit this application
, file these records into the form
Does the job 1
The docs show it meets the test above, and nothing we read says otherwise.
Does the job, with a limit 6
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 | CREATE SURVEYRESPONSE takes data by question id or shortname with a status, for most question types. A refusal naming a missing field isn't documented, and the listing notes up to five minutes before a new response reads back. source |
| Fillout E Restly, Inc. | POST submissions creates up to 10 at once and returns the created submissions with ids. Whether a missing required answer is refused by name isn't documented, and a retry has no idempotency key. source |
| Formbricks D Formbricks GmbH | create_response and validate_response under responses:write record a response through MCP, and the Management API has the same. Whether a refusal names the missing field wasn't read. source |
| Formstack E Intellistack, LLC | POST /forms/{formId}/submissions creates a submission. A refusal naming a missing field isn't documented, and the API needs the Enterprise add-on. source |
| Jotform E Jotform Inc. | POST /form/{id}/submissions takes answers by question id, but acc-24 shows a submission raising no error while nothing appeared in Jotform. source |
| SurveyMonkey D SurveyMonkey Inc. | POST /collectors/{id}/responses creates a response with pages and answers, but the responses_write scope needs a paid plan, and a refusal naming a missing field isn't documented. source |
Doesn't do this job 4
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Google Forms API BB Google LLC | forms.responses has get and list only; no submit method exists, and acc-25 shows scripted submission failing on required email collection. source |
| Paperform C Paperform Pty Ltd | No create-submission endpoint is in the API index; submissions can only be read and deleted. source |
| Tally C Tally BV | The API lists, fetches and deletes submissions but has no create-submission endpoint. source |
| Typeform C Typeform SL | No create-response endpoint is in the Responses API reference or the MCP tool list; responses arrive only through the form. source |
What stops agents finishing
- form requires a signed-in respondent
- submission silently dropped
Around it
Before: crm.read-contact, document-extraction.fields-from-doc. After: email.send-confirmation.
Where this comes from
Weight 7 of 100 in Forms, surveys & structured intake: 2 of 25 accounts (Jotform from Bitrix, Google Form not owned)
The same as data: /api/v1/use-cases/forms.submit-on-behalf.json, or the MCP tool get_use_case with id forms.submit-on-behalf. 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.