Try itExperimental
See what an agent can do with Kit before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -s https://api.kit.com/v4/subscribers | head -c 120 # v4 API, keyless → Authentication Failedrecorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Analytics attribution — stories about analytics attribution in this arenaAnalytics attributionevidence →
Stories about analytics attribution in this arena
Audience segmentation — stories about audience segmentation in this arenaAudience segmentationevidence →
Stories about audience segmentation in this arena
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Campaign sending — stories about campaign sending in this arenaCampaign sendingevidence →
Stories about campaign sending in this arena
Deliverability domains — stories about deliverability domains in this arenaDeliverability domainsevidence →
Stories about deliverability domains in this arena
Integrations webhooks — stories about integrations webhooks in this arenaIntegrations webhooksevidence →
Stories about integrations webhooks in this arena
Lifecycle automation — stories about lifecycle automation in this arenaLifecycle automationevidence →
Stories about lifecycle automation in this arena
List portability — stories about list portability in this arenaList portabilityevidence →
Stories about list portability in this arena
Marketing data access — stories about marketing data access in this arenaMarketing data accessevidence →
Stories about marketing data access in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Template content — stories about template content in this arenaTemplate contentevidence →
Stories about template content in this arena
Transactional sending — stories about transactional sending in this arenaTransactional sendingevidence →
Stories about transactional sending in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Kit stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Webhooks · Official SDKs · Scoped API keys · Machine-readable spec · Versioning policy · API sandbox · Official CLI · Full data export · Connect the platform to my existing stack — Stripe or Shopify, a CDP like Segment, my product database — with maintained first-party integrations · Subscribe webhooks to delivery and engagement events — sends, opens, clicks, bounces, unsubscribes — with a documented, signed payload
Subscribe to events via webhooks
—–
Build against official SDKs
—0/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
✓8/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
—–
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
—0/10
Operate the product with natural-language commands
✓7/10
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
~4/10
Set up automations that run autonomously in the background
~5/10
Analytics attribution — stories about analytics attribution in this arenaAnalytics attribution
Stories about analytics attribution in this arena
Audience segmentation — stories about audience segmentation in this arenaAudience segmentation
Stories about audience segmentation in this arena
An agent can translate a plain-language audience description into a real segment via the platform's programmatic surface
—0/10
Create, update, and suppress contacts with custom properties through the API at production scale
—–
Create and update segments, tags, or lists programmatically and read back exactly who is in them
—0/10
Build audience segments from profile attributes, tags, and behavioral events, and they stay live as data changes
~3/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Automation depth
Define rules that trigger actions automatically on events
~4/10
unlocks → Versioned workflows · Fire a custom event from my product and have it trigger an automation for exactly that person · See where any individual person sits inside an automation and pull or re-enter them without breaking the flow
Schedule recurring jobs or workflows
~3/10
unlocks → Versioned workflows
Perform bulk operations across many items at once
~5/10
Version, review, and roll back my automations
—–
Campaign sending — stories about campaign sending in this arenaCampaign sending
Stories about campaign sending in this arena
An agent can draft a campaign against a segment and leave it scheduled or queued for a human to approve before send
~6/10
Create and schedule a campaign or broadcast entirely through a documented public API, without touching the dashboard
✓7/10
Compose an email campaign, pick its audience, and send or schedule it — the arena's table-stakes loop
✓8/10
A/B test subject lines or content variants and have the winner picked from real engagement
~4/10
Deliverability domains — stories about deliverability domains in this arenaDeliverability domains
Stories about deliverability domains in this arena
See bounce, complaint, and blocklist signals per send and get actionable guidance when deliverability degrades
—–
Authenticate my own sending domain — SPF, DKIM, DMARC alignment — with guided DNS setup and verification
—–
Unsubscribes, bounces, and spam complaints are suppressed automatically and honored across every send type — CAN-SPAM/GDPR hygiene by default
—–
Integrations webhooks — stories about integrations webhooks in this arenaIntegrations webhooks
Stories about integrations webhooks in this arena
Lifecycle automation — stories about lifecycle automation in this arenaLifecycle automation
Stories about lifecycle automation in this arena
Build multi-step lifecycle automations — welcome series, onboarding, winback — with branches, delays, and exit rules
~4/10
Fire a custom event from my product and have it trigger an automation for exactly that person
—–
See where any individual person sits inside an automation and pull or re-enter them without breaking the flow
—0/10
List portability — stories about list portability in this arenaList portability
Stories about list portability in this arena
Marketing data access — stories about marketing data access in this arenaMarketing data access
Stories about marketing data access in this arena
An agent can pull my whole email program — audiences, live automations, recent campaign results — programmatically and report on what's working
~4/10
Read per-person engagement history — what was sent, opened, clicked — through the API for any contact
—0/10
Mint scoped or read-only API credentials so an agent or contractor can read analytics without the power to send
—–
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Template content — stories about template content in this arenaTemplate content
Stories about template content in this arena
Have the platform's built-in AI draft or refine subject lines and email copy from a brief, inside the composer
—0/10
Design on-brand emails with a visual editor, reusable templates, and personalization tokens that render correctly across clients
—–
Manage email templates as code — HTML/MJML or API-managed templates with variable substitution — under version control
—–
Transactional sending — stories about transactional sending in this arenaTransactional sending
Stories about transactional sending in this arena
Send one-to-one transactional email — receipts, magic links, notifications — through the same platform's API alongside marketing sends
—0/10
Transactional email is kept separate from marketing — its own templates, suppression rules, and reputation — so a receipt still delivers to an unsubscribed contact
—–
Sorted by importance (agentic first) (high → low) · 58/58 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | 0/10 | ||
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 3/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | none | untested | none yet | |
Compose an email campaign, pick its audience, and send or schedule it — the arena's table-stakes loop C Campaign core | marketer | Campaign sending — stories about campaign sending in this arenaCampaign sending | 3 | full | 8/10 | Cclaimed | |
Create and schedule a campaign or broadcast entirely through a documented public API, without touching the dashboard C Api campaigns | developer | Campaign sending — stories about campaign sending in this arenaCampaign sending | 3 | full | 7/10 | Tprobed | |
An agent can draft a campaign against a segment and leave it scheduled or queued for a human to approve before send C Agent campaigns | ai-native user | Campaign sending — stories about campaign sending in this arenaCampaign sending | 3 | partial | 6/10 | Cclaimed | |
Build multi-step lifecycle automations — welcome series, onboarding, winback — with branches, delays, and exit rules C Automation core | marketer | Lifecycle automation — stories about lifecycle automation in this arenaLifecycle automation | 3 | partial | 4/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 4/10 | Cclaimed | |
Build audience segments from profile attributes, tags, and behavioral events, and they stay live as data changes C Segment core | marketer | Audience segmentation — stories about audience segmentation in this arenaAudience segmentation | 3 | partial | 3/10 | Cclaimed | |
Create and update segments, tags, or lists programmatically and read back exactly who is in them C Api segments | developer | Audience segmentation — stories about audience segmentation in this arenaAudience segmentation | 3 | none | 0/10 | ||
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
Read per-person engagement history — what was sent, opened, clicked — through the API for any contact C Api access | developer | Marketing data access — stories about marketing data access in this arenaMarketing data access | 3 | none | 0/10 | ||
Send one-to-one transactional email — receipts, magic links, notifications — through the same platform's API alongside marketing sends C Transactional api | developer | Transactional sending — stories about transactional sending in this arenaTransactional sending | 3 | none | 0/10 | ||
Authenticate my own sending domain — SPF, DKIM, DMARC alignment — with guided DNS setup and verification C Domain auth | ops user | Deliverability domains — stories about deliverability domains in this arenaDeliverability domains | 3 | none | untested | none yet | |
Create, update, and suppress contacts with custom properties through the API at production scale C Api contacts | developer | Audience segmentation — stories about audience segmentation in this arenaAudience segmentation | 3 | none | untested | none yet | |
Export my entire audience — contacts, custom fields, tags, engagement history, and suppression list — in an open format, self-serve C Export | founder | List portability — stories about list portability in this arenaList portability | 3 | none | untested | none yet | |
Fire a custom event from my product and have it trigger an automation for exactly that person C Event triggers | developer | Lifecycle automation — stories about lifecycle automation in this arenaLifecycle automation | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Read opens, clicks, unsubscribes, and conversions per campaign and per automation step, over time C Reporting core | marketer | Analytics attribution — stories about analytics attribution in this arenaAnalytics attribution | 3 | none | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | untested | none yet | |
Subscribe webhooks to delivery and engagement events — sends, opens, clicks, bounces, unsubscribes — with a documented, signed payload C Webhooks | developer | Integrations webhooks — stories about integrations webhooks in this arenaIntegrations webhooks | 3 | none | untested | none yet | |
Unsubscribes, bounces, and spam complaints are suppressed automatically and honored across every send type — CAN-SPAM/GDPR hygiene by default C Suppression | ops user | Deliverability domains — stories about deliverability domains in this arenaDeliverability domains | 3 | none | untested | none yet | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 5/10 | Tprobed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 5/10 | Tprobed | |
A/B test subject lines or content variants and have the winner picked from real engagement C Experiments | marketer | Campaign sending — stories about campaign sending in this arenaCampaign sending | 2 | partial | 4/10 | Cclaimed | |
An agent can pull my whole email program — audiences, live automations, recent campaign results — programmatically and report on what's working C Agent access | ai-native user | Marketing data access — stories about marketing data access in this arenaMarketing data access | 2 | partial | 4/10 | Tprobed | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 3/10 | Cclaimed | |
An agent can translate a plain-language audience description into a real segment via the platform's programmatic surface C Agent segments | ai-native user | Audience segmentation — stories about audience segmentation in this arenaAudience segmentation | 2 | none | 0/10 | ||
Attribute signups or revenue to specific emails and flows, not just opens and clicks C Attribution | founder | Analytics attribution — stories about analytics attribution in this arenaAnalytics attribution | 2 | none | 0/10 | ||
Connect the platform to my existing stack — Stripe or Shopify, a CDP like Segment, my product database — with maintained first-party integrations C First party integrations | ops user | Integrations webhooks — stories about integrations webhooks in this arenaIntegrations webhooks | 2 | none | 0/10 | ||
Have the platform's built-in AI draft or refine subject lines and email copy from a brief, inside the composer C Ai content | marketer | Template content — stories about template content in this arenaTemplate content | 2 | none | 0/10 | ||
Migrate in from another email platform with guided list import that preserves tags, custom fields, and unsubscribe state C Import migration | marketer | List portability — stories about list portability in this arenaList portability | 2 | none | 0/10 | ||
Pull campaign and flow performance metrics through the API into my own warehouse or dashboards C Api metrics | developer | Analytics attribution — stories about analytics attribution in this arenaAnalytics attribution | 2 | none | 0/10 | ||
See where any individual person sits inside an automation and pull or re-enter them without breaking the flow C Flow operations | ops user | Lifecycle automation — stories about lifecycle automation in this arenaLifecycle automation | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Design on-brand emails with a visual editor, reusable templates, and personalization tokens that render correctly across clients C Editor | marketer | Template content — stories about template content in this arenaTemplate content | 2 | none | untested | none yet | |
Manage email templates as code — HTML/MJML or API-managed templates with variable substitution — under version control C Templates as code | developer | Template content — stories about template content in this arenaTemplate content | 2 | none | untested | none yet | |
Mint scoped or read-only API credentials so an agent or contractor can read analytics without the power to send C Scoped access | ops user | Marketing data access — stories about marketing data access in this arenaMarketing data access | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | n/a | untested | none yet | |
See bounce, complaint, and blocklist signals per send and get actionable guidance when deliverability degrades C Deliverability signals | marketer | Deliverability domains — stories about deliverability domains in this arenaDeliverability domains | 2 | none | untested | none yet | |
Transactional email is kept separate from marketing — its own templates, suppression rules, and reputation — so a receipt still delivers to an unsubscribed contact C Transactional hygiene | ops user | Transactional sending — stories about transactional sending in this arenaTransactional sending | 2 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 49 stories with headroom
What would move Kit’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
nonemoves Built-in AIimpact 45
Evidence only documents an MCP server that lets external AI agents (e.g., Claude) query Kit's docs and perform actions via natural language — this is agent-facing infrastructure, not a built-in AI assistant embedded in the Kit product UI itself.
Analytics attribution — stories about analytics attribution in this arenaRead opens, clicks, unsubscribes, and conversions per campaign and per automation step, over time
nonemoves PA Scoreimpact 30
Missing: analytics dashboard docs, per-campaign/per-step metrics, conversion tracking evidence.
Audience segmentation — stories about audience segmentation in this arenaCreate, update, and suppress contacts with custom properties through the API at production scale
nonemoves PA Scoreimpact 30
The evidence pack only covers broadcasts API, MCP docs, pricing features, and general company history — there is no documentation of contact/subscriber creation, updates, custom field/property management, or suppression via the API, nor any mention of production-scale rate limits or bulk operations.
Deliverability domains — stories about deliverability domains in this arenaAuthenticate my own sending domain — SPF, DKIM, DMARC alignment — with guided DNS setup and verification
nonemoves PA Scoreimpact 30
No evidence in the pack addresses domain authentication (SPF/DKIM/DMARC) setup, guided DNS configuration, or verification tooling; the evidence only covers broadcasts, MCP, pricing tiers, and general marketing.
Marketing data access — stories about marketing data access in this arenaRead per-person engagement history — what was sent, opened, clicked — through the API for any contact
nonemoves PA Scoreimpact 30
Evidence covers broadcast creation, MCP server, and pricing features, but nothing shows an API endpoint for retrieving per-subscriber engagement history (sent/opened/clicked events) for a given contact.
Lifecycle automation — stories about lifecycle automation in this arenaFire a custom event from my product and have it trigger an automation for exactly that person
nonemoves PA Scoreimpact 30
The evidence pack covers broadcasts API, MCP docs integration, and pricing features, but contains no mention of a custom-event API or webhook mechanism that lets a developer fire an event to trigger a per-subscriber automation.
List portability — stories about list portability in this arenaExport my entire audience — contacts, custom fields, tags, engagement history, and suppression list — in an open format, self-serve
nonemoves PA Scoreimpact 30
The evidence pack contains no mention of a self-serve data export feature (CSV/CSV-like) covering contacts, tags, custom fields, engagement history, or suppression lists; only API endpoints for broadcasts and pricing feature lists are present, none of which address audience export or portability.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
No evidence pack item documents a data export feature or open-format data portability for Kit; only a vague mention of 'Free migrations' (import-side) appears, with no explicit export/download-your-data capability.
Showing the top 8 of 49 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map6 surfaces · 18 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
MCP docs11 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Operate the product with natural-language commands
- Perform bulk operations across many items at once
- Schedule recurring jobs or workflows
- An agent can draft a campaign against a segment and leave it scheduled or queued for a human to approve before send
- An agent can pull my whole email program — audiences, live automations, recent campaign results — programmatically and report on what's working
- Do everything through the API that I can do in the UI
API reference10 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build audience segments from profile attributes, tags, and behavioral events, and they stay live as data changes
- Perform bulk operations across many items at once
- Schedule recurring jobs or workflows
- An agent can draft a campaign against a segment and leave it scheduled or queued for a human to approve before send
- Create and schedule a campaign or broadcast entirely through a documented public API, without touching the dashboard
- Compose an email campaign, pick its audience, and send or schedule it — the arena's table-stakes loop
- An agent can pull my whole email program — audiences, live automations, recent campaign results — programmatically and report on what's working
- Do everything through the API that I can do in the UI
Pricing docs6 stories
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Define rules that trigger actions automatically on events
- Schedule recurring jobs or workflows
- A/B test subject lines or content variants and have the winner picked from real engagement
- Build multi-step lifecycle automations — welcome series, onboarding, winback — with branches, delays, and exit rules
llms.txt3 stories
OpenAPI spec3 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -s https://api.kit.com/v4/subscribers | head -c 120 # v4 API, keyless → Authentication Failedreproduced$ curl -s https://api.kit.com/v4/subscribers | head -c 120 # v4 API, [redacted]less → Authentication Failed
{"errors":["Authentication Failed"]}
$curl -sL https://developers.kit.com/llms.txt | head -6reproduced$ curl -sL https://developers.kit.com/llms.txt | head -6 # Kit Developer Documentation - [Welcome](https://developers.kit.com/welcome.md) - [MCP overview](https://developers.kit.com/mcp/overview.md): How to access Kit programmatically — the REST API and Kit's two MCP servers. - [Kit Developer Docs MCP](https://developers.kit.com/mcp/kit-developer-docs-mcp.md): Connect AI coding agents directly to Kit's developer documentation using the Model Context Protocol - [Kit MCP](https://developers.kit.com/mcp/kit-mcp.md): Let AI clients act on a creator's Kit account via the Model Context Protocol.
$curl -si -X POST https://app.kit.com/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # the remote Kit MCP (paid plans)reproduced$ curl -si -X POST https://app.kit.com/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # the remote Kit MCP (paid plans) HTTP/2 401 www-authenticate: Bearer resource_metadata="https://app.kit.com/.well-known/oauth-protected-resource/mcp"
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
5 of 10 testable claims verified · 2 contradicted → integrity 10/100
17 distinct capability claims found in Kit’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
5
Verified
3
Unverified
2
Contradicted
10
Undersold
Verified (5)
“Target broadcasts to subscribers based on segment or tag IDs”
Create and schedule a campaign or broadcast entirely through a documented public API, without touching the dashboardfullproof ↗
“Public API lets third-party developers build on top of or integrate with the Kit platform”
Drive the product through a documented public APIfullproof ↗
“Official MCP server exposes live developer docs so agents query current API surface instead of stale/cached info”
“Natural-language prompts (e.g. 'draft a broadcast to my new subscribers') trigger real account actions via an agent”
Operate the product with natural-language commandsfullproof ↗
“Subscriber engagement scoring”
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
Unverified (3)
“Compose and send or schedule a broadcast email to all or a subset of subscribers”
Compose an email campaign, pick its audience, and send or schedule it — the arena's table-stakes loopfullproof ↗
“Unlimited visual multi-step automations”
Build multi-step lifecycle automations — welcome series, onboarding, winback — with branches, delays, and exit rulespartialproof ↗
“A/B test subject lines and email content”
A/B test subject lines or content variants and have the winner picked from real engagementpartialproof ↗
Contradicted (2)
“Connect creator tools and apps directly to Kit to automate work”
Connect the platform to my existing stack — Stripe or Shopify, a CDP like Segment, my product database — with maintained first-party integrationsnoneproof ↗
“Offers free migration assistance when switching to Kit from another platform”
Migrate in from another email platform with guided list import that preserves tags, custom fields, and unsubscribe statenoneproof ↗
Undersold (10)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Build audience segments from profile attributes, tags, and behavioral events, and they stay live as data changespartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
An agent can draft a campaign against a segment and leave it scheduled or queued for a human to approve before sendpartialproof ↗
An agent can pull my whole email program — audiences, live automations, recent campaign results — programmatically and report on what's workingpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Claims outside our story set (7)
Real capability claims found in Kit’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Survey subscribers with polls”
source ↗“Collaborative editing of content”
source ↗“Sell digital products and subscriptions directly”
source ↗“Unlimited landing pages and forms”
source ↗“RSS-to-email campaigns”
source ↗“Grow subscriber list via landing pages, forms, and creator recommendations”
source ↗“Monetize via digital products, subscriptions, and newsletter sponsorships on autopilot”
source ↗
Business model
Free Newsletter plan to 10,000 subscribers; V4 API and the Kit MCP require paid Creator ($33+/month) or Creator Pro plans.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
