Kit vs Mailchimp for AI agents
As of 6 Oct 2026, both reach L1 · Needs a person, and with each our agent was stopped at sign up (needs a human).
- 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 Kit for an agent today. Developer docs are agent-friendly: llms.txt, Markdown pages, OpenAPI, a read-only docs MCP our agent reached on its own. Sign-up is where it stopped: app.kit.com/users/signup showed a Cloudflare 'Verify you are human' challenge that never cleared, so no account, no key, and no call to the API past an unauthenticated 401. A person has to sign up, verify, and make the key in the web app before an agent can do any core email work through the API or the paid Kit MCP. No plan was started, so paying and cancelling 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: 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 get in: L1 · Needs a person. Sign-up is where our agent stopped: Google reCAPTCHA started invisible, then showed a visible image challenge, so no account, key or OAuth app ever existed. Its developer docs are agent-friendly on their own: an llms.txt, Markdown pages, agent skills and a docs-search MCP server, though that MCP's tool failed in our drive. Without a key, the ping endpoint answered with an invalid-key error, so no work was done. Buying needs that same gated sign-up form; cancelling and deleting were never reached, since no account or plan existed to act on.
Driven 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.
KitStopped at sign up: needs a human
MailchimpStopped at sign up: needs a human
| Checkpoint | Kit | Mailchimp |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | 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
| Kit | Mailchimp | |
|---|---|---|
| Headless (checkpoints) | 1 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 1 | 1 |
| Blocked (checkpoints) | 0 | 0 |
| Not tested (checkpoints) | 7 | 7 |
| Work done | Not measured | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | No |
| SDK | No | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Kit | Mailchimp | |
|---|---|---|
| Bot check | Cloudflare managed challenge (Turnstile 'Verify you are human') stopped it at sign up, with a visible challenge | Google reCAPTCHA (invisible, escalated to v2 image challenge) stopped it at sign up, with a visible challenge |
| Wall type | A check of our network and browser | A check of our network and browser |
| First wall | Cloudflare challenge on the sign-up page | reCAPTCHA image challenge 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. Where we drive from.
Level and part scores.
| Kit | Mailchimp | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 90 of 100, good | 100 of 100, good |
| Standards | MCP client registration (behind) · OpenAPI 3.0.3 (2 versions behind) | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) · OpenAPI 2.0 (3 versions behind) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Kit | Mailchimp | |
|---|---|---|
| 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
- Kit: Payment not reached.
- Mailchimp: Payment not reached.
Kit vs Mailchimp: the short answers.
Which can an AI agent use, Kit or Mailchimp?
Both reach L1 · Needs a person, and with each our agent was stopped at sign up (needs a human). Both driven 6 Oct 2026.
Can an AI agent sign up for Kit and Mailchimp on its own?
Kit: no, needs a human. Mailchimp: no, needs a human.
Do Kit and Mailchimp have an MCP server?
Kit: yes (official). Mailchimp: yes (official).
Can an AI agent delete its Kit or Mailchimp account?
Kit: not reached. Mailchimp: 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.