Brevo vs Kit for AI agents

As of 6 Oct 2026, Brevo gets an AI agent further: L2 · Gets in against L1 · Needs a person.

BrevoL2Gets in

Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
Access: Sign-up in a browser.
Use: 38% of the work.
Pay: Payment not reached.
Leave: Nothing to cancel: Can't delete its account.

Got in; payment not reached. Next: do half of the core work (now 38%)

Gets in on its own: L2 · Gets in, signing up in a browser past an invisible reCAPTCHA. Email confirmation worked headless, then separate browser consents won an MCP token and a REST token through OAuth, reaching contacts, deals, templates, webhooks and eCommerce data. Through MCP it created a contact and read it back. It never reached sending, which needs manual activation and a confirmed sender domain. An organization-address step in the web app also blocks the key page and account deletion, which stayed out of reach.

Gets furtherDriven 3 Oct 2026 · The drive and its evidence

KitL1Needs 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 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

The two summaries: written and checked by our agents from each product's drive. How we write.

Where each one stops.

BrevoGot in; payment not reached

KitStopped at sign up: needs a human

Brevo and Kit, checkpoint by checkpoint
Checkpoint	Brevo	Kit
Docs	Headless	Headless
Sign up	In a browser	Needs a human
Verify	Headless	Not reached
Key	In a browser	Not reached
First call	Headless	Not reached
First action	Headless	Not reached
Pay	Not reached	Not reached
Cancel	Not needed	Not reached
Delete	Blocked	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

Checkpoints by how our agent passed them, and what each product offers an agent
	Brevo	Kit
Headless (checkpoints)	4	1
In a browser (checkpoints)	2	0
Needs a human (checkpoints)	0	1
Blocked (checkpoints)	1	0
Not tested (checkpoints)	1	7
Work done	38% of the core	Not measured
API	Yes	Yes
OpenAPI	Yes	Yes
MCP server	Yes (official)	Yes (official)
CLI	Yes	No
SDK	Yes	No
llms.txt	Yes	Yes

Bot checks, and where a person was needed.

Walls our agent met
	Brevo	Kit
Bot check	Google reCAPTCHA (invisible) let it through at sign up	Cloudflare managed challenge (Turnstile 'Verify you are human') stopped it at sign up, with a visible challenge
Wall type	No bot-check wall	A check of our network and browser
First wall	Got in; payment not reached	Cloudflare challenge on the sign-up page
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.

Brevo and Kit: level and part scores, 0 to 100
	Brevo	Kit
Level	L2 · Gets in	L1 · Needs a person
Holds up	78 of 100, fair	Not measured
Docs match	89 of 100, fair	Not measured
Agent-ready setup	100 of 100, good	90 of 100, good
Standards	MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) · MCP client registration (behind) · OpenAPI 3.1.0 (1 version behind)	MCP client registration (behind) · OpenAPI 3.0.3 (2 versions behind)
Security	Reported privately to the owner	No review in this drive

Pay, cancel and delete.

Paying, cancelling and deleting the account
	Brevo	Kit
Pay	Payment not reached	Payment not reached
Free plan or trial	Free plan	Free plan
Cancel	Not needed	Not reached
Delete the account	Blocked	Not reached

How each one takes payment

Brevo: Payment not reached.
Kit: Payment not reached.

Brevo vs Kit: the short answers.

Which can an AI agent use, Brevo or Kit?

Brevo gets an AI agent further: L2 · Gets in against L1 · Needs a person. With Brevo our agent got in (payment not reached); with Kit it was stopped at sign up (needs a human). Driven 3 Oct 2026 (Brevo) and 6 Oct 2026 (Kit).

Can an AI agent sign up for Brevo and Kit on its own?

Brevo: yes, in a browser. Kit: no, needs a human.

Do Brevo and Kit have an MCP server?

Brevo: yes (official). Kit: yes (official).

Can an AI agent delete its Brevo or Kit account?

Brevo: blocked. Kit: not reached.