Framer vs Wix for AI agents
As of 12 Oct 2026, both reach L1 · Needs a person, and our agent got as far with each: with Framer it was stopped at sign up (blocked), with Wix it was stopped at sign up (needs a human).
- 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: 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: needs a human. Next: let an agent sign up on its own
Needs a person to set up: L1 · Needs a person. Our agent read the headless docs and reference, but the signup form showed a reCAPTCHA Enterprise checkbox before it could create an account, and our agent does not solve CAPTCHAs. Stopped there: no account, no key, no OAuth token, nothing past the docs. An unauthenticated Query Sites call returned an HTML page, not a JSON error. API keys live only in the dashboard, and MCP needs an authorization code a person must grant. No plan was started, so paying, cancelling and deleting were not reached: Wix's help center covers cancelling and closing an account from the dashboard.
Driven 12 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
WixStopped at sign up: needs a human
| Checkpoint | Framer | Wix |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Blocked | Needs a human |
| Verify | Not reached | Not reached |
| Key | Not reached | Not reached |
| First call | Not reached | Not reached |
| First action | Not reached | Not reached |
| Pay | Not reached | Not reached |
| Cancel | Not reached | Not reached |
| Delete | Not reached | Not reached |
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 | Wix | |
|---|---|---|
| Headless (checkpoints) | 1 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 0 | 1 |
| Blocked (checkpoints) | 1 | 0 |
| Not tested (checkpoints) | 7 | 7 |
| Work done | Not measured | Not measured |
| API | Yes | Yes |
| OpenAPI | No | No |
| 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 | Wix | |
|---|---|---|
| Bot check | Castle (risk SDK castleSDKV3) stopped it at sign up, without a visible challenge | reCAPTCHA Enterprise stopped it at sign up, with a visible challenge |
| Wall type | A check of our network and browser | A challenge on the form |
| First wall | Invisible risk check refuses sign-up | reCAPTCHA checkbox on the sign-up form |
| 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. A challenge on the form: It asks every visitor to prove they are human. It stops every agent on any network, and a signature doesn't help: a person does this step, or the owner opens it for agents. Where we drive from.
Level and part scores.
| Framer | Wix | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 75 of 100, fair | 75 of 100, fair |
| Standards | MCP client registration (behind) | MCP client registration (behind) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Framer | Wix | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not reached | Not reached |
| Delete the account | Not reached | Not reached |
How each one takes payment
- Framer: Payment not reached.
- Wix: Payment not reached.
Framer vs Wix: the short answers.
Which can an AI agent use, Framer or Wix?
Both reach L1 · Needs a person, and our agent got as far with each: with Framer it was stopped at sign up (blocked), with Wix it was stopped at sign up (needs a human). Driven 11 Oct 2026 (Framer) and 12 Oct 2026 (Wix).
Can an AI agent sign up for Framer and Wix on its own?
Framer: no, blocked. Wix: no, needs a human.
Do Framer and Wix have an MCP server?
Framer: yes (official). Wix: yes (official).
Can an AI agent delete its Framer or Wix account?
Framer: not reached. Wix: not reached.
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.