Kit vs Bento
Bento wins · 5–18 (32 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round drawnKit provides a live llms.txt file confirmed by probe (HTTP 200 with structured doc links) plus agent-oriented docs including an official MCP server that queries live docs to avoid hallucinated API surfaces. Missing for 10: independent third-party confirmation of an AI agent successfully using llms.txt in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.kit.com/llms.txt # Kit Developer Documentation - [Welcome](https://developers.kit.com/welcom…”
- [claimed-docs] “connect the Kit Developer Docs MCP. It queries the live docs so your agent stops working from a cached or hallucinated API surface.”
- [claimed-docs] “Natural-language prompts like “draft a broadcast to my new subscribers from this week” become real account actions.”
- [probe] “official MCP server documented at https://developers.kit.com/mcp/overview”
Bento has a live, confirmed llms.txt (HTTP 200) and a docs.md agent-friendly documentation file, directly enabling an AI agent to be pointed at agent-oriented docs, plus a documented MCP server for deeper agent integration. Missing for 10: independent third-party confirmation that agents actually consume these files effectively in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://bentonow.com/llms.txt # Bento (bentonow.com) — An Email Marketing and Automation Platform ## Overview B…”
- [probe] “PROBE docs-md: HTTP 200 at https://bentonow.com/docs.md # Bento Documentation Complete documentation for Bento email marketing platform. AP…”
- [claimed-docs] “Dedicated IP address options for high-volume senders”
- [claimed-docs] “The Bento MCP server gives your AI assistant direct access to your Bento account. It can look up subscribers, create broadcasts, track event…”
- [probe] “official MCP server documented at https://bentonow.com/docs/integrations/mcp”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round drawnKit exposes a REST API and an MCP server that let third-party tools or agents trigger actions (e.g., drafting broadcasts) programmatically, which could in principle be scripted into a CI pipeline, but there is no documentation of a CLI, headless mode, or explicit CI/automation-pipeline usage. missing for 10: explicit CI/headless execution docs, a CLI or non-interactive mode, and any independent evidence of running Kit unattended in automated pipelines.
- [claimed-docs] “If you are a third party developer, you can use the Kit API to link together or build on top of the Kit platform.”
- [claimed-docs] “connect the Kit Developer Docs MCP. It queries the live docs so your agent stops working from a cached or hallucinated API surface.”
- [claimed-docs] “Natural-language prompts like “draft a broadcast to my new subscribers from this week” become real account actions.”
- [probe] “official MCP server documented at https://developers.kit.com/mcp/overview”
Bento exposes REST-style APIs (events, subscribers) that could be scripted, and one marketing line mentions scripting a weekly job, but there is no documented CLI, headless mode, or CI/automation guide, and no OpenAPI spec was found (404s). missing for 10: explicit CI/headless documentation, CLI tool, and API spec/reference for automated pipelines.
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [claimed-docs] “Import subscribers, find a record, or script the job you run every week.”
- [probe] “PROBE openapi: all candidate paths 404 (https://bentonow.com/openapi.json, https://bentonow.com/swagger.json, https://bentonow.com/api/opena…”
ai-native userConnect an agent via an official MCP server
weight 3 · round drawnKit's developer docs explicitly describe and document an official MCP server ('Kit Developer Docs MCP') that lets agents query live API docs and turn natural-language prompts into real account actions, and a probe confirms this page is live. Missing for 10: independent/hands-on third-party confirmation that the MCP server works as described beyond first-party docs.
- [claimed-docs] “connect the Kit Developer Docs MCP. It queries the live docs so your agent stops working from a cached or hallucinated API surface.”
- [claimed-docs] “Natural-language prompts like “draft a broadcast to my new subscribers from this week” become real account actions.”
- [probe] “official MCP server documented at https://developers.kit.com/mcp/overview”
Bento documents an official MCP server that gives AI assistants direct access to the account (subscriber lookup, broadcast creation, event tracking) via natural conversation, confirmed by both docs and a probe hit on the integration page. Missing for 10: independent/hands-on corroboration beyond first-party docs and more detail on setup/auth specifics.
- [claimed-docs] “The Bento MCP server gives your AI assistant direct access to your Bento account. It can look up subscribers, create broadcasts, track event…”
- [probe] “official MCP server documented at https://bentonow.com/docs/integrations/mcp”
ai-native userUse an official CLI
weight 2 · round drawnKitnone0/10Kit's evidence pack covers its REST API, MCP server for AI agents, and marketing features, but nowhere mentions a CLI tool for developers or AI-native workflows. Since Kit is a SaaS platform where an official CLI is a plausible offering, absence of evidence means this axis is unmet rather than inapplicable.
- [claimed-docs] “If you are a third party developer, you can use the Kit API to link together or build on top of the Kit platform.”
- [claimed-docs] “connect the Kit Developer Docs MCP. It queries the live docs so your agent stops working from a cached or hallucinated API surface.”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.kit.com/llms.txt # Kit Developer Documentation - [Welcome](https://developers.kit.com/welcom…”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.kit.com/openapi.json, https://developers.kit.com/swagger.json, https://developers…”
ai-native userDrive the product through a documented public API
weight 3 · round to KitKit publishes a documented public API (broadcasts, subscribers, segments/tags) with a developer reference and overview explicitly aimed at third-party developers building on the platform, plus an llms.txt for AI-native discovery. Missing for 10: a publicly discoverable OpenAPI/Swagger spec (probe found only 404s) and independent hands-on developer corroboration beyond vendor docs.
- [claimed-docs] “Draft or schedule to send a broadcast to all or a subset of your subscribers.”
- [claimed-docs] “We currently support targeting your subscribers based on segment or tag ids.”
- [claimed-docs] “If you are a third party developer, you can use the Kit API to link together or build on top of the Kit platform.”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.kit.com/llms.txt # Kit Developer Documentation - [Welcome](https://developers.kit.com/welcom…”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.kit.com/openapi.json, https://developers.kit.com/swagger.json, https://developers…”
Bento documents multiple REST-style APIs (events, subscribers, transactional email) and provides machine-readable docs (llms.txt, docs.md) explicitly aimed at AI agents, plus an MCP server for natural-language control of the account. This satisfies the 'documented public API' story, though no formal OpenAPI/Swagger spec was found (404s on all candidate paths). Missing for 10: a discoverable OpenAPI/Swagger schema and independent third-party confirmation of programmatic API usage.
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [claimed-docs] “Request supports 1 to 1000 subscribers per post.”
- [claimed-docs] “Transactional email is for messages a person needs because of an action, request, or account state: password resets, receipts, login codes, …”
- [probe] “PROBE llms.txt: HTTP 200 at https://bentonow.com/llms.txt # Bento (bentonow.com) — An Email Marketing and Automation Platform ## Overview B…”
- [probe] “PROBE docs-md: HTTP 200 at https://bentonow.com/docs.md # Bento Documentation Complete documentation for Bento email marketing platform. AP…”
- [probe] “PROBE openapi: all candidate paths 404 (https://bentonow.com/openapi.json, https://bentonow.com/swagger.json, https://bentonow.com/api/opena…”
- [claimed-docs] “The Bento MCP server gives your AI assistant direct access to your Bento account. It can look up subscribers, create broadcasts, track event…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnKitnone0/10Evidence shows Kit has an API and an MCP server for agent integration, but nothing describes issuing scoped or least-privilege API keys/tokens (e.g., granular permission scopes, read-only vs write keys) for agents. missing for 10: any documentation of scoped API key creation, permission/role-based tokens, or least-privilege credential issuance for agent use.
- [claimed-docs] “If you are a third party developer, you can use the Kit API to link together or build on top of the Kit platform.”
- [claimed-docs] “connect the Kit Developer Docs MCP. It queries the live docs so your agent stops working from a cached or hallucinated API surface.”
- [claimed-docs] “Natural-language prompts like “draft a broadcast to my new subscribers from this week” become real account actions.”
ai-native userBuild against official SDKs
weight 2 · round to BentoKitnone0/10Evidence shows Kit has a REST API with reference docs and an MCP server, but nothing indicates official client SDKs (e.g., Python/JS/Ruby libraries); in fact the OpenAPI spec probe returned 404s, suggesting no machine-generated or officially maintained SDK tooling. missing for 10: evidence of any official SDK/client library, language coverage, or published OpenAPI spec used to generate SDKs.
- [claimed-docs] “If you are a third party developer, you can use the Kit API to link together or build on top of the Kit platform.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.kit.com/openapi.json, https://developers.kit.com/swagger.json, https://developers…”
Docs.md teaser mentions 'API guides, SDK references' but the evidence pack never names specific official SDKs, languages, or repos, only a generic mention plus an MCP server for AI assistants. Missing for 10: explicit list of official SDKs (e.g., language libraries), links to SDK documentation/repos, code samples, and independent developer corroboration of SDK usage.
- [probe] “PROBE docs-md: HTTP 200 at https://bentonow.com/docs.md # Bento Documentation Complete documentation for Bento email marketing platform. AP…”
- [claimed-docs] “The Bento MCP server gives your AI assistant direct access to your Bento account. It can look up subscribers, create broadcasts, track event…”
- [probe] “official MCP server documented at https://bentonow.com/docs/integrations/mcp”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnKitnone0/10No evidence in the pack of Kit offering webhook subscriptions for events; documentation covers API endpoints, broadcasts, MCP, and pricing but never mentions webhooks. Missing for 10: any webhook documentation, event types, subscription/registration endpoints, or delivery mechanism.
Bentonone0/10Evidence covers Bento's Events API (tracking inbound events), subscriber management, and an MCP server, but there is no mention of outbound webhook subscriptions that would let an AI-native user subscribe to Bento events. Missing for 10: any documentation of a webhooks feature, webhook endpoint configuration, or event subscription mechanism.
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [claimed-docs] “Import subscribers, find a record, or script the job you run every week.”
- [claimed-docs] “Build flows from behavior, events, and tags. Check every branch before it runs.”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round drawnKit offers subscriber engagement scoring and an MCP integration that lets an agent draft actions like broadcasts from natural-language prompts, which touches on data-driven suggestions, but there is no documented feature that surfaces AI-generated insights or recommendations from a user's own data (e.g., analytics summaries, content suggestions). Missing for 10: dedicated AI insight/analytics generation feature, evidence of proactive suggestions surfaced in-app, independent corroboration of engagement scoring being AI-driven.
- [claimed-docs] “Subscriber engagement scoring”
- [claimed-docs] “connect the Kit Developer Docs MCP. It queries the live docs so your agent stops working from a cached or hallucinated API surface.”
- [claimed-docs] “Natural-language prompts like “draft a broadcast to my new subscribers from this week” become real account actions.”
- [probe] “official MCP server documented at https://developers.kit.com/mcp/overview”
Bento advertises AI that can 'build' flows/segments from plain text and an MCP server letting an AI assistant query subscriber/event data conversationally, which implies some AI-data interaction, but there is no explicit documentation of AI-generated insights, analytics summaries, or proactive suggestions derived from the user's data. Missing for 10: dedicated AI insights/reporting feature, evidence of proactive suggestions, and independent confirmation of this capability in use.
- [claimed-docs] “Describe what you want in plain text and let Bento's powerful AI build it for you.”
- [claimed-docs] “The Bento MCP server gives your AI assistant direct access to your Bento account. It can look up subscribers, create broadcasts, track event…”
- [probe] “official MCP server documented at https://bentonow.com/docs/integrations/mcp”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to BentoKit ships 'Unlimited Visual Automations' as a core background-automation feature, and its MCP server lets AI agents trigger real account actions (e.g., drafting broadcasts) via natural language, showing some agentic setup capability. However, no evidence shows the MCP or API being used to configure/build visual automation workflows themselves (only broadcast creation is exemplified), and there's no confirmation of persistent, autonomously-triggered background execution driven by an AI agent. Missing for 10: documented API/MCP endpoints for creating or editing automation workflows, evidence of scheduled/triggered autonomous runs initiated by AI, independent confirmation of this working end-to-end.
- [claimed-docs] “Unlimited Visual Automations”
- [claimed-docs] “connect the Kit Developer Docs MCP. It queries the live docs so your agent stops working from a cached or hallucinated API surface.”
- [claimed-docs] “Natural-language prompts like “draft a broadcast to my new subscribers from this week” become real account actions.”
- [probe] “official MCP server documented at https://developers.kit.com/mcp/overview”
Bento's docs describe building automation flows triggered by user behavior, events, and tags, with the events API able to trigger automations, and even AI-assisted flow building — this directly supports autonomous background automations for an AI-native marketing use case. Missing for 10: independent/hands-on corroboration of automations running unattended, and more detail on monitoring/error-handling of long-running flows.
- [claimed-docs] “Build flows from behavior, events, and tags. Check every branch before it runs.”
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [claimed-docs] “Describe what you want in plain text and let Bento's powerful AI build it for you.”
- [claimed-docs] “The Bento MCP server gives your AI assistant direct access to your Bento account. It can look up subscribers, create broadcasts, track event…”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to BentoKitnone0/10Evidence 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. No evidence of an in-app assistant for drafting content, automations, or subscriber management.
- [claimed-docs] “connect the Kit Developer Docs MCP. It queries the live docs so your agent stops working from a cached or hallucinated API surface.”
- [claimed-docs] “Natural-language prompts like “draft a broadcast to my new subscribers from this week” become real account actions.”
- [probe] “official MCP server documented at https://developers.kit.com/mcp/overview”
Bento markets an in-product AI ('Describe what you want in plain text and let Bento's powerful AI build it for you') suggesting a built-in assistant for flow creation, but there's no detailed documentation of scope, task types, or interaction model beyond this marketing line. The MCP server evidence is about external AI assistants accessing Bento, not a built-in assistant, so it doesn't count here. Missing for 10: detailed docs/UI showing the built-in assistant's task range, hands-on usage examples, and independent corroboration of its capabilities.
- [claimed-docs] “Describe what you want in plain text and let Bento's powerful AI build it for you.”
ai-native userOperate the product with natural-language commands
weight 2 · round drawnKit ships an official Developer Docs MCP server explicitly designed so natural-language prompts (e.g., 'draft a broadcast to my new subscribers from this week') translate into real account actions, confirmed by both docs and a probe verifying the MCP endpoint exists. Missing for 10: independent/hands-on verification of natural-language command execution beyond the single documented example, and broader coverage of which actions are supported via NL.
- [claimed-docs] “connect the Kit Developer Docs MCP. It queries the live docs so your agent stops working from a cached or hallucinated API surface.”
- [claimed-docs] “Natural-language prompts like “draft a broadcast to my new subscribers from this week” become real account actions.”
- [probe] “official MCP server documented at https://developers.kit.com/mcp/overview”
Bento ships an official MCP server documented to let an AI assistant look up subscribers, create broadcasts, track events, etc. 'through natural conversation,' and separately advertises a plain-text AI builder for flows, directly supporting natural-language operation. Missing for 10: independent/hands-on corroboration of the MCP server's reliability and broader coverage of natural-language commands beyond the examples given.
- [claimed-docs] “The Bento MCP server gives your AI assistant direct access to your Bento account. It can look up subscribers, create broadcasts, track event…”
- [claimed-docs] “Describe what you want in plain text and let Bento's powerful AI build it for you.”
- [probe] “official MCP server documented at https://bentonow.com/docs/integrations/mcp”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnKitnone0/10Evidence confirms Kit has API reference docs (create-a-broadcast, overview) but nothing describes an interactive console or runnable/try-it-now examples, and a probe for an OpenAPI/Swagger spec (which typically powers such interactive references) returned 404s across all checked paths.
- [claimed-docs] “Draft or schedule to send a broadcast to all or a subset of your subscribers.”
- [claimed-docs] “If you are a third party developer, you can use the Kit API to link together or build on top of the Kit platform.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.kit.com/openapi.json, https://developers.kit.com/swagger.json, https://developers…”
Bentonone0/10Evidence shows only static docs (events/subscribers/transactional-email pages) and an llms.txt/docs.md text dump; explicit probes for OpenAPI/Swagger specs returned 404s, and no mention of an interactive, runnable API console or sandbox exists anywhere in the pack.
- [probe] “PROBE openapi: all candidate paths 404 (https://bentonow.com/openapi.json, https://bentonow.com/swagger.json, https://bentonow.com/api/opena…”
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [claimed-docs] “Request supports 1 to 1000 subscribers per post.”
- [probe] “PROBE llms.txt: HTTP 200 at https://bentonow.com/llms.txt # Bento (bentonow.com) — An Email Marketing and Automation Platform ## Overview B…”
- [probe] “PROBE docs-md: HTTP 200 at https://bentonow.com/docs.md # Bento Documentation Complete documentation for Bento email marketing platform. AP…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnKitnone0/10Kit's developer docs describe an API reference and even an MCP server for live API access, but a direct probe for machine-readable spec endpoints (openapi.json, swagger.json, etc.) returned 404 on all candidates, and no OpenAPI/Swagger download is documented anywhere in the evidence.
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.kit.com/openapi.json, https://developers.kit.com/swagger.json, https://developers…”
- [claimed-docs] “If you are a third party developer, you can use the Kit API to link together or build on top of the Kit platform.”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.kit.com/llms.txt # Kit Developer Documentation - [Welcome](https://developers.kit.com/welcom…”
Bentonone0/10A direct probe for OpenAPI/Swagger specs at all standard paths returned 404, and no evidence pack item shows a downloadable machine-readable API spec; only human-readable docs and an MCP server are documented.
- [probe] “PROBE openapi: all candidate paths 404 (https://bentonow.com/openapi.json, https://bentonow.com/swagger.json, https://bentonow.com/api/opena…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnKitnone0/10No evidence of a sandbox/test environment, staging account, or test-mode API keys distinct from production data; the docs only describe live API/MCP actions against a real account.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnKitnone0/10No evidence of API versioning scheme or a documented deprecation policy; the API reference and overview pages mention endpoints but say nothing about version numbers, sunset timelines, or backward-compatibility guarantees. OpenAPI spec probes also 404, further indicating no formal versioned contract is published.
- [claimed-docs] “If you are a third party developer, you can use the Kit API to link together or build on top of the Kit platform.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.kit.com/openapi.json, https://developers.kit.com/swagger.json, https://developers…”
Bentonone0/10No evidence of API versioning scheme or documented deprecation policy; OpenAPI spec probe returned 404s and no docs mention version numbers or deprecation timelines.
- [probe] “PROBE openapi: all candidate paths 404 (https://bentonow.com/openapi.json, https://bentonow.com/swagger.json, https://bentonow.com/api/opena…”
Analytics attribution — stories about analytics attribution in this arenaAnalytics attribution
Stories about analytics attribution in this arena
Api metrics
developerPull campaign and flow performance metrics through the API into my own warehouse or dashboards
weight 2 · round drawnKitnone0/10The evidence only shows API endpoints for creating/scheduling broadcasts and general platform/MCP docs; there is no mention of any API for retrieving campaign or automation ('flow') performance metrics, open/click stats, or analytics exports suitable for warehousing.
- [claimed-docs] “Draft or schedule to send a broadcast to all or a subset of your subscribers.”
- [claimed-docs] “We currently support targeting your subscribers based on segment or tag ids.”
- [claimed-docs] “If you are a third party developer, you can use the Kit API to link together or build on top of the Kit platform.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.kit.com/openapi.json, https://developers.kit.com/swagger.json, https://developers…”
Bentonone0/10Evidence shows Bento has an Events API and Subscribers API, and mentions revenue attribution to email/flows as a feature, but no documentation describes an API endpoint for pulling campaign or flow performance metrics (opens, clicks, conversions) into an external warehouse or dashboard. An OpenAPI spec search also returned 404s, giving no confirmation of such an endpoint's existence or schema. Missing for 10: documented performance/metrics API endpoint, example payload for campaign/flow stats, evidence of warehouse/dashboard export support.
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [claimed-docs] “Tie sales and recurring revenue back to the email or flow that came before.”
- [probe] “PROBE openapi: all candidate paths 404 (https://bentonow.com/openapi.json, https://bentonow.com/swagger.json, https://bentonow.com/api/opena…”
Attribution
founderAttribute signups or revenue to specific emails and flows, not just opens and clicks
weight 2 · round to BentoKitnone0/10No evidence of revenue/signup attribution reporting tied to specific emails or automations — the pack shows broadcast creation, MCP tooling, and general pricing feature bullets (e.g. engagement scoring, A/B testing) but nothing about linking conversions/signups/revenue back to specific emails or flows. Missing for 10: revenue attribution reporting, signup source tracking per email/flow, any analytics dashboard evidence.
- [claimed-docs] “Draft or schedule to send a broadcast to all or a subset of your subscribers.”
- [claimed-docs] “We currently support targeting your subscribers based on segment or tag ids.”
- [claimed-docs] “Subscriber engagement scoring”
- [claimed-docs] “Sell digital products & subscriptions”
Bento's marketing explicitly claims revenue attribution to specific emails/flows (bento-docs-6) and supports event tracking (bento-docs-1) and flow building from events/behavior (bento-docs-9), which are prerequisites for such attribution. However, there is no documentation detail on how attribution reporting/dashboards actually work, no independent or hands-on confirmation of accuracy, and no mention of signup attribution specifically. missing for 10: detailed attribution reporting docs/UI evidence, signup-specific attribution mechanics, independent verification of revenue attribution accuracy.
- [claimed-docs] “Tie sales and recurring revenue back to the email or flow that came before.”
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [claimed-docs] “Build flows from behavior, events, and tags. Check every branch before it runs.”
Reporting core
marketerRead opens, clicks, unsubscribes, and conversions per campaign and per automation step, over time
weight 3 · round to BentoKitnone0/10No evidence in the pack describes any analytics/reporting feature—no mention of open/click/unsubscribe/conversion tracking per broadcast or automation step; the pack only covers broadcast creation, MCP docs, and pricing feature lists. missing for 10: analytics dashboard docs, per-campaign/per-step metrics, conversion tracking evidence.
Evidence shows Bento tracks events, ties revenue to campaigns/flows, and lets you filter subscribers by tags/segments/dates, implying some analytics capability, but there is no documentation of a dedicated per-campaign or per-automation-step dashboard showing opens, clicks, unsubscribes, and conversions over time. missing for 10: explicit reporting/analytics documentation showing opens/clicks/unsubscribes/conversions broken out per campaign and per automation step over time, and any independent or hands-on confirmation of such reporting UI.
- [claimed-docs] “Tie sales and recurring revenue back to the email or flow that came before.”
- [claimed-docs] “Filter by tags, a segment, or by date ranges on creation, update, last event, and unsubscribe times.”
- [claimed-docs] “Build flows from behavior, events, and tags. Check every branch before it runs.”
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
Audience segmentation — stories about audience segmentation in this arenaAudience segmentation
Stories about audience segmentation in this arena
Agent segments
ai-native userAn agent can translate a plain-language audience description into a real segment via the platform's programmatic surface
weight 2 · round drawnKitnone0/10Evidence shows Kit's API can target broadcasts to existing segment/tag ids and its MCP server can turn natural language into broadcast actions, but there is no documented endpoint or MCP capability for creating or defining a new segment from a plain-language audience description. Missing for 10: a segment-creation API endpoint, MCP/agent workflow demonstrating natural-language-to-segment translation, and any example of dynamic segment criteria being set programmatically.
- [claimed-docs] “We currently support targeting your subscribers based on segment or tag ids.”
- [claimed-docs] “connect the Kit Developer Docs MCP. It queries the live docs so your agent stops working from a cached or hallucinated API surface.”
- [claimed-docs] “Natural-language prompts like “draft a broadcast to my new subscribers from this week” become real account actions.”
- [probe] “official MCP server documented at https://developers.kit.com/mcp/overview”
Bentonone0/10Evidence shows Bento's MCP server can look up subscribers, create broadcasts, and track events (bento-docs-5), and a generic 'describe what you want, AI will build it' feature (bento-docs-10), but no documentation ties this to translating a plain-language description into an actual audience segment via the API/MCP surface — segment filtering is described only as manual tag/date-based filters (bento-docs-8).
- [claimed-docs] “The Bento MCP server gives your AI assistant direct access to your Bento account. It can look up subscribers, create broadcasts, track event…”
- [claimed-docs] “Filter by tags, a segment, or by date ranges on creation, update, last event, and unsubscribe times.”
- [claimed-docs] “Describe what you want in plain text and let Bento's powerful AI build it for you.”
Api contacts
developerCreate, update, and suppress contacts with custom properties through the API at production scale
weight 3 · round to BentoKitnone0/10The 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.
Docs confirm a Subscribers API supporting batch create/update (1-1000 per request) and an Events API for tracking activity and updating profile fields, plus filtering by tags/segment/date, which implies some custom-field handling. However there is no explicit documentation of a suppression/unsubscribe endpoint, no explicit mention of arbitrary custom properties support, and no OpenAPI spec or rate-limit/production-scale guarantees (openapi probe returned 404s). missing for 10: explicit suppression/unsubscribe API endpoint, explicit custom-properties schema support, documented rate limits or production-scale guarantees.
- [claimed-docs] “Request supports 1 to 1000 subscribers per post.”
- [claimed-docs] “Filter by tags, a segment, or by date ranges on creation, update, last event, and unsubscribe times.”
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [probe] “PROBE openapi: all candidate paths 404 (https://bentonow.com/openapi.json, https://bentonow.com/swagger.json, https://bentonow.com/api/opena…”
Api segments
developerCreate and update segments, tags, or lists programmatically and read back exactly who is in them
weight 3 · round to BentoKitnone0/10Evidence only shows that broadcasts can be targeted using existing segment or tag ids, implying some segmentation exists, but there is no documentation of API endpoints to create/update segments, tags, or lists, nor any evidence of reading back the exact subscriber membership of those groups.
- [claimed-docs] “We currently support targeting your subscribers based on segment or tag ids.”
- [claimed-docs] “If you are a third party developer, you can use the Kit API to link together or build on top of the Kit platform.”
Docs confirm subscriber API supports adding/updating tags and profile fields (bento-docs-1, bento-docs-4) and filtering/reading back subscribers by tag, segment, or date range (bento-docs-8), showing read/write access to tag membership. However, there's no explicit evidence of an API endpoint to programmatically create or update segment/list definitions themselves (segments appear to be built via filters/UI), and no OpenAPI spec was found to confirm full CRUD coverage (bento-probe-3). Missing for 10: explicit segment-creation/update API endpoint, documented list CRUD operations, and independent confirmation of read-back accuracy.
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [claimed-docs] “Import subscribers, find a record, or script the job you run every week.”
- [claimed-docs] “Filter by tags, a segment, or by date ranges on creation, update, last event, and unsubscribe times.”
- [probe] “PROBE openapi: all candidate paths 404 (https://bentonow.com/openapi.json, https://bentonow.com/swagger.json, https://bentonow.com/api/opena…”
Segment core
marketerBuild audience segments from profile attributes, tags, and behavioral events, and they stay live as data changes
weight 3 · round to BentoEvidence only shows broadcasts can target subscribers by 'segment or tag ids' (kit-docs-2), implying segments exist as a concept, but there's no documentation of building segments from profile attributes or behavioral events, nor confirmation that segments update live as data changes. Missing for 10: segment-builder documentation, behavioral-event triggers, and confirmation of live/dynamic recalculation of membership.
- [claimed-docs] “We currently support targeting your subscribers based on segment or tag ids.”
Docs show segmentation via tags, saved segments, and date-range filters on subscriber fields (bento-docs-8), combined with behavioral event tracking (bento-docs-1) and flows built from behavior/events/tags (bento-docs-9), which together enable dynamic, attribute+behavior-based audience segments. Missing for 10: explicit documentation stating segments automatically re-evaluate/update in real time as data changes, and independent/hands-on corroboration of live segment behavior.
- [claimed-docs] “Filter by tags, a segment, or by date ranges on creation, update, last event, and unsubscribe times.”
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [claimed-docs] “Build flows from behavior, events, and tags. Check every branch before it runs.”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to BentoKit's API/MCP lets users draft and send broadcasts to all or a segment/tag-based subset of subscribers, and the MCP overview shows natural-language prompts triggering such bulk actions, which is a form of bulk operation across many subscriber items. However, there's no evidence of broader bulk operations like batch subscriber import/export, bulk tagging/untagging, or bulk updates via API beyond broadcast targeting. Missing for 10: documented bulk subscriber CRUD/import-export endpoints, evidence of batch processing limits or throughput, and independent confirmation of bulk actions working via the MCP in practice.
- [claimed-docs] “Draft or schedule to send a broadcast to all or a subset of your subscribers.”
- [claimed-docs] “We currently support targeting your subscribers based on segment or tag ids.”
- [claimed-docs] “connect the Kit Developer Docs MCP. It queries the live docs so your agent stops working from a cached or hallucinated API surface.”
- [claimed-docs] “Natural-language prompts like “draft a broadcast to my new subscribers from this week” become real account actions.”
- [probe] “official MCP server documented at https://developers.kit.com/mcp/overview”
Bento's API explicitly supports batch operations on subscribers (1–1000 per request), bulk import, and filtering/segmenting for bulk targeting, and the MCP server exposes some of this to AI assistants. However, evidence doesn't show bulk operations beyond subscriber records (e.g., bulk broadcast sends, bulk event batch limits) or independent confirmation of scale/performance. Missing for 10: evidence of bulk operations across other object types (broadcasts, tags, flows), documented rate/size limits beyond subscribers, and independent/hands-on verification.
- [claimed-docs] “Request supports 1 to 1000 subscribers per post.”
- [claimed-docs] “Import subscribers, find a record, or script the job you run every week.”
- [claimed-docs] “Filter by tags, a segment, or by date ranges on creation, update, last event, and unsubscribe times.”
- [claimed-docs] “The Bento MCP server gives your AI assistant direct access to your Bento account. It can look up subscribers, create broadcasts, track event…”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to BentoKit's pricing page references 'Unlimited Visual Automations' (kit-docs-6), implying a rule/trigger-based automation builder typical of email platforms, but the evidence pack contains no documentation detailing specific triggers, conditions, or actions, nor any hands-on confirmation of how automations are configured or fire on events. Missing for 10: detailed docs on trigger/event types, action definitions, conditional logic, and independent verification of automation reliability.
- [claimed-docs] “Unlimited Visual Automations”
Bento supports building automation flows triggered by behavior, events, and tags, with branch validation before running ('Build flows from behavior, events, and tags. Check every branch before it runs.'), plus an Events API to track activity and trigger automations. Missing for 10: independent hands-on verification of rule complexity/reliability, and detailed documentation of conditional logic depth beyond marketing copy.
- [claimed-docs] “Build flows from behavior, events, and tags. Check every branch before it runs.”
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnKit supports scheduling one-time broadcasts and offers 'Unlimited Visual Automations' and RSS campaigns (which are inherently recurring), but there's no evidence of an AI-native (API/MCP) mechanism to schedule or manage recurring workflows—broadcast scheduling is single-send and automations are event-triggered rather than time-based recurring jobs. Missing for 10: explicit API/MCP support for recurring/cron-style workflow scheduling, documentation of recurring automation triggers, and independent confirmation these can be set up via AI-native tooling.
- [claimed-docs] “Draft or schedule to send a broadcast to all or a subset of your subscribers.”
- [claimed-docs] “Unlimited Visual Automations”
- [claimed-docs] “RSS campaigns”
- [claimed-docs] “Natural-language prompts like “draft a broadcast to my new subscribers from this week” become real account actions.”
Bento supports event/tag-triggered automation flows and scripting API jobs (e.g. 'script the job you run every week'), which implies some recurring automation capability, but there is no explicit documentation of a scheduler, cron-like recurring job configuration, or AI-driven scheduling of workflows. Missing for 10: explicit recurring/scheduled job feature, AI-native interface for setting schedules, and independent confirmation of time-based (not just event-based) automation triggers.
- [claimed-docs] “Import subscribers, find a record, or script the job you run every week.”
- [claimed-docs] “Build flows from behavior, events, and tags. Check every branch before it runs.”
ai-native userVersion, review, and roll back my automations
weight 1 · round drawnKitnone0/10No evidence Kit offers version history, review workflows, or rollback for automations/visual automations; docs mention only building automations and MCP-driven actions, not versioning or undo capabilities.
Campaign sending — stories about campaign sending in this arenaCampaign sending
Stories about campaign sending in this arena
Agent campaigns
ai-native userAn agent can draft a campaign against a segment and leave it scheduled or queued for a human to approve before send
weight 3 · round to KitKit's API and MCP let an agent draft or schedule a broadcast to a segment/tag (kit-docs-1, kit-docs-2, kit-docs-5), and drafts inherently sit unsent until a human acts, which functions as an approval gate. However, there is no explicit documentation of a formal 'queued for human approval' workflow or approval-status field distinct from draft/schedule. Missing for 10: explicit human-approval/review step or status beyond generic draft/schedule, and independent confirmation the MCP flow reliably leaves campaigns unsent pending approval.
- [claimed-docs] “Draft or schedule to send a broadcast to all or a subset of your subscribers.”
- [claimed-docs] “We currently support targeting your subscribers based on segment or tag ids.”
- [claimed-docs] “Natural-language prompts like “draft a broadcast to my new subscribers from this week” become real account actions.”
- [claimed-docs] “connect the Kit Developer Docs MCP. It queries the live docs so your agent stops working from a cached or hallucinated API surface.”
The MCP server can create broadcasts via natural language, implying a draft/queued campaign can be produced by an agent, but there is no documented approval/hold-for-human-review workflow or explicit 'scheduled pending approval' state before send. missing for 10: explicit approval-gating or human-review-before-send workflow, documentation of a queued/pending state distinct from immediate send, evidence of segment-targeted broadcast drafting via the agent.
- [claimed-docs] “The Bento MCP server gives your AI assistant direct access to your Bento account. It can look up subscribers, create broadcasts, track event…”
- [probe] “official MCP server documented at https://bentonow.com/docs/integrations/mcp”
- [claimed-docs] “Build flows from behavior, events, and tags. Check every branch before it runs.”
Api campaigns
developerCreate and schedule a campaign or broadcast entirely through a documented public API, without touching the dashboard
weight 3 · round to KitKit's public API docs explicitly support creating/drafting and scheduling broadcasts with targeting by segment/tag, directly enabling campaign creation without the dashboard. Missing for 10: an accessible OpenAPI/swagger spec (probe found 404s), independent developer confirmation of end-to-end scheduling success, and clarity on recurring/RSS campaign API support.
- [claimed-docs] “Draft or schedule to send a broadcast to all or a subset of your subscribers.”
- [claimed-docs] “We currently support targeting your subscribers based on segment or tag ids.”
- [claimed-docs] “If you are a third party developer, you can use the Kit API to link together or build on top of the Kit platform.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.kit.com/openapi.json, https://developers.kit.com/swagger.json, https://developers…”
Bentonone0/10Evidence documents APIs for events, subscribers, and transactional email, plus an MCP server that can 'create broadcasts' via AI assistant — but there is no documented public REST API endpoint for creating or scheduling campaigns/broadcasts, and OpenAPI spec probes returned 404s. Missing for 10: a documented broadcast/campaign creation and scheduling endpoint in the public API reference.
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [claimed-docs] “Transactional email is for messages a person needs because of an action, request, or account state: password resets, receipts, login codes, …”
- [claimed-docs] “The Bento MCP server gives your AI assistant direct access to your Bento account. It can look up subscribers, create broadcasts, track event…”
- [probe] “PROBE openapi: all candidate paths 404 (https://bentonow.com/openapi.json, https://bentonow.com/swagger.json, https://bentonow.com/api/opena…”
Campaign core
marketerCompose an email campaign, pick its audience, and send or schedule it — the arena's table-stakes loop
weight 3 · round to KitKit's API docs confirm drafting/scheduling a broadcast (send/schedule) with audience targeting by segment or tag (kit-docs-1, kit-docs-2), covering the core compose-audience-send/schedule loop, and this is corroborated by the product's broader marketing platform positioning (kit-docs-14, kit-docs-15). missing for 10: independent hands-on user account of composing and sending a real campaign via the UI, and detail on scheduling UI/preview features beyond the API reference.
- [claimed-docs] “Draft or schedule to send a broadcast to all or a subset of your subscribers.”
- [claimed-docs] “We currently support targeting your subscribers based on segment or tag ids.”
- [claimed-docs] “Get more subscribers with landing pages, forms, and creator recommendations.”
Evidence confirms subscriber segmentation (tags/segments/date filters) and broadcast creation (including via MCP), which are core pieces of the campaign-sending loop, but there is no direct documentation of the actual campaign composition UI or a 'schedule send' feature. Missing for 10: explicit docs/screenshots of composing an email campaign, choosing send-now vs schedule-for-later, and confirmation of the full end-to-end send flow.
- [claimed-docs] “Request supports 1 to 1000 subscribers per post.”
- [claimed-docs] “Filter by tags, a segment, or by date ranges on creation, update, last event, and unsubscribe times.”
- [claimed-docs] “The Bento MCP server gives your AI assistant direct access to your Bento account. It can look up subscribers, create broadcasts, track event…”
- [claimed-docs] “Build flows from behavior, events, and tags. Check every branch before it runs.”
Experiments
marketerA/B test subject lines or content variants and have the winner picked from real engagement
weight 2 · round to KitKit's pricing page lists "A/B test subject lines & content" as a feature [kit-docs-7], confirming the capability exists, but there's no documentation describing how winners are determined from engagement data (e.g., automatic winner selection, sample size, or evaluation window). Missing for 10: documentation on automatic winner-selection logic/criteria, evidence of engagement-based decisioning, and any hands-on or independent confirmation the feature works as described.
- [claimed-docs] “A/B test subject lines & content”
Deliverability domains — stories about deliverability domains in this arenaDeliverability domains
Stories about deliverability domains in this arena
Deliverability signals
marketerSee bounce, complaint, and blocklist signals per send and get actionable guidance when deliverability degrades
weight 2 · round drawnKitnone0/10No evidence in the pack mentions bounce, complaint, or blocklist tracking, deliverability metrics, or actionable guidance for degraded sending reputation; the documentation covers broadcasts, pricing features, and MCP/API tooling but nothing about deliverability signal reporting.
Bentonone0/10The evidence pack shows subscriber/event tracking, dedicated IPs, and general email automation features, but there is no mention of per-send bounce/complaint/blocklist reporting or deliverability health guidance. missing for 10: bounce/complaint/blocklist reporting per send, deliverability health dashboard, actionable degradation alerts/guidance.
- [claimed-docs] “Dedicated IP address options for high-volume senders”
- [claimed-docs] “Request supports 1 to 1000 subscribers per post.”
- [claimed-docs] “Filter by tags, a segment, or by date ranges on creation, update, last event, and unsubscribe times.”
Domain auth
ops userAuthenticate my own sending domain — SPF, DKIM, DMARC alignment — with guided DNS setup and verification
weight 3 · round drawnKitnone0/10No 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.
Bentonone0/10The evidence pack contains no mention of SPF/DKIM/DMARC domain authentication, guided DNS setup, or verification flows — only unrelated features like dedicated IPs, transactional email, and subscriber management. Domain authentication is a standard, fair-to-expect capability for an email marketing platform, so its absence is 'none' rather than 'na'. missing for 10: any documentation of SPF/DKIM/DMARC setup, DNS record guidance, or domain verification UI.
- [claimed-docs] “Dedicated IP address options for high-volume senders”
Suppression
ops userUnsubscribes, bounces, and spam complaints are suppressed automatically and honored across every send type — CAN-SPAM/GDPR hygiene by default
weight 3 · round drawnKitnone0/10No evidence pack items mention unsubscribe suppression, bounce handling, spam complaint suppression, or automatic CAN-SPAM/GDPR compliance across send types; the pack only covers broadcast creation, MCP/API access, and pricing features unrelated to suppression hygiene.
Integrations webhooks — stories about integrations webhooks in this arenaIntegrations webhooks
Stories about integrations webhooks in this arena
First party integrations
ops userConnect the platform to my existing stack — Stripe or Shopify, a CDP like Segment, my product database — with maintained first-party integrations
weight 2 · round drawnKitnone0/10Evidence only shows a generic marketing line about connecting 'creator tools' via apps (kit-docs-15) and a general third-party API note (kit-docs-3); there is no mention of specific maintained first-party integrations with Stripe, Shopify, Segment/CDPs, or product databases anywhere in the pack.
- [claimed-docs] “Automate your work with apps that connect your creator tools directly to Kit.”
- [claimed-docs] “If you are a third party developer, you can use the Kit API to link together or build on top of the Kit platform.”
Bentonone0/10The evidence pack shows generic Events/Subscribers APIs, an MCP server, and marketing copy, but no mention of maintained first-party integrations with Stripe, Shopify, Segment, or a product database — nothing names a specific connector or integrations marketplace.
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [claimed-docs] “Import subscribers, find a record, or script the job you run every week.”
- [probe] “PROBE docs-md: HTTP 200 at https://bentonow.com/docs.md # Bento Documentation Complete documentation for Bento email marketing platform. AP…”
Webhooks
developerSubscribe webhooks to delivery and engagement events — sends, opens, clicks, bounces, unsubscribes — with a documented, signed payload
weight 3 · round drawnKitnone0/10No evidence in the pack mentions webhooks, signed payloads, or event subscriptions (sends, opens, clicks, bounces, unsubscribes); the docs cover broadcasts, MCP, and pricing features unrelated to webhook delivery. missing for 10: any documentation of webhook subscription endpoints, event types, or payload signing/verification.
Bentonone0/10No evidence pack item documents an outbound webhooks feature for delivery/engagement events (sends, opens, clicks, bounces, unsubscribes) with signed payloads; the closest items reference an inbound Events API for tracking user activity, not outbound webhook subscriptions. OpenAPI/spec probes turned up nothing, and no webhook-specific docs appear anywhere in the pack.
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [probe] “PROBE openapi: all candidate paths 404 (https://bentonow.com/openapi.json, https://bentonow.com/swagger.json, https://bentonow.com/api/opena…”
Lifecycle automation — stories about lifecycle automation in this arenaLifecycle automation
Stories about lifecycle automation in this arena
Automation core
marketerBuild multi-step lifecycle automations — welcome series, onboarding, winback — with branches, delays, and exit rules
weight 3 · round to BentoKit's pricing page confirms a visual automation builder ("Unlimited Visual Automations") exists, which is consistent with the story's need for lifecycle automations, but the evidence pack contains no documentation detailing branch logic, delay steps, or exit-rule configuration, nor examples of welcome/onboarding/winback templates. Missing for 10: docs on branching logic, delay/wait steps, exit-rule conditions, and concrete welcome/onboarding/winback automation examples.
- [claimed-docs] “Unlimited Visual Automations”
Docs confirm flow-building based on behavior, events, and tags with branch checking (bento-docs-9) and event/activity tracking to trigger automations (bento-docs-1), supporting core lifecycle automation building blocks, but there is no explicit documentation of delays, timed waits, or exit rules, nor named templates like welcome/onboarding/winback series. missing for 10: explicit delay/wait-step documentation, explicit exit-rule/goal documentation, named use-case templates (welcome, onboarding, winback), independent hands-on corroboration.
- [claimed-docs] “Build flows from behavior, events, and tags. Check every branch before it runs.”
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [claimed-docs] “Tie sales and recurring revenue back to the email or flow that came before.”
Event triggers
developerFire a custom event from my product and have it trigger an automation for exactly that person
weight 3 · round to BentoKitnone0/10The 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. This is a plausible axis for an email/lifecycle automation platform, but no evidence supports it here.
Docs confirm an Events API that tracks user activity per subscriber and can trigger automations, and flows explicitly built from 'behavior, events, and tags' with per-branch checks, matching the story of firing a custom event to trigger an automation for a specific person. missing for 10: no hands-on/independent confirmation of exact event-to-person targeting behavior, and no code sample showing the custom event payload triggering a single-subscriber automation.
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [claimed-docs] “Build flows from behavior, events, and tags. Check every branch before it runs.”
Flow operations
ops userSee where any individual person sits inside an automation and pull or re-enter them without breaking the flow
weight 2 · round drawnKitnone0/10Evidence only mentions 'Unlimited Visual Automations' as a pricing line item, with no documentation of subscriber-level visibility into automation steps or the ability to pull/re-enter an individual subscriber without disrupting the automation. Missing for 10: any docs on per-subscriber automation position view, manual add/remove-from-automation actions, and confirmation that re-entry doesn't break flow state.
- [claimed-docs] “Unlimited Visual Automations”
Bentonone0/10Evidence only shows generic flow-building and event/segment filtering (bento-docs-9, bento-docs-8) but nothing about viewing an individual subscriber's current position inside a running automation or safely pulling/re-entering them without breaking the flow.
- [claimed-docs] “Build flows from behavior, events, and tags. Check every branch before it runs.”
- [claimed-docs] “Filter by tags, a segment, or by date ranges on creation, update, last event, and unsubscribe times.”
List portability — stories about list portability in this arenaList portability
Stories about list portability in this arena
Export
founderExport my entire audience — contacts, custom fields, tags, engagement history, and suppression list — in an open format, self-serve
weight 3 · round to BentoKitnone0/10The 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.
Bento's docs mention a Subscribers API that can filter by tags, segments, and dates and can be scripted to run exports (bento-docs-2, bento-docs-4, bento-docs-8), implying some self-serve data extraction is possible via API, but there is no explicit documentation of a full audience export covering suppression list, full engagement history, or a one-click open-format (CSV/JSON) export tool. Missing for 10: documented bulk export/download feature, explicit suppression list export, engagement history export, and confirmation of an open standard export format.
- [claimed-docs] “Request supports 1 to 1000 subscribers per post.”
- [claimed-docs] “Import subscribers, find a record, or script the job you run every week.”
- [claimed-docs] “Filter by tags, a segment, or by date ranges on creation, update, last event, and unsubscribe times.”
Import migration
marketerMigrate in from another email platform with guided list import that preserves tags, custom fields, and unsubscribe state
weight 2 · round to BentoKitnone0/10The only relevant evidence is a single marketing line mentioning 'Free migrations' on the pricing page, with no documentation of guided list import, tag/custom-field preservation, or unsubscribe-state handling. missing for 10: any docs on import tooling, evidence tags/custom fields are preserved, evidence unsubscribe status is preserved, guided/step-by-step migration flow.
- [claimed-docs] “14-day free trial. No credit card required. Free migrations.”
Bento documents subscriber import (bulk import, 1-1000 per request), filtering by tags/segments and unsubscribe timestamps, and explicitly lists 'Migration help when you switch' on its pricing page plus testimonials of users moving from Mailchimp/Hubspot. However there is no dedicated guided-migration wizard or documentation detailing how custom fields and unsubscribe state are specifically preserved during a platform switch. Missing for 10: a documented step-by-step migration/import wizard, explicit confirmation that unsubscribe status and custom fields are mapped/preserved on import, and independent evidence of successful full-data migrations.
- [claimed-docs] “Import subscribers, find a record, or script the job you run every week.”
- [claimed-docs] “Filter by tags, a segment, or by date ranges on creation, update, last event, and unsubscribe times.”
- [claimed-docs] “Migration help when you switch”
- [claimed-docs] “Moved to Bento from Hubspot and never looked back!”
- [community] “I started out on MailChimp, but recently switched to Bento (bentonow.com). I really like it.”
Marketing data access — stories about marketing data access in this arenaMarketing data access
Stories about marketing data access in this arena
Agent access
ai-native userAn agent can pull my whole email program — audiences, live automations, recent campaign results — programmatically and report on what's working
weight 2 · round to BentoKit has a documented API and an official MCP server that can query live docs and turn natural-language prompts into account actions (e.g., drafting broadcasts), showing programmatic access exists. However, the evidence pack lacks any documentation of endpoints for pulling subscriber/audience lists, automation status, or campaign performance/reporting data — the core of 'report on what's working'. Missing for 10: audience/segment retrieval endpoints, automation status/reporting API, campaign analytics endpoints, and any example of an agent synthesizing a performance report.
- [claimed-docs] “Draft or schedule to send a broadcast to all or a subset of your subscribers.”
- [claimed-docs] “We currently support targeting your subscribers based on segment or tag ids.”
- [claimed-docs] “If you are a third party developer, you can use the Kit API to link together or build on top of the Kit platform.”
- [claimed-docs] “connect the Kit Developer Docs MCP. It queries the live docs so your agent stops working from a cached or hallucinated API surface.”
- [claimed-docs] “Natural-language prompts like “draft a broadcast to my new subscribers from this week” become real account actions.”
- [probe] “official MCP server documented at https://developers.kit.com/mcp/overview”
Bento ships an official MCP server plus REST APIs (events, subscribers) that let an AI assistant look up subscribers, create broadcasts, and track events 'through natural conversation,' which supports programmatic access to audiences and automations triggers. However, there is no direct evidence of an API/MCP capability for pulling campaign performance metrics or automation run reports (the closest is generic revenue-attribution copy), so full 'report on what's working' analytics access isn't demonstrated. Missing for 10: explicit API/MCP endpoints for campaign/broadcast analytics or automation performance reporting, and independent confirmation of MCP reliability for this reporting use case.
- [claimed-docs] “The Bento MCP server gives your AI assistant direct access to your Bento account. It can look up subscribers, create broadcasts, track event…”
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [claimed-docs] “Request supports 1 to 1000 subscribers per post.”
- [claimed-docs] “Build flows from behavior, events, and tags. Check every branch before it runs.”
- [claimed-docs] “Tie sales and recurring revenue back to the email or flow that came before.”
- [probe] “official MCP server documented at https://bentonow.com/docs/integrations/mcp”
Api access
developerRead per-person engagement history — what was sent, opened, clicked — through the API for any contact
weight 3 · round drawnKitnone0/10Evidence 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. Subscriber engagement scoring is mentioned only as a pricing feature name, not an API capability.
- [claimed-docs] “Subscriber engagement scoring”
- [claimed-docs] “Draft or schedule to send a broadcast to all or a subset of your subscribers.”
- [claimed-docs] “We currently support targeting your subscribers based on segment or tag ids.”
Bentonone0/10Evidence covers Bento's Events API (tracking activity, updating fields, triggering automations) and Subscribers API filters (tags, segments, last-event/date ranges), but nothing documents a way to retrieve per-contact history of what was sent, opened, and clicked via the API. No endpoint or field for message-level engagement history is described.
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [claimed-docs] “Filter by tags, a segment, or by date ranges on creation, update, last event, and unsubscribe times.”
Scoped access
ops userMint scoped or read-only API credentials so an agent or contractor can read analytics without the power to send
weight 2 · round drawnKitnone0/10No evidence of scoped or read-only API key/credential creation in Kit's docs; the evidence pack shows general API access, MCP integration, and pricing features but nothing about granular permission scoping or read-only tokens for third parties/agents.
Bentonone0/10No evidence of scoped or read-only API key/credential management in Bento's docs; API references only cover events, subscribers, and transactional email without mention of permission levels or credential scoping for third parties like contractors or agents.
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [claimed-docs] “Request supports 1 to 1000 subscribers per post.”
- [claimed-docs] “Import subscribers, find a record, or script the job you run every week.”
- [probe] “PROBE openapi: all candidate paths 404 (https://bentonow.com/openapi.json, https://bentonow.com/swagger.json, https://bentonow.com/api/opena…”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round drawnKit's docs show a real API and MCP layer that can create/schedule broadcasts and let agents take 'real account actions,' plus a llms.txt manifest, showing meaningful API parity ambition. But no OpenAPI spec is discoverable (404s across expected paths) and there is no evidence the API covers major UI-only features like landing pages/forms, visual automations, digital product sales, or A/B testing — so full UI-API parity is unconfirmed. Missing for 10: documented API coverage for landing pages/forms/commerce/automations, a public OpenAPI/schema reference, and independent confirmation of parity.
- [claimed-docs] “Draft or schedule to send a broadcast to all or a subset of your subscribers.”
- [claimed-docs] “If you are a third party developer, you can use the Kit API to link together or build on top of the Kit platform.”
- [claimed-docs] “connect the Kit Developer Docs MCP. It queries the live docs so your agent stops working from a cached or hallucinated API surface.”
- [claimed-docs] “Natural-language prompts like “draft a broadcast to my new subscribers from this week” become real account actions.”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.kit.com/llms.txt # Kit Developer Documentation - [Welcome](https://developers.kit.com/welcom…”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.kit.com/openapi.json, https://developers.kit.com/swagger.json, https://developers…”
Bento's docs show a broad API/events/subscribers/transactional-email surface (bento-docs-1,2,3,8) and an MCP server exposing subscriber lookup, broadcast creation, and event tracking via natural language (bento-docs-5, bento-probe-4), suggesting substantial API parity with the UI. However, no public OpenAPI/swagger spec was found (bento-probe-3), and UI-only features like AI-driven flow building from plain text (bento-docs-10) and flow branch testing (bento-docs-9) aren't shown as API-accessible. Missing for 10: a full OpenAPI reference, explicit API endpoints for flow/automation creation and testing, and confirmation that all UI actions (flows, broadcasts, deliverability settings) have API equivalents.
- [claimed-docs] “Track user activity, update profile fields, and trigger automations.”
- [claimed-docs] “Request supports 1 to 1000 subscribers per post.”
- [claimed-docs] “Transactional email is for messages a person needs because of an action, request, or account state: password resets, receipts, login codes, …”
- [claimed-docs] “The Bento MCP server gives your AI assistant direct access to your Bento account. It can look up subscribers, create broadcasts, track event…”
- [claimed-docs] “Filter by tags, a segment, or by date ranges on creation, update, last event, and unsubscribe times.”
- [claimed-docs] “Build flows from behavior, events, and tags. Check every branch before it runs.”
- [claimed-docs] “Describe what you want in plain text and let Bento's powerful AI build it for you.”
- [probe] “PROBE openapi: all candidate paths 404 (https://bentonow.com/openapi.json, https://bentonow.com/swagger.json, https://bentonow.com/api/opena…”
- [probe] “official MCP server documented at https://bentonow.com/docs/integrations/mcp”
ai-native userExport all of my data in open formats and leave
weight 3 · round to BentoKitnone0/10No 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. Data portability is a fair axis for a SaaS platform, but nothing shows Kit actually supports full open-format export.
- [claimed-docs] “14-day free trial. No credit card required. Free migrations.”
Bento offers a subscribers API for querying/importing records and mentions 'migration help when you switch,' implying some data portability, but there is no explicit documentation of a full data export feature or open-format (CSV/JSON) bulk export for all account data. missing for 10: explicit bulk export endpoint/tool, documented open export formats, and independent confirmation that a full account export is possible.
- [claimed-docs] “Import subscribers, find a record, or script the job you run every week.”
- [claimed-docs] “Filter by tags, a segment, or by date ranges on creation, update, last event, and unsubscribe times.”
- [claimed-docs] “Migration help when you switch”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnKitnone0/10No evidence in the pack mentions data residency, regional storage options, or any data-location controls for Kit.
Bentonone0/10No evidence in the pack mentions data residency, region selection, or storage location options for Bento; the only infrastructure-related item is a dedicated IP address feature for sending, unrelated to data residency. missing for 10: any mention of regional data hosting, residency guarantees, or data storage location controls.
- [claimed-docs] “Dedicated IP address options for high-volume senders”
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnKitnone0/10No evidence in the pack addresses AI-training data opt-out or a privacy policy governing use of user/subscriber data for model training; all evidence concerns email marketing features, MCP/API docs, and business history.
ai-native userControl data retention and deletion
weight 2 · round drawnKitnone0/10No evidence pack items address data retention policies, deletion controls, or privacy/data-export mechanisms for AI-native usage; all evidence concerns broadcast features, pricing tiers, and MCP integration.
Bentonone0/10No evidence pack items describe data retention policies, subscriber deletion/export controls, or privacy/GDPR compliance tooling; the docs focus on subscriber import/filtering/automation, not on how AI-native users can control or delete stored data. Missing for 10: documented data deletion/export APIs, retention policy settings, GDPR/CCPA compliance statements.
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnKitnone0/10No evidence pack items mention telemetry, usage tracking, or opt-out controls for Kit's MCP server, API, or product; the evidence covers unrelated features like broadcasts, pricing, and MCP docs access.
Bentonone0/10No evidence in the pack addresses telemetry/usage-tracking opt-out for Bento itself (as opposed to its email/marketing tracking features for end customers); this is a fair privacy-posture question for any AI-native tool but no documentation or community evidence confirms such a control exists.
Template content — stories about template content in this arenaTemplate content
Stories about template content in this arena
Ai content
marketerHave the platform's built-in AI draft or refine subject lines and email copy from a brief, inside the composer
weight 2 · round drawnKitnone0/10Evidence shows Kit's API/MCP can create or draft broadcasts programmatically and offers A/B testing of subject lines, but there is no mention of an in-composer AI assistant that drafts or refines subject lines/email copy from a marketer's brief inside the editor itself.
- [claimed-docs] “Draft or schedule to send a broadcast to all or a subset of your subscribers.”
- [claimed-docs] “A/B test subject lines & content”
- [claimed-docs] “Natural-language prompts like “draft a broadcast to my new subscribers from this week” become real account actions.”
Bentonone0/10The only AI-related claim (bento-docs-10) is generic ('let Bento's powerful AI build it for you') and appears tied to flow/segment building, not to drafting or refining subject lines and email copy inside a composer. No evidence describes an AI copywriting assistant for email content.
- [claimed-docs] “Describe what you want in plain text and let Bento's powerful AI build it for you.”
Editor
marketerDesign on-brand emails with a visual editor, reusable templates, and personalization tokens that render correctly across clients
weight 2 · round drawnKitnone0/10The evidence pack covers broadcast API, MCP integration, and pricing feature bullets (automations, A/B testing, collaborative editing) but contains no mention of a visual email editor, reusable templates, or personalization token rendering across email clients. Since this is a core capability marketers would expect from an email platform, the axis clearly applies, but no supporting evidence exists in the pack.
Bentonone0/10The evidence pack covers transactional email, subscriber/segment management, flows/automations, and an MCP integration, but contains no mention of a visual email editor, reusable templates, personalization tokens, or cross-client rendering testing — all core to this story for an email marketing platform.
Templates as code
developerManage email templates as code — HTML/MJML or API-managed templates with variable substitution — under version control
weight 2 · round drawnKitnone0/10No evidence of HTML/MJML template files, template-as-code storage, or version-control support for email templates; evidence only covers broadcast creation API, pricing features, and MCP docs tooling.
Transactional sending — stories about transactional sending in this arenaTransactional sending
Stories about transactional sending in this arena
Transactional api
developerSend one-to-one transactional email — receipts, magic links, notifications — through the same platform's API alongside marketing sends
weight 3 · round to BentoKitnone0/10Evidence shows Kit's API only supports broadcast/campaign sends to subscriber segments or tags (kit-docs-1, kit-docs-2), with no mention of a transactional API for one-to-one sends like receipts or magic links. The axis is fair to ask of an email-sending platform, but nothing in the pack indicates this capability exists.
- [claimed-docs] “Draft or schedule to send a broadcast to all or a subset of your subscribers.”
- [claimed-docs] “We currently support targeting your subscribers based on segment or tag ids.”
Bento's docs explicitly describe a dedicated transactional email feature for one-to-one messages like password resets, receipts, login codes, and order confirmations, sent via the same platform used for marketing, and note dedicated IP options for high-volume senders. Missing for 10: explicit confirmation this uses the same unified API endpoint as marketing sends, and independent/hands-on corroboration of transactional delivery in practice.
- [claimed-docs] “Transactional email is for messages a person needs because of an action, request, or account state: password resets, receipts, login codes, …”
- [claimed-docs] “Dedicated IP address options for high-volume senders”
Transactional hygiene
ops userTransactional email is kept separate from marketing — its own templates, suppression rules, and reputation — so a receipt still delivers to an unsubscribed contact
weight 2 · round to BentoKitnone0/10Kit is positioned as a creator/newsletter marketing platform (broadcasts, automations, landing pages) with no evidence of a distinct transactional-sending system, templates, or suppression-list separation from marketing sends. Nothing in the evidence pack addresses transactional email, receipts, or reputation isolation.
Bento explicitly documents transactional email as a distinct category (password resets, receipts, order confirmations) separate from marketing sends, and mentions dedicated IP options for high-volume senders. However, there is no explicit documentation confirming that suppression/unsubscribe rules are bypassed for transactional messages, that transactional templates are managed separately from marketing templates, or that transactional sending reputation/IP is isolated from marketing reputation. Missing for 10: explicit suppression-list bypass behavior for transactional sends, dedicated transactional template system, and documented separate sending reputation/domain infrastructure.
- [claimed-docs] “Transactional email is for messages a person needs because of an action, request, or account state: password resets, receipts, login codes, …”
- [claimed-docs] “Dedicated IP address options for high-volume senders”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableKitn/aKit is a SaaS email-marketing platform, not an AI agent capable of consuming external MCP servers as tools. The evidence only shows Kit exposing its own MCP server for others (like coding agents) to connect to and use Kit's API, which is the opposite direction from this story's ask.
- [claimed-docs] “connect the Kit Developer Docs MCP. It queries the live docs so your agent stops working from a cached or hallucinated API surface.”
- [probe] “official MCP server documented at https://developers.kit.com/mcp/overview”
Bentonone0/10Evidence only shows Bento exposes its own MCP server so external AI assistants can call Bento's tools (bento-docs-5, bento-probe-4) — the reverse of what this story asks. There is no evidence Bento itself can act as an MCP client and plug in external MCP servers to use their tools.
- [claimed-docs] “The Bento MCP server gives your AI assistant direct access to your Bento account. It can look up subscribers, create broadcasts, track event…”
- [probe] “official MCP server documented at https://bentonow.com/docs/integrations/mcp”
ai-native userRead the product's source under an open license
weight 2 · not comparableKitn/aKit is a closed-source SaaS email marketing/creator platform; there is no indication its core product source is open at all, and reading proprietary SaaS source code isn't a fair axis for this product category.
ai-native userSelf-host the core product
weight 3 · not comparableKitn/aKit is a SaaS email marketing/creator platform with no self-hosted deployment option evidenced anywhere; self-hosting is not a fair axis for a hosted SaaS product with proprietary pricing tiers and no open-source core.