Framer vs Webflow for AI agents
As of 11 Oct 2026, Webflow gets an AI agent further: L2 · Gets in against L1 · Needs a person.
- Find: Some docs for agents: llms.txt and an MCP server.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: blocked. Next: let an agent sign up on its own
A person has to get in first: L1 · Needs a person is where Framer sits. Its docs read well on their own, with llms.txt and markdown on every page, plus Server API, External Agents and plugin guides. Our agent stopped at the first step: the email signup form sends a Castle risk check with no visible challenge, and api.framer.com answers "Access denied by policy, Verification failed," so no verification email went out. With no account, the Server API key, the CLI's project command and the MCP server's OAuth login stayed out of reach, and mcp.framer.com returned 401 with no token to send. Checkout and account deletion sit behind that same locked door, untested.
Driven 11 Oct 2026 · The drive and its evidence- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Sign-up in a browser.
- Use: 0% of the work.
- Pay: Reaches the checkout: Stopped at the card form.
- Leave: Nothing to cancel: Can't delete its account.
Got in; first wall at first action (blocked). Next: do half of the core work (now 0%)
Gets in on its own, but not yet the work: L2 · Gets in. Sign-up passed an invisible PerimeterX sensor, and verification and MCP OAuth consent both completed in the browser. It stopped at the first real action: creating a site, which nearly every tool needs, is dashboard-only on the free plan, and the Create Site API is Enterprise-only. It read the docs through a Markdown llms.txt tree and an OpenAPI spec, and listed the MCP server's tools, but could do no site work through API, MCP or CLI. Upgrading opened an in-app checkout with an hCaptcha script loaded, left unpaid; deletion was requested and confirmed by email, but never checked through to completion.
Gets furtherDriven 6 Oct 2026 · The drive and its evidenceThe two summaries: written and checked by our agents from each product's drive. How we write.
Where each one stops.
FramerStopped at sign up: blocked
WebflowGot in; first wall at first action (blocked)
| Checkpoint | Framer | Webflow |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Blocked | In a browser |
| Verify | Not reached | In a browser |
| Key | Not reached | In a browser |
| First call | Not reached | Headless |
| First action | Not reached | Blocked |
| Pay | Not reached | In a browser |
| Cancel | Not reached | Not needed |
| Delete | Not reached | Blocked |
Headless or in a browser.
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| Framer | Webflow | |
|---|---|---|
| Headless (checkpoints) | 1 | 2 |
| In a browser (checkpoints) | 0 | 4 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 1 | 2 |
| Not tested (checkpoints) | 7 | 0 |
| Work done | Not measured | 0% of the core |
| API | Yes | Yes |
| OpenAPI | No | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | Yes |
| SDK | Yes | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Framer | Webflow | |
|---|---|---|
| Bot check | Castle (risk SDK castleSDKV3) stopped it at sign up, without a visible challenge | HUMAN (PerimeterX) invisible sensor let it through at sign up |
| Wall type | A check of our network and browser | No bot-check wall |
| First wall | Invisible risk check refuses sign-up | Got in; first wall at first action (blocked) |
| A person helped | No | No |
A check of our network and browser: It judged where our agent connects from and its browser, not a person. An agent that works on its own from a data center doesn't get through unless the owner lets signed agents in. How agents in a person's own browser fare isn't measured yet. Where we drive from.
Level and part scores.
| Framer | Webflow | |
|---|---|---|
| Level | L1 · Needs a person | L2 · Gets in |
| Agent-ready setup | 75 of 100, fair | 100 of 100, good |
| Standards | MCP client registration (behind) | MCP spec of 28 Jul 2026 (current) · MCP discovery (current) · MCP client registration (behind) · OpenAPI 3.1.0 (1 version behind) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Framer | Webflow | |
|---|---|---|
| Pay | Payment not reached | Reaches the checkout |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not reached | Not needed |
| Delete the account | Not reached | Blocked |
How each one takes payment
- Framer: Payment not reached.
- Webflow: Reaches the checkout: stopped at the card form.
Framer vs Webflow: the short answers.
Which can an AI agent use, Framer or Webflow?
Webflow gets an AI agent further: L2 · Gets in against L1 · Needs a person. With Framer our agent was stopped at sign up (blocked); with Webflow it got in and met its first wall at first action (blocked). Driven 11 Oct 2026 (Framer) and 6 Oct 2026 (Webflow).
Can an AI agent sign up for Framer and Webflow on its own?
Framer: no, blocked. Webflow: yes, in a browser.
Do Framer and Webflow have an MCP server?
Framer: yes (official). Webflow: yes (official).
Can an AI agent delete its Framer or Webflow account?
Framer: not reached. Webflow: blocked.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.