Loops vs Bento
Bento wins · 15–16 (25 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 drawnLoops has a live, probe-confirmed llms.txt (loops-probe-1) with dedicated agent-oriented docs at /agents and /agents/api, plus an OpenAPI spec (loops-probe-3) and MCP server for agent connectivity (loops-docs-6, loops-probe-4). Missing for 10: independent hands-on confirmation that an agent successfully consumes llms.txt end-to-end rather than just server availability.
- [probe] “PROBE llms.txt: HTTP 200 at https://loops.so/llms.txt # Loops > Loops is an email platform for software companies. Send transactional and m…”
- [claimed-docs] “Author campaigns in code with the Content API and keep editing visually in Loops.”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://loops.so/agents/mcp”
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 to LoopsLoops exposes a REST API with Bearer-token auth, an OpenAPI spec, and a CLI for terminal-based contact/event/email management, which supports scripted/CI usage. However, evidence doesn't explicitly confirm a headless automation workflow (e.g., CI pipeline examples, non-interactive auth for automation, or documented CI recipes) beyond API/CLI existence. Missing for 10: explicit CI/CD examples or automation-pipeline documentation, evidence of non-interactive/service-account auth flow, and independent confirmation of headless use in production automation.
- [claimed-docs] “add an Authorization header and set the API key as a Bearer token”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Manage contacts, send events, and test transactional email from your terminal”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
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 drawnLoops documents an official MCP server ('Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.') with a dedicated docs page, backed by a first-party API and CLI/skills for agent integration. Missing for 10: independent/hands-on verification of the MCP server working end-to-end and more detail on setup/auth for MCP specifically.
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [probe] “official MCP server documented at https://loops.so/agents/mcp”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
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 to LoopsLoops documents an official CLI ('Manage contacts, send events, and test transactional email from your terminal' and 'Install the CLI and skills with one command so your coding agent can use Loops for you'), explicitly positioned for AI-native/agentic workflows. Missing for 10: independent hands-on verification of the CLI's functionality and no detailed command reference in the evidence pack.
- [claimed-docs] “Manage contacts, send events, and test transactional email from your terminal”
- [claimed-docs] “Install the CLI and skills with one command so your coding agent can use Loops for you.”
ai-native userDrive the product through a documented public API
weight 3 · round to LoopsLoops provides a documented public REST API with authentication (Bearer token), endpoints for events, contacts, campaigns, and email sending, plus an OpenAPI spec (confirmed live at /openapi.json) and SDKs/CLI for programmatic access. This clearly enables an AI-native user to drive the product entirely via API. Missing for 10: independent third-party developer corroboration of API robustness/versioning in practice beyond founder claims.
- [claimed-docs] “add an Authorization header and set the API key as a Bearer token”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Add Loops to your application in minutes with our SDKs.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
- [claimed-docs] “Author campaigns in code with the Content API and keep editing visually in Loops.”
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 drawnLoopsnone0/10Evidence shows a single Bearer-token API key auth model with no mention of scoped, restricted-permission, or per-agent credentials — only a full-access API key pattern is documented across docs, MCP, and CLI. No evidence of least-privilege or scoped token issuance.
- [claimed-docs] “add an Authorization header and set the API key as a Bearer token”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
ai-native userBuild against official SDKs
weight 2 · round to LoopsLoops documents official SDKs plus a REST API with Bearer auth, an OpenAPI spec, and a CLI/skills installer for coding agents, indicating strong AI-native SDK support beyond just docs. missing for 10: independent hands-on developer confirmation of SDK reliability/coverage across languages, and no explicit list of supported languages beyond generic 'SDKs' mention.
- [claimed-docs] “add an Authorization header and set the API key as a Bearer token”
- [claimed-docs] “Add Loops to your application in minutes with our SDKs.”
- [claimed-docs] “Install the CLI and skills with one command so your coding agent can use Loops for you.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
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 drawnLoopsnone0/10Evidence shows Loops lets users send events INTO Loops (POST /events/send) and use APIs/MCP/CLI to manage contacts and campaigns, but there is no mention of Loops emitting outbound webhooks that a user's system could subscribe to for platform events (e.g., opens, bounces, unsubscribes). Missing for 10: any documentation of a webhook subscription/callback mechanism, webhook payload schema, or webhook management endpoint.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
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 to BentoLoopsnone0/10Loops documents analytics/segmentation (loops-docs-16), campaign drafting via API, and an email 'Guardian' check (loops-docs-19), but none of this evidence describes AI-generated insights or suggestions derived from a customer's data (e.g., predictive recommendations, anomaly detection, or AI-surfaced trends). The agent/API/MCP features are about enabling external agents to act on Loops, not the product itself surfacing AI insights.
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
- [claimed-docs] “Run Guardian checks on an email message”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
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 BentoLoops supports event-triggered workflows (POST /events/send triggers workflows) and lifecycle automations (onboarding, activation, upgrade, winback emails) that are 'set up once' and run autonomously over time, which is the core of background automation for an email/lifecycle platform. Missing for 10: detailed documentation of workflow logic (branching, delays, conditions), and independent/hands-on corroboration that these automations reliably run unattended long-term.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “Reach users after they close the tab. Set up onboarding, activation, upgrade, and winback emails once, then improve them over time.”
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
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 BentoLoopsnone0/10Loops' 'agents' materials describe APIs/MCP/CLI/skills that let external coding agents (Claude, Cursor, etc.) act on Loops on the user's behalf — this is Loops being consumed by an agent, not a built-in AI assistant living inside the Loops product that a user delegates tasks to. No evidence of an in-app assistant (e.g., an AI chat/copilot embedded in the Loops dashboard) exists in the pack.
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [claimed-docs] “Install the CLI and skills with one command so your coding agent can use Loops for you.”
- [claimed-docs] “I scanned your codebase and found every send, template, and webhook. Each one maps to a Loops equivalent, so I swapped the API calls and reb…”
- [probe] “official MCP server documented at https://loops.so/agents/mcp”
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 to BentoLoops provides an MCP server and CLI/skills that let an AI agent operate Loops via natural-language-driven tool calls (create contacts, send events, draft campaigns, run Guardian checks) rather than requiring manual API scripting, which supports agentic/natural-language operation. However, the evidence is all vendor docs describing agent-facing surfaces (MCP, CLI, API) rather than a chat/NL command interface for end-users themselves, and there's no independent/hands-on confirmation of how well natural-language control actually works. Missing for 10: independent verification of natural-language command execution, evidence of an end-user-facing NL/chat interface (not just agent APIs/MCP), and confirmation of reliability/quality of agent-driven actions in practice.
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [claimed-docs] “Install the CLI and skills with one command so your coding agent can use Loops for you.”
- [claimed-docs] “Run Guardian checks on an email message”
- [probe] “official MCP server documented at https://loops.so/agents/mcp”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
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 to LoopsLoops documents API endpoints (contacts, events, Guardian checks) and exposes a valid openapi.json spec, suggesting a structured API reference exists, but there's no evidence of an interactive 'try it now' console or runnable code examples within the docs themselves. Missing for 10: explicit interactive/try-it API console, runnable code snippets in docs, independent confirmation of the reference UI's interactivity.
- [claimed-docs] “add an Authorization header and set the API key as a Bearer token”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Run Guardian checks on an email message”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
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 to LoopsA probe confirms a valid OpenAPI spec is served at https://loops.so/openapi.json (contains an 'openapi' key, HTTP 200), and this is complemented by full API reference docs. Missing for 10: independent third-party confirmation that the spec is complete/versioned or widely used by external tooling.
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
- [claimed-docs] “add an Authorization header and set the API key as a Bearer token”
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 drawnLoopsnone0/10No evidence of a sandbox/test environment, test API keys, or staging mode separate from production data; docs cover API auth, SDKs, MCP, and migration guides but nothing about sandboxing. Missing for 10: dedicated sandbox/test-mode environment, test API keys or data isolation guarantees, documentation of a non-production testing workflow.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round to LoopsA founder comment mentions the API has versioning ('performant API with versioning for transactional email') and an OpenAPI spec is exposed, but there is no documented deprecation policy, version lifecycle, or migration guidance anywhere in the evidence. Missing for 10: documented deprecation/sunset policy, versioning scheme details, migration guides between API versions.
- [community] “Founder describes Loops' approach: simplified pricing (no tables, one metric), performant API with versioning for transactional email, text-…”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
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 drawnLoopsnone0/10Evidence covers API endpoints for creating contacts, sending events, drafting campaign content, and MCP integration, but nothing documents an endpoint for retrieving campaign or flow performance metrics (opens, clicks, conversions, revenue) via API for warehousing or BI use. The analytics mentioned (e.g., 'see which emails lead to upgrades') appear to be dashboard-only features, not exposed via API.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Create draft campaigns, content and all, straight from the API. Review and send from the dashboard.”
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
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 BentoLoops explicitly markets seeing 'which emails lead to upgrades, lower churn, and add revenue' with dynamic segments, suggesting some revenue/conversion attribution beyond opens/clicks, but this is a single marketing-page claim with no detail on methodology, dashboards, or per-flow attribution granularity, and no independent or hands-on corroboration exists in the evidence pack. Missing for 10: detailed docs on how revenue/signup attribution is computed, screenshots or hands-on reports of attribution reporting, and third-party validation.
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
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 BentoLoopsnone0/10Evidence covers Loops' API, SDKs, CLI, MCP, and migration tooling, plus a generic mention of segmentation revenue impact, but there is no documentation of an analytics dashboard or API reporting opens, clicks, unsubscribes, and conversions per campaign or per automation step over time. Missing for 10: any analytics/reporting endpoint or dashboard docs showing per-campaign/per-step metrics, time-series breakdowns, or conversion attribution.
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
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 drawnLoopsnone0/10While Loops exposes API endpoints for contacts, events, and campaign content (loops-docs-3, loops-docs-4, loops-docs-6), and mentions segments only as a dashboard feature that stays dynamic (loops-docs-16), there is no documented endpoint or MCP tool for creating or defining an audience segment programmatically from a natural-language description. No evidence shows an agent can translate plain-language criteria into a real segment via the API or MCP surface.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
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 BentoEvidence confirms a REST API with bearer-token auth and a POST /contacts/create endpoint plus an OpenAPI spec, and dynamic segment properties are mentioned, implying custom contact properties exist. However, there is no explicit documentation of contact update or suppression endpoints, nor any mention of rate limits, bulk operations, or production-scale guarantees. Missing for 10: explicit contacts/update and suppression API endpoints, documented custom-property schema support, and evidence of production-scale throughput/rate limits.
- [claimed-docs] “add an Authorization header and set the API key as a Bearer token”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
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 BentoLoops' API supports creating/updating contacts and triggering events (loops-docs-4, loops-docs-3), and segments are described as dynamic (loops-docs-16), but no evidence shows an endpoint to read back which contacts belong to a segment, tag, or list. Missing for 10: documented GET/list endpoints for contacts by segment/tag/list, and confirmation that programmatic tag/list membership queries are supported.
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
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 BentoLoops explicitly claims segments are built from profile properties and stay dynamic as data changes (loops-docs-16), and the API supports contacts with properties and events that trigger workflows (loops-docs-3, loops-docs-4), suggesting behavioral/event-based segmentation is possible. However, there's no explicit documentation of tag-based segmentation or a dedicated segment-builder UI walkthrough, and no independent/hands-on confirmation of live segment updates. Missing for 10: explicit tag-attribute mention, segment-builder UI documentation, and independent corroboration of segments staying live.
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
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 BentoLoopsnone0/10Evidence shows only single-item API operations (create one contact, send one event, send one transactional email) and no documented bulk/batch endpoints, CSV import, or bulk update/segment operations for AI agents to invoke at scale.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Send transactional emails with dynamic data variables, right from your backend.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
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 BentoLoops' event API explicitly triggers workflows ('Send an event to trigger workflows') and marketing copy references onboarding/activation/winback flows set up once and running automatically, matching the rule-on-event automation pattern. However, the evidence pack lacks detail on how rules/conditions are authored (branching logic, if/then rules, workflow builder specifics) beyond the event-trigger primitive. Missing for 10: documentation of conditional rule logic/branching in workflows, independent hands-on confirmation of workflow automation depth.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “Reach users after they close the tab. Set up onboarding, activation, upgrade, and winback emails once, then improve them over time.”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
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 to LoopsLoops supports event-triggered workflows (POST /events/send) and lifecycle emails (onboarding, winback, etc.) that run automatically once set up, which touches on workflow automation, but there is no evidence of an API or agent-facing capability to schedule recurring jobs/crons directly — workflow triggers are event-based and configured largely via the dashboard. missing for 10: explicit recurring/cron scheduling API, agent-driven workflow creation beyond event triggers, independent confirmation of automation depth.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “Reach users after they close the tab. Set up onboarding, activation, upgrade, and winback emails once, then improve them over time.”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
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 drawnLoopsnone0/10Loops evidence covers email campaign creation, API/MCP integration, and content authoring, but there is no mention of versioning, reviewing changes, or rolling back automations/workflows — the closest is draft campaigns reviewed before sending, which is not version history or rollback.
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 LoopsLoops explicitly supports agents creating draft campaigns via API that are then reviewed/sent from the dashboard (loops-docs-5, loops-docs-9), and has API/MCP access for contacts, events, and content (loops-docs-3,4,6). However, there's no explicit evidence of segment targeting being part of the drafted campaign creation flow, nor of a 'scheduled/queued' state distinct from 'draft awaiting dashboard review' — the described flow is draft-then-manual-send rather than draft-then-schedule-with-approval-gate. missing for 10: explicit mention of segment-targeted campaign creation via API, a distinct 'scheduled pending approval' state vs plain draft, and independent/hands-on confirmation of this human-approval workflow.
- [claimed-docs] “Create draft campaigns, content and all, straight from the API. Review and send from the dashboard.”
- [claimed-docs] “Author campaigns in code with the Content API and keep editing visually in Loops.”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
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 LoopsLoops documents a Content API that lets developers create draft campaigns via API, but its own docs explicitly state that review and sending happen from the dashboard ('Create draft campaigns... Review and send from the dashboard'), directly contradicting the 'without touching the dashboard' requirement for sending/scheduling. Missing for 10: documented API endpoints for scheduling/sending a campaign, evidence of full campaign lifecycle (create+schedule+send) without dashboard interaction, and independent confirmation of this workflow.
- [claimed-docs] “Create draft campaigns, content and all, straight from the API. Review and send from the dashboard.”
- [claimed-docs] “Author campaigns in code with the Content API and keep editing visually in Loops.”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
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 LoopsDocs describe composing campaigns via editor or Content API, segmenting/targeting dynamic audiences, and sending from the dashboard, covering the core compose→audience→send loop (loops-docs-5, loops-docs-9, loops-docs-16, loops-docs-17, loops-docs-18). Missing for 10: explicit documentation of a 'schedule for later' feature and independent/hands-on confirmation of the end-to-end campaign flow (community evidence only covers pricing/editor tech, not campaign sending itself).
- [claimed-docs] “Create draft campaigns, content and all, straight from the API. Review and send from the dashboard.”
- [claimed-docs] “Author campaigns in code with the Content API and keep editing visually in Loops.”
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
- [claimed-docs] “Set your colors, type, and spacing in one place. Every email you send picks them up automatically, so your brand stays consistent without an…”
- [claimed-docs] “How to craft an email using our editor”
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 drawnLoopsnone0/10No evidence in the pack mentions A/B testing of subject lines or content, nor any automated winner-selection based on engagement metrics; docs cover campaigns, transactional email, contacts, and API/MCP integration but not split-testing functionality.
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 drawnLoopsnone0/10The evidence pack has no mention of bounce, complaint, or blocklist tracking per send, nor any deliverability health dashboard or actionable guidance when deliverability degrades; the closest item ('Guardian checks on an email message') is vague and not tied to bounce/complaint/blocklist metrics. Missing for 10: per-send bounce/complaint/blocklist reporting, deliverability health dashboard, automated alerts or actionable remediation guidance.
- [claimed-docs] “Run Guardian checks on an email message”
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 drawnLoopsnone0/10No evidence in the pack describes domain authentication setup (SPF/DKIM/DMARC), DNS record guidance, or verification tooling; one migration doc merely mentions 'verify your domain' as a step without detail. missing for 10: DNS setup guide, SPF/DKIM/DMARC record instructions, verification status UI or API, any deliverability-domain documentation.
- [claimed-docs] “Move transactional email, contacts, and lists from Brevo to Loops: swap the SDK, map each call, verify your domain, and cut over one email t…”
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 drawnLoopsnone0/10No evidence pack items describe automatic suppression of unsubscribes, bounces, or spam complaints, nor honoring suppression lists across transactional and marketing sends; the community thread even raises a concern about pricing encouraging unlimited sends without addressing suppression handling. Missing for 10: documentation of automatic unsubscribe/bounce/complaint suppression, cross-send-type enforcement, and CAN-SPAM/GDPR compliance details.
- [community] “Concern raised: 'your service seems priced in a way that encourages spam (send unlimited emails to an address)' regarding deliverability/ded…”
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 drawnLoopsnone0/10Evidence only shows generic API/SDK/events/contacts endpoints and migration guides from competing ESPs (Brevo, Customer.io) — there is no mention of maintained first-party integrations with Stripe, Shopify, Segment, or a product database. Ops users would need to build custom API/webhook connections themselves rather than use a documented native integration.
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 drawnLoopsnone0/10No evidence pack item mentions webhooks for delivery/engagement events (sends, opens, clicks, bounces, unsubscribes) or signed payloads; the docs focus on REST API, MCP, CLI, and events for triggering workflows, not outbound webhook subscriptions. Missing for 10: any webhook subscription endpoint, event types list, and payload signing/verification documentation.
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 BentoEvidence confirms Loops supports lifecycle email use cases like onboarding, activation, upgrade, and winback sequences (loops-docs-15) and event-triggered workflows via API (loops-docs-3), but there is no documentation of branching logic, time-based delays, or exit-rule conditions within a visual automation builder. missing for 10: explicit branch/condition support, delay/wait-step configuration, exit-rule mechanics, and independent confirmation of a multi-step workflow builder.
- [claimed-docs] “Reach users after they close the tab. Set up onboarding, activation, upgrade, and winback emails once, then improve them over time.”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
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 LoopsLoops' API includes a documented POST /events/send endpoint explicitly for triggering workflows per contact, alongside contact identification via API key/email, matching the story of firing a custom event to trigger a targeted automation. This is corroborated by an OpenAPI spec and SDK/docs references, though there's no independent hands-on report specifically testing event-triggered automation reliability. missing for 10: independent/hands-on verification of event-to-automation triggering, more detail on per-contact targeting semantics.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “Add Loops to your application in minutes with our SDKs.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
- [claimed-docs] “Manage contacts, send events, and test transactional email from your terminal”
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 drawnLoopsnone0/10The evidence shows Loops can trigger workflows via events and manage contacts via API, but there is no documentation of viewing an individual contact's position within a live automation/workflow or safely pulling/re-entering them without disrupting the flow. Missing for 10: workflow visualization UI, per-contact automation status view, documented pull/re-enter mechanics.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
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 BentoLoopsnone0/10The evidence pack shows API endpoints for creating contacts and sending events, migration guides for moving data INTO Loops from other providers, and CLI/SDK/MCP tooling, but no documented export endpoint, bulk-export feature, or self-serve mechanism to pull contacts, tags, engagement history, or suppression lists OUT of Loops in an open format. Missing for 10: a documented export/download API or dashboard feature, evidence of tags/engagement/suppression data being included in any export, and confirmation of an open file format (CSV/JSON) for full audience export.
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Move transactional email, contacts, and lists from Brevo to Loops: swap the SDK, map each call, verify your domain, and cut over one email t…”
- [claimed-docs] “A guide to moving contacts, events, workflows, and transactional email from Customer.io to Loops, with before and after code and a cutover c…”
- [claimed-docs] “Add marketing, lifecycle, and transactional email to your SaaS from one product. Keep your current transactional provider while you migrate.”
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 drawnLoops publishes migration guides for moving contacts, lists, events, and transactional email from platforms like Brevo and Customer.io with 'before and after code and a cutover checklist,' indicating some list-portability support, but these are developer-facing API migration guides rather than a marketer-friendly guided import wizard. No evidence explicitly confirms preservation of tags, custom fields, or unsubscribe state during import. Missing for 10: explicit UI-based guided import flow for marketers, confirmation that tags/custom fields/unsubscribe status are preserved, and independent evidence of successful migrations.
- [claimed-docs] “Move transactional email, contacts, and lists from Brevo to Loops: swap the SDK, map each call, verify your domain, and cut over one email t…”
- [claimed-docs] “A guide to moving contacts, events, workflows, and transactional email from Customer.io to Loops, with before and after code and a cutover c…”
- [claimed-docs] “Add marketing, lifecycle, and transactional email to your SaaS from one product. Keep your current transactional provider while you migrate.”
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 BentoLoops exposes API/MCP access to contacts (audiences), events (automation triggers), and campaign content creation, and dashboard analytics on which emails drive upgrades/churn exist, but there's no documented endpoint or MCP capability for pulling campaign performance/results data programmatically — the 'report on what's working' analytics piece is not evidenced as API-accessible. missing for 10: an API/MCP endpoint for campaign performance metrics, evidence of reading analytics/results data programmatically rather than just creating content or contacts.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Create draft campaigns, content and all, straight from the API. Review and send from the dashboard.”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://loops.so/agents/mcp”
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 drawnLoopsnone0/10The evidence pack documents contact creation, event sending, campaign drafting, and transactional email APIs, but nowhere shows an endpoint or documentation for retrieving per-contact engagement history (sends, opens, clicks) via the API. This is a fair capability to expect from an email marketing platform, but no evidence confirms it exists.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Run Guardian checks on an email message”
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 drawnLoopsnone0/10Evidence shows only a single Bearer-token API key auth model with no mention of scoped, read-only, or per-agent/contractor credentials; nothing indicates permission tiers or restricted-scope keys.
- [claimed-docs] “add an Authorization header and set the API key as a Bearer token”
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 to LoopsLoops exposes a broad API (contacts, events, transactional email, content/campaign drafting, Guardian checks) plus an OpenAPI spec, CLI, and MCP server, letting AI-native users perform most workflows programmatically (loops-docs-3, loops-docs-4, loops-docs-5, loops-docs-19, loops-probe-3, loops-probe-4). However, campaign creation explicitly notes 'Review and send from the dashboard,' meaning the final send step is UI-only, and analytics/segmentation dashboards have no documented API equivalent. Missing for 10: API parity for sending/publishing campaigns, API access to analytics/segments, independent confirmation of full UI-API parity.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Create draft campaigns, content and all, straight from the API. Review and send from the dashboard.”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [claimed-docs] “Run Guardian checks on an email message”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://loops.so/agents/mcp”
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 BentoLoopsnone0/10Evidence shows API endpoints for creating/writing contacts and events, migration guides for moving data INTO Loops from other providers, and an OpenAPI spec, but nothing documents a bulk export feature or open-format data portability for users wanting to leave Loops with their data.
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”
ai-native userRead the product's source under an open license
weight 2 · round drawnLoopsnone0/10Loops is a closed-source SaaS email platform; no evidence of an open-source license or public source code repository is provided anywhere in the evidence pack.
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 drawnLoopsnone0/10No evidence in the pack mentions data residency, regional storage options, or compliance controls letting users choose where data is stored; Loops' documentation focuses on email API, agents, and pricing, not data residency.
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 drawnLoopsnone0/10No evidence in the pack addresses AI-training data usage, opt-outs, or privacy commitments regarding model training; Loops' materials focus on email/marketing API features, not data-privacy policy toward AI training. Missing for 10: any privacy policy statement, opt-out mechanism, or documentation about AI training data usage.
ai-native userControl data retention and deletion
weight 2 · round drawnLoopsnone0/10No evidence pack items address data retention policies, deletion controls, data export, or GDPR/CCPA-style deletion APIs for contacts/events. The docs focus on sending email, API/SDK usage, and migration, with nothing on how a user or agent controls retention or deletion of stored data. Missing for 10: documented data retention policy, contact/event deletion API or endpoint, data export/erasure workflow, and any privacy compliance certification.
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 drawnLoopsnone0/10No evidence in the pack mentions telemetry, analytics opt-out, or usage tracking controls for Loops as a product/tool; the evidence focuses on email API/agent features and pricing/UX community feedback. missing for 10: any documentation of telemetry collection or an opt-out mechanism, privacy settings, or data-collection disclosure.
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 drawnLoopsnone0/10Evidence shows API-driven draft campaign creation, agent/MCP integrations, and a text-based editor, but there is no mention of a built-in AI feature inside the composer that drafts or refines subject lines/email copy from a brief — the 'AI drafting' capability described is done by external coding agents via API/MCP, not a native in-app AI assistant.
- [claimed-docs] “Create draft campaigns, content and all, straight from the API. Review and send from the dashboard.”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [claimed-docs] “Author campaigns in code with the Content API and keep editing visually in Loops.”
- [claimed-docs] “I scanned your codebase and found every send, template, and webhook. Each one maps to a Loops equivalent, so I swapped the API calls and reb…”
- [claimed-docs] “How to craft an email using our editor”
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 to LoopsLoops documents an email editor, brand-consistency settings (colors/type/spacing applied automatically), dynamic personalization variables, and reusable content built via templates/Content API (loops-docs-17, loops-docs-18, loops-docs-2, loops-docs-9, loops-docs-14). Community evidence confirms the editor is a customizable, text-based system built on extended MJML (loops-comm-7), which supports templating but is not a classic drag-and-drop visual builder, and no evidence addresses cross-client rendering testing or guarantees. missing for 10: explicit cross-email-client rendering validation, confirmation of a fully visual (non-code) editor experience, independent hands-on review of template reuse in practice.
- [claimed-docs] “Set your colors, type, and spacing in one place. Every email you send picks them up automatically, so your brand stays consistent without an…”
- [claimed-docs] “How to craft an email using our editor”
- [claimed-docs] “Send transactional emails with dynamic data variables, right from your backend.”
- [claimed-docs] “Author campaigns in code with the Content API and keep editing visually in Loops.”
- [claimed-docs] “I scanned your codebase and found every send, template, and webhook. Each one maps to a Loops equivalent, so I swapped the API calls and reb…”
- [community] “Founder explains editor was rewritten using Lexical (switched from Slate.js) to power their text-based, customizable email editor, built on …”
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 to LoopsLoops offers a Content API to author campaigns in code (loops-docs-9), transactional emails with dynamic data variables (loops-docs-2), and an editor built on extended MJML (loops-comm-7), which together enable API-managed templates with variable substitution that a developer could store in their own repo. However, there's no first-party feature for native version-control integration, template diffing, or a documented HTML/MJML file-based workflow — the API/editor split still centers editing in the dashboard. Missing for 10: explicit git/version-control integration or CLI-based template push/pull workflow, and independent confirmation that Content API templates round-trip cleanly with raw MJML/HTML files.
- [claimed-docs] “Author campaigns in code with the Content API and keep editing visually in Loops.”
- [claimed-docs] “Send transactional emails with dynamic data variables, right from your backend.”
- [community] “Founder explains editor was rewritten using Lexical (switched from Slate.js) to power their text-based, customizable email editor, built on …”
- [claimed-docs] “Create draft campaigns, content and all, straight from the API. Review and send from the dashboard.”
- [claimed-docs] “I scanned your codebase and found every send, template, and webhook. Each one maps to a Loops equivalent, so I swapped the API calls and reb…”
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 drawnLoops explicitly documents sending transactional emails with dynamic data via API/SDK alongside marketing/lifecycle sends from the same platform, with an OpenAPI spec and events API to trigger workflows, and this is corroborated by community mention of a 'performant API with versioning for transactional email.' Missing for 10: no hands-on developer report of using the transactional send endpoint specifically (e.g. receipts/magic links) beyond docs framing, and no independent deliverability benchmark for transactional use.
- [claimed-docs] “Send transactional emails with dynamic data variables, right from your backend.”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “Add marketing, lifecycle, and transactional email to your SaaS from one product. Keep your current transactional provider while you migrate.”
- [probe] “PROBE llms.txt: HTTP 200 at https://loops.so/llms.txt # Loops > Loops is an email platform for software companies. Send transactional and m…”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
- [community] “Founder describes Loops' approach: simplified pricing (no tables, one metric), performant API with versioning for transactional email, text-…”
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 BentoDocs confirm Loops offers distinct transactional email sending (its own API/backend calls) separate from marketing/lifecycle campaigns, and migration guides note transactional vs marketing distinctions, but there is no explicit documentation of separate suppression-list logic or dedicated sending reputation ensuring transactional mail still reaches unsubscribed contacts. Missing for 10: explicit suppression-rule separation, reputation isolation, and confirmation that unsubscribe status doesn't block transactional sends.
- [claimed-docs] “Send transactional emails with dynamic data variables, right from your backend.”
- [claimed-docs] “Add marketing, lifecycle, and transactional email to your SaaS from one product. Keep your current transactional provider while you migrate.”
- [claimed-docs] “Move transactional email, contacts, and lists from Brevo to Loops: swap the SDK, map each call, verify your domain, and cut over one email t…”
- [claimed-docs] “A guide to moving contacts, events, workflows, and transactional email from Customer.io to Loops, with before and after code and a cutover c…”
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 comparableLoopsn/aLoops is an email/marketing SaaS platform, not an AI agent — the evidence shows Loops publishing its own MCP server so other agents can call ITS tools (loops-docs-6, loops-probe-4), which is the server role, not Loops acting as a client that plugs in external MCP servers to gain their tools. There is no agentic/assistant capability within Loops that could consume external MCP servers, so this axis is a category error for this product.
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [probe] “official MCP server documented at https://loops.so/agents/mcp”
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 userSelf-host the core product
weight 3 · not comparableLoopsn/aLoops is a hosted SaaS email platform; nothing in the evidence suggests a self-hostable core product, and this is inherently a cloud service (with SES/SES-like MTA infra) rather than software distributed for self-hosting — this axis is a category error for this product type.