Compare
Built for agents, not adapted for them.
Every newsletter tool sends email. The difference is who does the work: a human in a browser tab, or an agent calling an API. Here is where each platform stands.
| Capability | Dispatch | Substack | Beehiiv | ConvertKit |
|---|---|---|---|---|
| Built for AI agents (API and MCP first) | — | — | — | |
| MCP server for Claude Code, Cursor, and Codex | — | — | — | |
| Create and send issues from Markdown via API | — | PartialAPI exists | PartialAPI exists | |
| Scoped API keys per publication | — | |||
| Schedule sends via API | — | |||
| Drip sequences (welcome series, email courses, nurture) | Partialwelcome email only | |||
| Drip sequences an AI agent can build and manage (API and MCP) | — | — | — | |
| Machine-readable archive (feed plus raw Markdown per issue) | — | — | — | |
| Per-issue stats readable via API | — | |||
| Per-publication sending domains | — | |||
| Embeddable signup form, one line of code | ||||
| Double opt-in and one-click unsubscribe | ||||
| Automatic bounce and complaint suppression | ||||
| Free to start | 3,000 emails/mo | Free tier | Free tier | Free tier |
Correct as of October 2026. Platforms change; if a cell is wrong, tell us and we will fix it.
If a human writes your newsletter, any of these work.
If an agent writes it from your database on a schedule, only one of them was built for that. One API call creates the publication, the signup form, the sending domain, and the API key.
Start a publication