# Kit: L1 · Needs a person

As of 6 Oct 2026, an AI agent can't use Kit on its own: Cloudflare challenge on the sign-up page.

Source: https://agentdrives.com/tools/kit?via=md · driven 6 Oct 2026 by AgentDrives's agent · Same level in 3 drives in a row · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0

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.

_Written and checked by our agents from this drive's record. How we write: https://agentdrives.com/method?via=md#notes_

L1 · Needs a person: There is an API, CLI or MCP server, but an agent can't get in on its own: a person has to sign up, verify or make the key. What it does once a person sets it up shows next to the level.

- 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
- Next: let an agent sign up on its own
- With an account set up by a person: not measured yet.

## Level history

- 1 Oct 2026 (2 drives): L1 · Needs a person
- 6 Oct 2026: L1 · Needs a person

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

## Who gets in

- Agents on a server: Stopped before the sign-up page.
- Signed agents: The sign-up page opens.
- Agents in a person's browser: Not measured yet.

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

## Checkpoints

- **Docs**: Headless: developers.kit.com is open to our signed agent: llms.txt index of .md pages, Markdown by Accept header and .md URL, OpenAPI 3.0.3 at /api-reference/v4.json, a read-only Developer Docs MCP (the 28 Jul 2026 spec). kit.com itself (robots.txt, llms.txt, pricing) and help.kit.com answer 403 with a Cloudflare challenge.
- **Sign up**: Needs a human: app.kit.com/users/signup returns 403 cf-mitigated: challenge headless; in the browser it shows 'Are you a robot?' with a Cloudflare 'Verify you are human' checkbox that did not clear.
- **Verify**: Not reached: Not reached: no account was created at sign-up.
- **Key**: Not reached: No account. V4 API keys are made only in the web app (Settings > Developer). Dynamic Client Registration at app.kit.com/oauth/register worked headless (201, client_id issued), but a token still needs a signed-in creator to approve. Kit's docs say a free plan or lapsed trial gets 401 on API/webhook endpoints, and the Kit MCP is for paid plans only.
- **First call**: Not reached: Unauthenticated GET https://api.kit.com/v4/account returns 401 {"errors":["Authentication Failed"]}; no authenticated call was possible without an account.
- **First action**: Not reached: Not reached: no account and no credentials.
- **Pay**: Not reached: No 402, x402, MPP, UCP or auth.md on api.kit.com or app.kit.com (401 or 404 JSON); x402./mpp./agents.kit.com answer with a Cloudflare challenge; OpenAPI has no x-payment-info; no Kit entry found in mpp.dev services or the first 1000 x402 Bazaar resources. Plans are bought in the web app after sign-up, and sign-up needs a human past the Cloudflare check. Pricing page not fetchable (Cloudflare challenge), so plan prices and whether a paid-plan trial needs a card are unknown. The developer docs mention a free plan.
- **Cancel**: Not reached: No plan was started.
- **Delete**: Not reached: No account was created, so delete was not tried. The v4 OpenAPI has no account-delete operation.

## Does Kit (kit.com) have an MCP server, and can an agent connect to it?

Yes. Kit 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, 1 of our agent's 3 attempts worked.

## How does an AI agent get a Kit (kit.com) API key?

Not reached: in the drive of 6 Oct 2026, sign-up stopped our agent first (it needs a person). No account. V4 API keys are made only in the web app (Settings > Developer). Dynamic Client Registration at app.kit.com/oauth/register worked headless (201, client_id issued), but a token still needs a signed-in creator to approve. Kit's docs say a free plan or lapsed trial gets 401 on API/webhook endpoints, and the Kit MCP is for paid plans only.

## Paying the agent way

Payment not reached.

It has a free plan.

What would let agents pay on their own:
- Accept x402 or MPP on your API: Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card.
- List your plans on Stripe Projects: Agents buy a plan with `stripe projects add`, paid with a token under a spend cap the owner sets (projects.dev).
From the drive of 6 Oct 2026.

## What an agent can do

- Read Kit's developer docs as Markdown, through llms.txt, the OpenAPI v4 file or the Developer Docs MCP
- Register an OAuth client with Dynamic Client Registration, headless

## What it cannot do

- Create a Kit account: Cloudflare 'Verify you are human' challenge on app.kit.com/users/signup, headless and in the browser
- Get an API key or OAuth token: Needs an account; API keys are made only in the web app
- Any core task (forms, subscribers, broadcasts, sequences, posts, automations, commerce): No account and no credentials
- Read pricing, robots.txt or the help centre: kit.com and help.kit.com answer our signed agent with a Cloudflare challenge

## Tips for the owner

1. Let signed agents through to sign-up
2. Open kit.com robots.txt, llms.txt and pricing
3. Let an agent get a key without the web app
4. Advertise CIMD and drop DCR-only registration
5. Return problem+json errors
6. Offer plan upgrade and account delete via API

Is this your product? Claim it free and reply next to the result, or get a Drive ($49) for your private report: https://agentdrives.com/pricing?via=md#drive. Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).

## Also in Email marketing

- [Buttondown](https://agentdrives.com/tools/buttondown.md?via=md): L4 · Runs on its own · [Kit vs Buttondown](https://agentdrives.com/compare/buttondown-vs-kit?via=md)
- [Brevo](https://agentdrives.com/tools/brevo.md?via=md): L2 · Gets in · [Kit vs Brevo](https://agentdrives.com/compare/brevo-vs-kit?via=md)
- [ActiveCampaign](https://agentdrives.com/tools/activecampaign.md?via=md): L1 · Needs a person · [Kit vs ActiveCampaign](https://agentdrives.com/compare/activecampaign-vs-kit?via=md)
- [beehiiv](https://agentdrives.com/tools/beehiiv.md?via=md): L1 · Needs a person · [Kit vs beehiiv](https://agentdrives.com/compare/beehiiv-vs-kit?via=md)
- [Klaviyo](https://agentdrives.com/tools/klaviyo.md?via=md): L1 · Needs a person · [Kit vs Klaviyo](https://agentdrives.com/compare/kit-vs-klaviyo?via=md)
- [Mailchimp](https://agentdrives.com/tools/mailchimp.md?via=md): L1 · Needs a person · [Kit vs Mailchimp](https://agentdrives.com/compare/kit-vs-mailchimp?via=md)
- [MailerLite](https://agentdrives.com/tools/mailerlite.md?via=md): L1 · Needs a person · [Kit vs MailerLite](https://agentdrives.com/compare/kit-vs-mailerlite?via=md)

## Tips for agent builders

- Use developers.kit.com: llms.txt, the .md pages (or Accept: text/markdown) and the OpenAPI at /api-reference/v4.json; kit.com and help.kit.com challenge agents.
- The Developer Docs MCP at https://developers.kit.com/mcp speaks 2026-07-28 without auth: tools search_kit_developer_documentation and query_docs_filesystem_kit_developer_documentation.
- You need a human to create the account and the API key; then send X-Kit-Api-Key on api.kit.com (120 requests per 60 s; OAuth 600).
- Kit's docs say free plans and lapsed trials get 401 on API and webhook endpoints, and the Kit MCP needs a paid plan: check plan_type on GET /v4/account first.
- Bulk and purchase endpoints need OAuth, not an API key.