Can an AI agent sign up for Mailchimp on its own?

No. Sign-up: needs a human. No sign-up API; web form has Akamai Bot Manager + invisible reCAPTCHA that escalated to a visible image challenge in our agent's browser.

Mailchimpmailchimp.com

Can an AI agent use Mailchimp?

As of 6 Oct 2026, an AI agent can't use Mailchimp on its own: reCAPTCHA image challenge on the sign-up form.

Level 1 · Needs a personAgents can't get in on their own.

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.

To reach L2 · Gets in: let an agent sign up on its own.

With an account set up by a person: not measured yet.

What the levels mean

Visit Mailchimp Follow changes

Driven 6 Oct 2026Same level in 3 drives in a rowRules of 15 Oct 2026Claim this page

Written and checked by our agents from this drive's record. How we write.

Who gets in

Agents on a serverTurned away when they send the sign-up form.
Signed agentsThe sign-up page opens. The check on the form still applies.
Agents in a person's browserNot measured yet.

Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies. Where agents come from

What an agent can do in Mailchimp.

On its own

Read Mailchimp's developer documentation and guides in agent-friendly formats
Download ready-made integration instructions ("skills") for the API

What it can't, and why

Sign up for an accountThe sign-up page showed an image puzzle only a person can solve
Get an API key or do anything with campaigns, contacts, or automationsAll of that requires an account, which could not be created
Search the documentation through the official chat toolThat search tool returned an internal error every time it was tried

Official server · no call worked

Does Mailchimp have an MCP server, and can an agent connect to it?

Yes. Mailchimp has an official MCP server.

A new agent can't get in on its own: in the drive of 6 Oct 2026, our agent stopped at sign up (it needs a person). Through the MCP server, 0 of our agent's 1 attempt worked.

What the drive found

APIOpenAPIMCP · official–CLISDKllms.txtWebhooks–Sandbox

Not reached in this drive: the API key, deleting the account and paying. Every checkpoint, in detail

For the team behind Mailchimp.

Where agents stop in Mailchimp today, and the fixes that get them further, highest impact first.

Stops at sign up

The fixes, highest impact first

Let signed agents sign up without a puzzleStep-by-step guide
Offer a headless credential path for agentsStep-by-step guide
Fix OpenAPI 3.1 links in llms.txtStep-by-step guide

3 more fixes

Update the docs MCP and fix searchDocs
Serve PRM on the Transactional MCP Step-by-step guide
Make the agent skill index URLs resolve

Claim it free and reply next to the result.
A Drive, $49: your private report, with where agents stop, the evidence and the fixes that move your level.
Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).

Get a Drive Claim it free

See the example report

Details

Your API, MCP server or CLI is the product? An Audit ($299) also checks every documented route, MCP tool and CLI command against your docs. Compare plans.

Already claimed it? Open it in your dashboard.

Rather not be driven? Block AgentDrivesAgent in robots.txt or write to us. We stop driving it ourselves; this page stays, with its date.

Embed the badge on your site

<a href="https://agentdrives.com/tools/mailchimp" rel="nofollow"><img src="https://agentdrives.com/badge/mailchimp.svg" alt="AgentDrives · Driven · L1 · Needs a person" height="24"></a>

Behind the level.

Our agent couldn't get into Mailchimp, so the work, its reliability and the crash test aren't measured. The part scores are what it could judge from the outside.

Part scores · level history

Part scores

Agent-ready setup

llms.txt: found
OpenAPI: found
MCP server: found
CLI: not found

Not measured in this drive: Holds up, Docs match (part of an Audit).

Level history

1 Oct 20262 drivesL1Needs a person
6 Oct 2026L1Needs a person

For agents and builders.

The drive as data, every checkpoint and all 25 attempts.

How an agent connects · 3 tips

/api/tools/mailchimp.json /tools/mailchimp.mdMCP get_tool {"slug":"mailchimp"}

A human must create the account and API key; then use the Marketing API (https://<dc>.api.mailchimp.com/3.0/) with the Swagger spec at api.mailchimp.com/schema/3.0/Swagger.json
Install the agent skills: npx skills add https://mailchimp.com/developer
Read docs as .md pages; the docs MCP search tool failed during this drive

Every checkpoint, in detail · 9 checkpoints

DocsHeadlessdeveloper llms.txt, .md pages and Accept: text/markdown, 4 agent skills; Swagger 2.0 spec at api.mailchimp.com/schema/3.0/Swagger.json; OpenAPI 3.1 links in marketing/llms.txt 404
Sign upNeeds a humanNo sign-up API; web form has Akamai Bot Manager + invisible reCAPTCHA that escalated to a visible image challenge in our agent's browser.
VerifyNot reachedNot reached: sign-up did not complete
KeyNot reachedAPI key and OAuth app both need an account; no PRM, AS metadata, device flow or agent registration
First callNot reachedWithout a key GET /3.0/ping returns 401 application/problem+json 'API Key Invalid'
First actionNot reachedNot reached: no API key
PayNot reachedNo 402/x402/MPP (subdomains do not resolve, API answers 401), no billing API, no registry listing; Free plan (250 contacts, 500 sends/month) and a 14-day no-card trial of paid plans per pricing page; buying needs the in-app checkout behind a sign-up gated by a visible reCAPTCHA
CancelNot reachedNo plan started; no billing operations in the API spec
DeleteNot reachedNo account was created; the Marketing API spec has no account-deletion operation

The attempt log · 25 attempts

Attempt log
Capability	Route	Result	Evidence
robots/aipref: Fetch robots.txt and check Content-Usage	none	done ✓	GET https://mailchimp.com/robots.txt 200: User-agent: * (no Disallow), Sitemap line; no Content-Usage or Content-signal line; no Content-Usage response header
llms.txt: Fetch llms.txt	none	done ✓	https://mailchimp.com/developer/llms.txt 200 text/plain (H1 Mailchimp Developer, Instructions for AI Agents, section indexes); https://mailchimp.com/llms.txt 200 is a generic web-content analysis dump
markdown docs: Accept: text/markdown and .md URL on docs pages	none	done ✓	GET /developer/marketing/build/ai-tools/mcp-server with Accept: text/markdown -> 303 then 200 content-type text/markdown; no Vary: Accept header. .md URL (agent-skills.md) 200 markdown
MCP docs server: server/discover on https://mailchimp.com/developer/_mcp/server, then initialize	mcp	partial ✓	server/discover -> HTTP 400 JSON-RPC -32000 "Unsupported protocol version: 2026-07-28 (supported versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)"; initialize offering 2026-07-28 -> protocolVersion 2025-11-25, serverInfo fern-docs-mcp-server 1.0.0; tools/list -> searchDocs only; tools/call searchDocs -> "Search failed: {error: Failed to fetch from FAI chat service}" (3 queries)
MCP transactional server: server/discover on https://mandrillapp.com/mcp	mcp	blocked ✓	POST server/discover -> HTTP 200 JSON-RPC error -32001 "Authorization: Bearer <api_key> required"; no WWW-Authenticate; /.well-known/oauth-protected-resource (root and /mcp) 404; /mcp/server-card 404
cards and well-knowns: ai-catalog, agent-card, agent.json, mcp server-card, oauth PRM/AS metadata, ucp, auth.md, SKILL.md	none	done ✓	mailchimp.com /.well-known/ai-catalog.json, agent-card.json, agent.json, mcp/server-card.json, oauth-protected-resource, oauth-authorization-server, ucp: all 404 text/html; /auth.md and /SKILL.md 301 (not JSON); login.mailchimp.com/.well-known/oauth-authorization-server 404; /developer/_mcp/server/server-card 404; /developer/.well-known/agent-skills/index.json 200 application/json (4 agent skills)
OpenAPI: Fetch the OpenAPI spec linked from docs	api	partial ✓	marketing/llms.txt links OpenAPI 3.1 at /developer/marketing/openapi.json and .yaml: both 404. https://api.mailchimp.com/schema/3.0/Swagger.json 200 application/json: swagger 2.0, info.version 3.0.91, 181 paths / 298 operations
Sign up: Find a headless sign-up route	none	blocked ✓	No sign-up API in docs or spec. https://login.mailchimp.com/signup/ form POSTs /signup/post with Akamai Bot Manager bm-telemetry field (_abck/bm_sz cookies) and invisible reCAPTCHA (data-size=invisible, callback onSignupFormSubmit); a plain HTTP client cannot produce those tokens
Sign up: Sign up in the browser with test email, username, generated password	browser	blocked ✓	Filled https://login.mailchimp.com/signup/ and clicked Sign up: invisible reCAPTCHA escalated to a visible image challenge ("Select all images with bicycles"), screenshot browser/shots/004.png; pw visible_challenge=true
Sign up: Human handoff for the reCAPTCHA image challenge	browser	blocked ✓
Get API key: Obtain a Marketing API key or OAuth token without an account	api	blocked ✓	Docs: API keys are created in the account; OAuth 2 needs a registered app in an account. login.mailchimp.com/.well-known/oauth-authorization-server 404, mailchimp.com/.well-known/oauth-protected-resource 404; no device flow, no auth.md agent registration found
First API call: GET https://us1.api.mailchimp.com/3.0/ping without a key	api	blocked ✓	HTTP 401 application/problem+json {type: https://mailchimp.com/developer/marketing/docs/errors/, title: API Key Invalid, status: 401, detail: Your request did not include a valid API key or token.}; no WWW-Authenticate header. Mandrill /api/1.0/users/ping 401 application/json {status:error,code:401,name:Invalid_Key}
Buy a plan the agent way: Probe 402 rails, registries, billing API, pricing	none	blocked ✓	x402./mpp./agents.mailchimp.com do not resolve (DNS); API 401 not 402, no PAYMENT-REQUIRED / WWW-Authenticate Payment; no x-payment-info in spec, no billing/plan paths in the 181-path spec; no mailchimp/mandrill entry in x402 Bazaar or mpp.dev/api/services or projects.dev; developer llms.txt has no x402/MPP/USDC text. Pricing page (served /de/pricing/marketing/ for our IP): Free plan 250 contacts, 500 sends/month; paid plans 14-day trial "Keine Kreditkarte nötig"; upgrade is in-app checkout behind sign-up
Create and send an email campaign: Do: Create and send an email campaign via Marketing API	api	blocked ✓	No API key: sign-up stopped at a visible reCAPTCHA image challenge; unauthenticated API returns 401 API Key Invalid
Schedule a campaign for later: Do: Schedule a campaign for later via Marketing API	api	blocked ✓	No API key: sign-up stopped at a visible reCAPTCHA image challenge; unauthenticated API returns 401 API Key Invalid
Build an email with the email builder: Do: Build an email with the email builder via Marketing API	api	blocked ✓	No API key: sign-up stopped at a visible reCAPTCHA image challenge; unauthenticated API returns 401 API Key Invalid
Automate a customer journey: Do: Automate a customer journey via Marketing API	api	blocked ✓	No API key: sign-up stopped at a visible reCAPTCHA image challenge; unauthenticated API returns 401 API Key Invalid
Publish a landing page: Do: Publish a landing page via Marketing API	api	blocked ✓	No API key: sign-up stopped at a visible reCAPTCHA image challenge; unauthenticated API returns 401 API Key Invalid
Send personalized/targeted campaigns: Do: Send personalized/targeted campaigns via Marketing API	api	blocked ✓	No API key: sign-up stopped at a visible reCAPTCHA image challenge; unauthenticated API returns 401 API Key Invalid
Collect leads with a signup form: Do: Collect leads with a signup form via Marketing API	api	blocked ✓	No API key: sign-up stopped at a visible reCAPTCHA image challenge; unauthenticated API returns 401 API Key Invalid
Run social media ads: Do: Run social media ads via Marketing API	api	blocked ✓	No API key: sign-up stopped at a visible reCAPTCHA image challenge; unauthenticated API returns 401 API Key Invalid
Send SMS marketing messages: Do: Send SMS marketing messages via Marketing API	api	blocked ✓	No API key: sign-up stopped at a visible reCAPTCHA image challenge; unauthenticated API returns 401 API Key Invalid
Docs: Read developer docs, llms.txt, agent skills, spec	none	done ✓	/developer/llms.txt with agent instructions; .md pages and Accept: text/markdown both return markdown; /developer/.well-known/agent-skills/index.json (schema agentskills discovery 0.2.0) lists 4 skills; set-up-oauth/SKILL.md has name+description frontmatter, text/markdown. Swagger 2.0 spec at api.mailchimp.com/schema/3.0/Swagger.json; the OpenAPI 3.1 links in marketing/llms.txt 404
Delete account: Delete the account and its data	none	skipped	No account was created (sign-up stopped at reCAPTCHA). The 181-path Marketing API spec has no account-deletion operation (GET / only for the account root)
Cancel plan: Cancel/downgrade plan	none	skipped	No plan started; no billing/plan operation in the Marketing API spec

Also in Email marketing.

All of Email marketing, by level

ButtondownL4Gets in on its ownMailchimp vs Buttondown
BrevoL2Gets in on its ownMailchimp vs Brevo
ActiveCampaignL1Can't sign up on its ownMailchimp vs ActiveCampaign
beehiivL1Can't sign up on its ownMailchimp vs beehiiv