Make vs Zapier for AI agents
As of 6 Oct 2026, Zapier gets an AI agent further: L2 · Gets in against L1 · Needs a person.
- Find: Docs for agents: llms.txt, an OpenAPI 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
L1 · Needs a person describes Make today: our agent could not get in on its own. It stopped at signup, where a Cloudflare managed challenge on the registration page did not clear, even for a signed, docs-reading agent. OAuth client registration worked on its own, but the authorize step redirects to that same challenged login, and API and MCP calls both failed for want of a key. Make's docs are agent-friendly: llms.txt, markdown pages, a full REST API, CLI, SDK and hosted MCP server, all unreachable without a person completing signup first. Checkout, subscription cancellation and profile deletion all sit behind that same human login and were never reached.
Driven 6 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: 25% of the work.
- Pay: Card checkout.
- Leave: Leaves on its own: Nothing to cancel, deletes its account.
In on its own; 25% of the work done. Next: do half of the core work (now 25%)
Gets in on its own: L2 · Gets in. Our agent passed sign-up (no CAPTCHA, no email confirmation needed) and authorised the account, both in a browser, then worked headless through the SDK CLI and the official MCP server. It created, updated and read back records in Zapier Tables, ran a Tables action through MCP, and saved and used an MCP Skill. Zaps, the core product, have no headless route for a normal account, and in the browser the editor's Copilot left a draft Zap unfinished. Our agent never reached checkout: the trial started without a card, and account deletion needs the browser too.
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.
MakeStopped at sign up: needs a human
ZapierIn on its own; 25% of the work done
| Checkpoint | Make | Zapier |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | In a browser |
| Verify | Not reached | Not needed |
| Key | Not reached | In a browser |
| First call | Not reached | Headless |
| First action | Not reached | Headless |
| Pay | Not reached | Not tried |
| Cancel | Not reached | Not needed |
| Delete | Not reached | In a browser |
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
| Make | Zapier | |
|---|---|---|
| Headless (checkpoints) | 1 | 3 |
| In a browser (checkpoints) | 0 | 3 |
| Needs a human (checkpoints) | 1 | 0 |
| Blocked (checkpoints) | 0 | 0 |
| Not tested (checkpoints) | 7 | 1 |
| Work done | Not measured | 25% of the core |
| API | Yes | Yes |
| OpenAPI | Yes | 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.
| Make | Zapier | |
|---|---|---|
| Bot check | Cloudflare managed challenge (interstitial) stopped it at sign up, with a visible challenge | None met |
| Wall type | A check of our network and browser | No bot-check wall |
| First wall | Cloudflare challenge on sign-up and login | None |
| 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.
| Make | Zapier | |
|---|---|---|
| Level | L1 · Needs a person | L2 · Gets in |
| Agent-ready setup | 100 of 100, good | 100 of 100, good |
| Standards | MCP client registration (behind) · OpenAPI 3.0.0 (2 versions behind) | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) · MCP client registration (behind) · OpenAPI 3.1.0 (1 version behind) |
| Security | No review in this drive | Reported privately to the owner |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Make | Zapier | |
|---|---|---|
| Pay | Payment not reached | Card checkout |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not reached | Not needed |
| Delete the account | Not reached | In a browser |
How each one takes payment
- Make: Payment not reached.
- Zapier: Card checkout.
Make vs Zapier: the short answers.
Which can an AI agent use, Make or Zapier?
Zapier gets an AI agent further: L2 · Gets in against L1 · Needs a person. With Make our agent was stopped at sign up (needs a human); with Zapier it got in on its own and did 25% of the work. Both driven 6 Oct 2026.
Can an AI agent sign up for Make and Zapier on its own?
Make: no, needs a human. Zapier: yes, in a browser.
Do Make and Zapier have an MCP server?
Make: yes (official). Zapier: yes (official).
Can an AI agent delete its Make or Zapier account?
Make: not reached. Zapier: yes, in a browser.
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.