Built for AI agents

The form backend built for AI agents.

When Claude, Cursor, v0, Lovable, or Bolt builds a website, it needs a working form endpoint at generation time — not after a human signs up. FormsList provisions one in a single API call: no signup, no OAuth dance, no human in the loop. The generated site ships with a form that already works.

By Vaibhav Jain · Last updated August 5, 2026

One call, live endpoint

One POST to the instant provisioning endpoint returns a live form endpoint, ready to receive submissions immediately:

curl -X POST https://formslist.com/api/v1/instant \
  -H 'Content-Type: application/json' \
  -d '{"email":"owner@example.com","form_name":"Contact"}'

The response has everything an agent needs to wire the form into the page it is generating:

{
  "endpoint": "https://formslist.com/f/abc123",
  "html_snippet": "...",
  "claim_url": "...",
  "expires_at": "..."
}

The form works immediately — drop the html_snippet into the generated page and submissions start flowing. The site owner gets an email to claim the dashboard; unclaimed forms expire in 7 days.

Self-documenting endpoints

Agents shouldn't have to guess how an endpoint works. A GET request to any form endpoint (GET /f/<hash>) returns JSON usage docs for that exact form: accepted content types, expected fields, and example requests.

When something goes wrong, errors come back as {error, fix, docs_url} — a machine-readable description of what failed, the concrete fix, and a link to the relevant docs — so agents self-correct without a human reading a stack trace. The full form submission API works the same way for reading submissions and managing forms.

MCP server

FormsList ships an MCP server, so agent runtimes that speak the Model Context Protocol get typed tools instead of raw HTTP. Add it to Claude Code:

claude mcp add formslist -- node /path/to/formflow/mcp/dist/index.js

Or configure Claude Desktop:

{
  "mcpServers": {
    "formslist": {
      "command": "node",
      "args": ["/path/to/formflow/mcp/dist/index.js"],
      "env": { "FORMSLIST_API_KEY": "ff_sk_..." }
    }
  }
}

FORMSLIST_API_KEY is optional — without it the server can still provision instant forms; with it the full account is available. Seven tools are exposed:

instant_provision

Create a live form endpoint with no account — the one-call flow above

create_form

Create a form on an authenticated account

list_forms

List all forms on the account

get_form

Get details and settings for one form

get_submissions

Read submissions for a form (paginated)

configure_autoresponse

Set up the auto-reply email sent to submitters

get_embed_snippet

Get ready-to-paste HTML for a form

Made to be found by AI

An AI-native backend is only useful if models can discover and understand it at generation time. FormsList publishes machine-readable surface area for exactly that:

/llms.txt

A concise, LLM-oriented index of what FormsList is and how to use it

/llms-full.txt

The complete docs in one plain-text file, ready for a context window

/api/v1/openapi.json

A full OpenAPI 3 spec of the REST v1 API for codegen and tool use

/docs

Human-readable documentation, structured so agents can parse it too

Spam protection built in

Forms provisioned by agents get the same protection as every FormsList form: a honeypot field, heuristic spam scoring, and duplicate detection run on every submission automatically. There is nothing to configure and nothing for the agent to wire up — a form dropped into a generated static site is production-safe from the first submission.

Frequently Asked Questions

Is instant provisioning free?

Yes. Instant provisioning creates a form on the free plan, which includes 5 forms and 500 submissions per month. No credit card, no signup, no OAuth — one API call and the endpoint is live.

What happens if nobody claims a form?

Unclaimed forms are deleted after 7 days, along with any submissions they received. The site owner gets a claim email at provisioning time; claiming attaches the form to a full dashboard account and removes the expiry.

Can my agent read submissions too?

Yes. The REST v1 API exposes submissions via GET /api/v1/forms/:id/submissions using an ff_sk_ API key, and the MCP server exposes the same data through the get_submissions tool. Agents can build full read-write workflows, not just fire-and-forget forms.

How do I get an API key?

Claim the account from the email sent at provisioning time (or sign up directly), then generate a key at /account/api-keys. Keys are prefixed ff_sk_ and are sent as a bearer token on the management API.

Does this work from the browser?

Yes. CORS is enabled on the submission and provisioning endpoints, so browser-based agents and client-side code can call them directly — no proxy or server-side relay required.

Point your agent at FormsList

Read the docs or see how FormsList became AI-native in this announcement.

Read the Docs