# Formbricks: L4 · Runs on its own

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

Source: https://agentdrives.com/tools/formbricks?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

Gets in on its own, creates its key and runs the whole survey lifecycle: L4 · Runs on its own. Our agent passed every checkpoint: email sign-up with no CAPTCHA, a headless verification link, an API key from Organization Settings, then calls through the REST API and the official OAuth MCP server. It created, edited, published and read back surveys and responses, with webhooks and targeting, all from the API or MCP; sign-up, the key page, tags, segments, billing and account deletion stayed in the browser. The trial needed no card; our agent returned the plan to Hobby in the billing screen, then deleted its account and org from the profile page.

_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: 100% of the work
- Pay: Reaches the checkout (Stopped at the card form)
- Leave: Leaves on its own (Cancels on its own, deletes its account)
- Ways in: Sign-up in a browser, 8 of 8 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 + docs/llms.txt; every API page available as .md with an embedded OpenAPI fragment; MCP setup docs
- **Sign up**: In a browser: No documented sign-up API. Email sign-up form at app.formbricks.com/auth/signup worked in our agent's browser; no CAPTCHA or bot check seen
- **Verify**: Headless: Verification mail arrived in seconds; the GET link worked headless (302 to /auth/login?verified=1)
- **Key**: In a browser: API keys are created only in the UI (Organization Settings > API Keys), workspace-scoped read/write/manage, shown once. MCP uses OAuth with dynamic client registration: discovery and registration headless, consent is one click in the browser
- **First call**: Headless: GET /api/v1/management/me with x-api-key -> 200
- **First action**: Headless: POST /api/v1/management/surveys created a link survey, read back by GET
- **Pay**: In a browser: No 402/x402/MPP/L402, no /.well-known/ucp, not in the x402 Bazaar or mpp.dev, no billing API. Sign-up starts a 14-day Pro trial automatically, no card needed. Upgrading is in-app ('Pay now & unlock', $89/mo) plus a Stripe customer portal at billing.formbricks.com ('Add payment method'). Graded from what we saw: a hosted flow an agent could complete alone. We had no card, so neither checkout completion nor 3DS was tested
- **Cancel**: In a browser: Billing > 'Return to Hobby plan' ended the trial at once (verified: plan Hobby). Without a card the trial would also end on its own (Oct 16). No billing API
- **Delete**: In a browser: Account > Profile > Delete account (type email + password) deletes the account and the sole-owned org; the old API key then returns 401 and login fails. No documented headless route

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

Yes. Formbricks 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, 5 of our agent's 7 attempts worked.

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

In the drive of 2 Oct 2026, our agent got its Formbricks API key in a browser, without a person. API keys are created only in the UI (Organization Settings > API Keys), workspace-scoped read/write/manage, shown once. MCP uses OAuth with dynamic client registration: discovery and registration headless, consent is one click in the browser

## Paying the agent way

Reaches the checkout: stopped at the card form.

Ways to pay it offers an agent: Stripe Checkout.
No card needed to start.

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

- Create, edit (blocks, hidden fields, recall, conditional logic), publish and delete link and app surveys through the REST API or MCP
- Share a survey as a public link and collect responses through the unauthenticated Client API
- List, read, update (mark finished) and delete responses
- Create action classes and app surveys, and read the widget's workspace state
- Identify users with attributes and read contacts and attributes back
- Create signed webhooks that fire on response events
- PIN-protect a survey, cap submissions (auto-close) and set publish/close dates
- Add a second language with translated text via MCP
- Connect through the official MCP server with standard OAuth (dynamic client registration)

## What it cannot do

- Sign up or create an API key headless: Only the web UI offers them (no CAPTCHA, though); the API key is shown once in a modal
- Tag responses, create segments, invite members or remove branding headless: No documented API; UI only (all worked in the browser)
- Email follow-ups, workflows, Unify Feedback, spam protection, teams, 2FA, SSO: Paid plans beyond the no-card trial (403 with clear messages)
- Pay or cancel through an API: No billing API or agent payment rail; Stripe-hosted portal and in-app buttons only
- Delete the account headless: Only the Profile page in the UI

## Tips for the owner

1. Let agents create API keys headlessly
2. Document the survey document schema for API
3. Fix followUps date validation on JSON input
4. Serve the v2 OpenAPI file as YAML
5. Document workspaceId on management create-response
6. Add tags and segments to the API

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

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

## Tips for agent builders

- Use the Management API v1 with header x-api-key; the key is workspace-scoped, so /api/v2/me returns 401 unless the key also has Organization Access
- Webhooks live at /api/v1/webhooks, not /api/v1/management/webhooks (that path returns a 404 HTML page)
- Management POST /responses needs workspaceId in the body even though the docs list only surveyId
- Hidden field id 'source' is reserved; error messages name the offending field, so read details
- MCP uses a different translation dialect: {'en-US': '...'} instead of {'default': '...'}; validate_survey takes {operation, data}
- Survey status 'scheduled' is not settable: set publishOn/closeOn with status draft
- The client API enforces PIN protection and submission limits (403 with clear messages)
- Workspace state is cached for 5 minutes