Lanes Forms vs Formspree

Formspree and Lanes Forms solve the same core problem: a form backend you do not have to build. The difference is how a form comes to exist. Formspree is dashboard-first and needs an account. Lanes Forms can be created anonymously, by you or your agent, and claimed later.

This page is about that difference in creation paths, and what each one makes easy.

At a glance

Dimension	Lanes Forms	Formspree
Create a form	One POST or an MCP tool call	Set up in the dashboard
Account to start	Not required; claim by email later	Required up front
Agent friendly	Yes, provision over MCP mid-task	Manual setup
Spam defense	Honeypot, rate limits, disposable-email rejection	Spam filtering
Destinations	Email and Lanes storage with CSV export today; webhooks on the roadmap	Email and integrations
Origin rules	Yes	Yes
Unclaimed forms	Hold up to 25 submissions, claim within 7 days	Not applicable; account comes first
Validation	Server-side, a 422 lists the missing fields	In the dashboard
Docs	Lanes Forms docs	formspree.io

Where Lanes Forms fits

Lanes Forms is built for speed and for agents. A coding agent can provision a live endpoint mid-build over MCP, or you can with one curl, no signup. The owner claims it by email whenever they are ready. It is the fastest path from "I need a form" to a working endpoint.

The mechanics are simple. The create call is one POST /v1/forms where only a schema is required, and the response returns a live endpoint_url plus a claim link; see provisioning. While unclaimed, the form holds up to 25 submissions, forwards nothing, and expires after 7 days if nobody claims it, so an endpoint born mid-task waits safely for its owner. Claiming releases every held submission into the dashboard and turns email forwarding on; see claiming. The agent path runs over a hosted MCP server whose create_form and submit_form tools work with no key at all, covered in agents and MCP.

Where Formspree fits

Formspree is a mature, dashboard-driven form backend with a long list of integrations. If you want to manage everything from an established dashboard and that is where your team lives, Formspree is a solid choice. The difference is where management starts: Formspree in its dashboard from day one, Lanes in an API-first flow with a dashboard after the claim.

How Lanes does it

Provisioning is one POST. POST /v1/forms with a schema is the whole setup. The response includes the endpoint_url and either a claim link or the address a claim email went to, and an optional Idempotency-Key header makes retries safe, so a retried call replays the same form instead of duplicating it. See provisioning.
Claiming transfers ownership safely. The claim link is single-use and possession is the authorization, so an agent can provision on your behalf and you still end up as the owner. A preview endpoint renders the claim page without consuming the token, which means an email scanner cannot burn it. See claiming.
Security splits browsers from servers. Browser posts are checked against an allowed_origins hostname allowlist, with per-form CORS that echoes the exact origin and never a wildcard. Server-only forms can require an lfk_ key by setting submission_auth to api_key. See securing your endpoints.

Choose Lanes Forms if

You want to create a form with no signup, or have an agent do it over MCP.
You want to claim and manage it later, not before you start collecting.
You want origin allowlisting for browsers and an optional API-key mode for servers on the same form.
You want a stable error envelope and an interactive OpenAPI contract an agent can drive; see the API reference.

Choose Formspree if

You prefer a dashboard-first setup and its integration catalog.
Forms are set up by people, not agents, and the account already exists.

The overlap is real: both are form backends. The split is the starting point, an account and a dashboard on one side, an anonymous POST and a claim link on the other.