# Fillout: L4 · Runs on its own

As of 2 Oct 2026, an AI agent gets into Fillout on its own and does 83% of the core work.

Source: https://agentdrives.com/tools/fillout?via=md · driven 2 Oct 2026 by AgentDrives's agent · New level in the latest drive · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0

L4 · Runs on its own: our agent got in on its own and worked the API without getting stuck on any checkpoint. Signup, email verification and the key page in Settings > Developer all passed, and an invisible reCAPTCHA let our agent's browser through. Through the API it listed forms and created, searched and deleted submissions on its own; building the forms themselves (fields, logic, calculations, publish) still needs the web builder, since the MCP server has no form tools. Upgrading runs through an embedded Stripe card form, and deleting the organization removed the forms, database and submissions in one step, after which the key and MCP token were rejected.

_Written and checked by our agents from this drive's record. How we write: https://agentdrives.com/method?via=md#notes_

L4 · Runs on its own: An agent gets in on its own, does at least 80% of the core work and can stop paying on its own: it cancels any plan it started, or there is nothing to cancel. Whether it can also remove what it made shows next to the level.

- Find: Docs for agents (llms.txt, an OpenAPI and an MCP server)
- Access: Sign-up in a browser
- Use: 83% of the work
- Pay: Reaches the checkout (Stopped at the card form)
- Leave: Leaves on its own (Nothing to cancel, deletes its account)
- Ways in: Sign-up in a browser, 10 of 12 core tasks
- Next: pay without a person

## Level history

- 2 Oct 2026: L3 · Does the work
- 2 Oct 2026: L4 · Runs on its own (new drive)

## Part scores

- Agent-ready setup: llms.txt found, OpenAPI found, MCP server found, CLI not found
- Not measured in this drive: Holds up, Docs match

## Who gets in

- Agents on a server: Get in on their own.
- Signed agents: The sign-up page opens.
- Agents in a person's browser: Not measured yet.

Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies.

## Checkpoints

- **Docs**: Headless: llms.txt, llms-full.txt and an OpenAPI file (8 operations) at fillout.com/help; the MCP server is documented only on developers.zite.com, not in the Fillout help center.
- **Sign up**: In a browser: Email + password + name at build.fillout.com/fillout/signup (now app.zite.com). Invisible reCAPTCHA let our agent's browser through. No signup API.
- **Verify**: In a browser: Mail arrived in under a minute; the link opens a page where you must click Verify email (a plain GET does not verify).
- **Key**: In a browser: Settings > Developer > Enable API, then Copy (the key is masked). MCP: OAuth with dynamic client registration and PKCE worked headless except for one Authorize click on the consent page.
- **First call**: Headless: GET https://api.fillout.com/v1/api/forms -> 200.
- **First action**: In a browser: Forms can only be created in the web builder. The first headless write was POST /forms/{id}/submissions.
- **Pay**: In a browser: No 402/x402/MPP/L402, well-known payment files or payment text in the docs. Upgrading goes through the app.zite.com/billing/plan-builder page with an embedded Stripe Payment Element (card). The Zite Build API returns a plain 402 when its 14-day window ends. We did not pay or enter a card, and did not check the registries (web search was down).
- **Cancel**: Not needed: Nothing to cancel: our agent used the free plan.
- **Delete**: In a browser: Settings > General > Delete organization (type a confirmation phrase). Removed the forms, database and submissions in one step. Afterwards the API key and MCP token were rejected. No API for this.

## Does Fillout have an MCP server, and can an agent connect to it?

Yes. Fillout has an official MCP server.

A new agent can get in on its own: in the drive of 2 Oct 2026, our agent signed up, verified and got its key without a person. Through the MCP server, 0 of our agent's 1 attempt worked.

## How does an AI agent get a Fillout API key?

In the drive of 2 Oct 2026, our agent got its Fillout API key in a browser, without a person. Settings > Developer > Enable API, then Copy (the key is masked). MCP: OAuth with dynamic client registration and PKCE worked headless except for one Authorize click on the consent page.

## Paying the agent way

Reaches the checkout: stopped at the card form.

Ways to pay it offers an agent: Stripe card form (card checkout).
It has a free plan.

What would let agents pay on their own:
- Accept x402 or MPP on your API: Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card.
- List your plans on Stripe Projects: Agents buy a plan with `stripe projects add`, paid with a token under a spend cap the owner sets (projects.dev).
From the drive of 2 Oct 2026.

## What an agent can do

- List forms and read form metadata (questions, calculations) over the REST API
- Create submissions in bulk (up to 10 per call) over the REST API
- List, search, sort and page through submissions, and get edit links
- Delete a submission over the REST API
- Subscribe a webhook to a form's submissions over the REST API
- Query form responses stored in the linked workspace database with SQL through the Zite MCP
- Build and edit a form (fields, conditional logic, calculations) by prompting Fillout's in-app Form Agent in a browser
- Publish a form, add a webhook workflow, duplicate a form and download a CSV in the web app

## What it cannot do

- Create or edit a form headless: The REST API and MCP have no form create/update tools; building is only possible in the web builder.
- Send an email from a workflow: The Send email action needs a connected Gmail/Outlook/SMTP account or a manually reviewed account verification, even for self-email.
- Collect payments or book meetings: Needs a Stripe account or a Google/Outlook calendar, which our agent does not have.
- Sign up, get an API key or delete the account headless: These steps exist only in the web UI.
- Rely on API-created submissions behaving like real ones: They get no calculation values, do not fire webhooks and are not written to the linked database.

## Tips for the owner

1. Add form create/update endpoints and MCP tools
2. Expose the Form Agent as an MCP tool
3. Make API submissions behave like real ones
4. Document the MCP server in the Fillout help
5. Let agents mint API keys via OAuth
6. Add a list-webhooks endpoint and 404s
7. Add workflow and export endpoints

Is this your product? Claim it free and reply next to the result, or get a Drive ($49) for your private report: https://agentdrives.com/pricing?via=md#drive. Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).

## Also in Forms

- [Formbricks](https://agentdrives.com/tools/formbricks.md?via=md): L4 · Runs on its own · [Fillout vs Formbricks](https://agentdrives.com/compare/fillout-vs-formbricks?via=md)
- [Tally](https://agentdrives.com/tools/tally.md?via=md): L4 · Runs on its own · [Fillout vs Tally](https://agentdrives.com/compare/fillout-vs-tally?via=md)
- [Formspree](https://agentdrives.com/tools/formspree.md?via=md): L1 · Needs a person · [Fillout vs Formspree](https://agentdrives.com/compare/fillout-vs-formspree?via=md)
- [Jotform](https://agentdrives.com/tools/jotform.md?via=md): L1 · Needs a person · [Fillout vs Jotform](https://agentdrives.com/compare/fillout-vs-jotform?via=md)
- [Typeform](https://agentdrives.com/tools/typeform.md?via=md): L1 · Needs a person · [Fillout vs Typeform](https://agentdrives.com/compare/fillout-vs-typeform?via=md)

## Tips for agent builders

- Use https://api.fillout.com/v1/api with Authorization: Bearer <key>; the EU server is eu-api.fillout.com. The limit is 5 requests/second.
- Read question ids from GET /forms/{id} before POSTing submissions; unknown ids give a clear 400.
- API-created submissions do not run calculations, webhooks or database sync; use the public form link if you need those.
- Form responses are also rows in the linked Zite database; the Zite MCP (mcp.zite.com/mcp, OAuth DCR) can run SQL over them.
- There is no headless way to build forms. In a browser, the Form Agent panel adds fields, logic and calculations from one prompt.
- The app now lives on app.zite.com; build.fillout.com redirects there. Use /fillout/signup to get the Fillout-branded flow.