What Is Kit? Creator Email, Formerly ConvertKit
By Joris van Huët · Kit's own site
The short answer: if you sell courses, products or paid posts to your audience and want tags, sequences and purchase history to decide who gets which email, Kit is built around that, with a public API, webhooks and an MCP server. It is the former ConvertKit: convertkit.com now redirects to kit.com. Its developer documentation names the paid plans Creator and Creator Pro (Kit MCP docs).
Disclosure: I may earn a commission through some links on this site. It does not change what this page says.
Before you connect your stack:
- Price the mistake first. Adding subscribers to a double opt-in form through the API sends each one an incentive email (bulk form docs). For example, backfilling 5,000 past buyers that way is 5,000 x 1 = 5,000 confirmation emails to people who never asked for one. Tag them instead.
- Start from the data you already hold. Shop orders can be recorded against subscribers through the purchases endpoint, which needs OAuth, creates the subscriber if needed and can drive purchase-based automations (create a purchase).
- Fix the scoreboard. The account stats endpoint returns sends, opens, clicks and unsubscribe and bounce rates for the last 90 days (email stats docs). Pull it into the report you already send.
What Kit does
Kit manages subscribers with tags, custom fields and segments, sends broadcasts and sequences, records purchases, publishes posts with a paid flag for paywalled ones, and lists creators in its Creator Network (API reference). Developers can build App Store apps and editor plugins, and receive webhooks when subscribers are created, activated or join a form (webhooks overview).
Two MCP servers sit on top: a read-only one for the developer docs, and the Kit MCP at app.kit.com/mcp, which lets Claude, ChatGPT or Cursor read and write your account on paid plans, with actions such as sending a broadcast always needing your explicit confirmation (Kit MCP docs).
Who it suits
It suits creators and small creator businesses whose email is a sales channel: course launches, product drops, offers segmented by tag, and marketers who want to wire app or checkout signups into email logic. It is less suited to a team that only needs a weekly newsletter and never touches tags.
What it costs
I could not read Kit's prices: on 24 October 2026 the Kit pricing page, homepage and help centre returned a bot check to automated reading, so open the pricing page for figures. Kit's API overview says API access depends on the plan being eligible, and the MCP documentation puts the Kit MCP on the paid Creator and Creator Pro plans.
How it compares
beehiiv. beehiiv is free up to 2,500 subscribers and lists a 0% take rate on paid subscriptions from its Lite plan (beehiiv pricing); its MCP is read-only on the free plan. Choose beehiiv when the newsletter itself is the product to grow; choose Kit when the newsletter feeds products you sell.
Flodesk. Flodesk starts from design, custom fonts and layouts, and prices by active subscribers, $25 a month on monthly billing for up to 1,000 on Lite (Flodesk pricing). Kit puts its depth into routing and integrations; Flodesk puts it into design.
An app store is a good thing and also a structural pull: every app you connect is another reason to stay. Connect the ones that remove manual work, and keep a regular export of subscribers and tags.
Getting started
Define your tags, then send product signups through the API, tag them and start the right sequence: How to use Kit works through it.
FAQ
Is Kit the same company as ConvertKit?
Yes. Requests to convertkit.com and help.convertkit.com redirect to kit.com, and Kit's upgrade guide moves API calls from api.convertkit.com/v3 to api.kit.com/v4.
Can an AI assistant send a broadcast from Kit on its own?
No. The Kit MCP docs say sending broadcasts and deleting data always require your explicit confirmation, and requests are limited to 120 per minute per token.
Which API version should I build on?
Version 4. Kit says API V3 still works but is deprecated and will be sunset, and recommends V4 for all new projects (API overview).