Loops vs Klaviyo
Loops wins · 19–8 (28 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 to LoopsLoops 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”
Klaviyonone0/10A direct probe for llms.txt returned 404, and no evidence pack item mentions agent-oriented documentation formats aside from the unrelated MCP server docs, which serve a different purpose (data assistance, not doc discovery for agents).
- [probe] “PROBE llms.txt: HTTP 404 at https://developers.klaviyo.com/llms.txt”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round drawnLoops 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”
Klaviyo exposes a full REST API secured by API keys/OAuth, with maintained SDKs (Python, PHP, Ruby, Node) and a sandbox test account for safely automating campaign creation, imports, etc. — enough to script/automate outside the UI, but there is no explicit CI/CD documentation, CLI tool, or headless-runner guidance in the evidence. Missing for 10: dedicated CI/CD integration docs, official CLI, and any explicit statement about running headlessly in automated pipelines.
- [claimed-docs] “All `/api` endpoints use private API keys with API key scopes to authenticate requests.”
- [claimed-docs] “Install a Klaviyo maintained SDK to accelerate development– offered in Python, PHP, Ruby, and Node.”
- [claimed-docs] “Test custom integrations and apps without the risk of impacting your production account.”
- [claimed-docs] “Populate your test account with sample data to quickly explore our API and see how data is used in Klaviyo.”
- [claimed-docs] “Make test calls using Postman’s UI tool with our collection of pre-built API requests.”
- [claimed-docs] “Creates a campaign given a set of parameters, then returns it.”
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”
Klaviyo documents an official MCP server that connects to MCP clients like Claude or Cursor, with example usage shown. Missing for 10: independent/hands-on third-party corroboration and details on scopes/auth specific to the MCP server itself.
- [claimed-docs] “You’ll connect Klaviyo’s MCP server to an MCP client, i.e., an AI agent like Claude or Cursor, to get assistance with your Klaviyo data.”
- [claimed-docs] ““Create an email campaign promoting our Memorial Day sale.””
- [probe] “official MCP server documented at https://developers.klaviyo.com/en/docs/klaviyo_mcp_server”
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.”
Klaviyonone0/10Evidence shows SDKs in Python/PHP/Ruby/Node and an MCP server, but no mention of an official CLI tool anywhere in the docs; llms.txt probe 404s and no CLI reference exists.
- [claimed-docs] “Install a Klaviyo maintained SDK to accelerate development– offered in Python, PHP, Ruby, and Node.”
- [probe] “PROBE llms.txt: HTTP 404 at https://developers.klaviyo.com/llms.txt”
ai-native userDrive the product through a documented public API
weight 3 · round drawnLoops 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.”
Klaviyo publishes a comprehensive public REST API with documented authentication (private API keys, OAuth for partners), scoped permissions, official SDKs in multiple languages, sandbox test accounts, and Postman collections, plus concrete endpoint docs (e.g., create campaign) showing programmatic control. Missing for 10: no evidence of an llms.txt or AI-specific machine-readable API discovery file, and no independent third-party corroboration of API robustness beyond vendor docs.
- [claimed-docs] “All `/api` endpoints use private API keys with API key scopes to authenticate requests.”
- [claimed-docs] “If you are a tech partner integrating with Klaviyo, we recommend using OAuth to authenticate your app.”
- [claimed-docs] “Install a Klaviyo maintained SDK to accelerate development– offered in Python, PHP, Ruby, and Node.”
- [claimed-docs] “Test custom integrations and apps without the risk of impacting your production account.”
- [claimed-docs] “Make test calls using Postman’s UI tool with our collection of pre-built API requests.”
- [claimed-docs] “Creates a campaign given a set of parameters, then returns it.”
- [claimed-docs] “Adding a scope helps you protect your and your customers’ data by limiting what third parties can access.”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to KlaviyoLoopsnone0/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”
Klaviyo supports private API keys with scoped permissions and explicitly frames scopes as a way to limit third-party access, which directly supports issuing least-privilege credentials for an agent; OAuth is also recommended for integrator apps. However, there's no documented workflow specifically for provisioning agent-specific credentials, no granular scope list/enumeration shown, and no evidence of key rotation, expiry, or agent-specific audit trails. missing for 10: agent-specific credential provisioning workflow, full enumerated scope list, key rotation/expiry controls, independent confirmation of scope enforcement in practice.
- [claimed-docs] “All `/api` endpoints use private API keys with API key scopes to authenticate requests.”
- [claimed-docs] “If you are a tech partner integrating with Klaviyo, we recommend using OAuth to authenticate your app.”
- [claimed-docs] “Adding a scope helps you protect your and your customers’ data by limiting what third parties can access.”
ai-native userBuild against official SDKs
weight 2 · round drawnLoops 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”
Klaviyo maintains official SDKs in Python, PHP, Ruby, and Node, backed by API key/OAuth authentication, sandboxed test accounts, and Postman collections for development. Missing for 10: independent/third-party corroboration of SDK quality and no explicit mention of typed/async support or SDK versioning cadence.
- [claimed-docs] “Install a Klaviyo maintained SDK to accelerate development– offered in Python, PHP, Ruby, and Node.”
- [claimed-docs] “All `/api` endpoints use private API keys with API key scopes to authenticate requests.”
- [claimed-docs] “If you are a tech partner integrating with Klaviyo, we recommend using OAuth to authenticate your app.”
- [claimed-docs] “Test custom integrations and apps without the risk of impacting your production account.”
- [claimed-docs] “Make test calls using Postman’s UI tool with our collection of pre-built API requests.”
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”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round drawnLoopsnone0/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.”
Klaviyonone0/10The evidence only covers Klaviyo's MCP server, which lets external AI agents (Claude, Cursor) query and act on Klaviyo data—this is an external-agent integration, not native in-product AI-generated insights or suggestions surfaced to the user inside Klaviyo's own UI. No evidence pack item describes built-in analytics AI, predictive suggestions, or in-app insight generation. Missing for 10: any documentation of native AI-driven insights/suggestions surfaced within Klaviyo's own dashboard or reporting UI.
- [claimed-docs] “You’ll connect Klaviyo’s MCP server to an MCP client, i.e., an AI agent like Claude or Cursor, to get assistance with your Klaviyo data.”
- [claimed-docs] ““Create an email campaign promoting our Memorial Day sale.””
- [probe] “official MCP server documented at https://developers.klaviyo.com/en/docs/klaviyo_mcp_server”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to LoopsLoops 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.”
Klaviyo's pricing docs confirm the platform supports building automations (flows) that presumably run autonomously once configured, and the MCP server lets an AI agent interact with Klaviyo (e.g., create campaigns) — suggesting some AI-native automation setup is possible. However, the evidence never details how automations trigger/run in the background, whether MCP can create or manage automation flows specifically, or any autonomous execution mechanics beyond a one-line mention. Missing for 10: documentation of flow/automation trigger logic and autonomous runtime behavior, evidence that MCP or another AI-native interface can configure automations (not just campaigns), and independent confirmation of autonomous background execution.
- [claimed-docs] “use the drag-and-drop email/SMS editors and build automations, segmentation and reports”
- [claimed-docs] “You’ll connect Klaviyo’s MCP server to an MCP client, i.e., an AI agent like Claude or Cursor, to get assistance with your Klaviyo data.”
- [claimed-docs] ““Create an email campaign promoting our Memorial Day sale.””
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round drawnLoopsnone0/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”
Klaviyonone0/10Evidence only shows Klaviyo exposing an MCP server so external AI agents (Claude, Cursor) can act on Klaviyo data — this is the reverse of a built-in assistant inside Klaviyo itself. No documentation of an in-product AI assistant users delegate tasks to directly within the Klaviyo UI.
- [claimed-docs] “You’ll connect Klaviyo’s MCP server to an MCP client, i.e., an AI agent like Claude or Cursor, to get assistance with your Klaviyo data.”
- [claimed-docs] ““Create an email campaign promoting our Memorial Day sale.””
- [probe] “official MCP server documented at https://developers.klaviyo.com/en/docs/klaviyo_mcp_server”
ai-native userOperate the product with natural-language commands
weight 2 · round drawnLoops 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”
Klaviyo ships an official MCP server that connects to AI agents (Claude, Cursor), enabling natural-language commands like "Create an email campaign promoting our Memorial Day sale" to operate Klaviyo data and actions. This directly supports natural-language operation, but it's mediated through third-party MCP clients rather than a native NL interface, and there's no independent/hands-on corroboration of reliability. Missing for 10: first-party natural-language UI within Klaviyo itself, independent verification of MCP command success, breadth of supported natural-language operations beyond the single documented example.
- [claimed-docs] “You’ll connect Klaviyo’s MCP server to an MCP client, i.e., an AI agent like Claude or Cursor, to get assistance with your Klaviyo data.”
- [claimed-docs] ““Create an email campaign promoting our Memorial Day sale.””
- [probe] “official MCP server documented at https://developers.klaviyo.com/en/docs/klaviyo_mcp_server”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to KlaviyoLoops 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”
Klaviyo provides a Postman collection of pre-built API requests and a sandboxed test account for exploring the API, plus reference pages describing individual endpoints, but this relies on an external tool (Postman) rather than an in-browser interactive 'try it out' console with runnable examples. missing for 10: evidence of a native in-docs interactive API explorer/console, runnable code snippets embedded in the reference pages themselves.
- [claimed-docs] “Make test calls using Postman’s UI tool with our collection of pre-built API requests.”
- [claimed-docs] “Test custom integrations and apps without the risk of impacting your production account.”
- [claimed-docs] “Populate your test account with sample data to quickly explore our API and see how data is used in Klaviyo.”
- [claimed-docs] “Creates a campaign given a set of parameters, then returns it.”
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”
Klaviyonone0/10Klaviyo's developer docs describe a full REST API reference, SDKs, and a Postman collection, but no evidence mentions a downloadable OpenAPI/Swagger spec file or machine-readable schema; the llms.txt probe returned 404 as well. missing for 10: explicit OpenAPI/Swagger spec download link, documented schema export, or API definition file.
- [claimed-docs] “Make test calls using Postman’s UI tool with our collection of pre-built API requests.”
- [probe] “PROBE llms.txt: HTTP 404 at https://developers.klaviyo.com/llms.txt”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round to KlaviyoLoopsnone0/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.
Klaviyo explicitly documents a test/sandbox account for testing integrations without affecting production, plus sample data population and Postman collections for exploration. missing for 10: independent/hands-on confirmation of sandbox fidelity, and explicit guidance on using the sandbox specifically with AI agents/MCP workflows.
- [claimed-docs] “Test custom integrations and apps without the risk of impacting your production account.”
- [claimed-docs] “Populate your test account with sample data to quickly explore our API and see how data is used in Klaviyo.”
- [claimed-docs] “Make test calls using Postman’s UI tool with our collection of pre-built API requests.”
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”
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”
Klaviyonone0/10The evidence pack shows general API access, authentication, and SDKs, plus a campaign-creation endpoint, but no documentation of any reporting/analytics or metrics endpoints for campaign or flow performance data. Missing for 10: evidence of a Campaigns/Flows reporting or metrics API endpoint, sample response schemas for performance data, or any mention of pulling analytics into a warehouse/BI tool.
- [claimed-docs] “Creates a campaign given a set of parameters, then returns it.”
- [claimed-docs] “All `/api` endpoints use private API keys with API key scopes to authenticate requests.”
- [claimed-docs] “Install a Klaviyo maintained SDK to accelerate development– offered in Python, PHP, Ruby, and Node.”
Attribution
founderAttribute signups or revenue to specific emails and flows, not just opens and clicks
weight 2 · round to LoopsLoops 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.”
Reporting core
marketerRead opens, clicks, unsubscribes, and conversions per campaign and per automation step, over time
weight 3 · round drawnLoopsnone0/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.”
Klaviyonone0/10The evidence pack contains no documentation of campaign/automation analytics reporting (opens, clicks, unsubscribes, conversions) or any reporting/analytics API or dashboard feature; it only covers API auth, SDKs, testing, MCP server, and pricing. Missing for 10: any mention of a reporting/analytics dashboard, per-campaign or per-flow-step metrics, or a metrics API endpoint.
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 to KlaviyoLoopsnone0/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.”
Klaviyo has a documented MCP server that lets an AI agent act on Klaviyo data via natural language, and the API supports arbitrary schema-free data plus programmatic campaign creation, suggesting an agent could plausibly create segments too. However, no evidence pack item shows a segment-creation endpoint or an MCP example translating a plain-language audience description into an actual segment (the campaign example is the only concrete natural-language-to-action illustration). Missing for 10: explicit segment/API endpoint documentation, a worked example of natural-language-to-segment translation, and independent/hands-on confirmation this works in practice.
- [claimed-docs] “You’ll connect Klaviyo’s MCP server to an MCP client, i.e., an AI agent like Claude or Cursor, to get assistance with your Klaviyo data.”
- [claimed-docs] ““Create an email campaign promoting our Memorial Day sale.””
- [claimed-docs] “Since Klaviyo doesn't impose a rigid data schema, it's easy to send in just about any arbitrary data without having to do annoying manipulat…”
- [claimed-docs] “Creates a campaign given a set of parameters, then returns it.”
- [probe] “official MCP server documented at https://developers.klaviyo.com/en/docs/klaviyo_mcp_server”
Api contacts
developerCreate, update, and suppress contacts with custom properties through the API at production scale
weight 3 · round to KlaviyoEvidence 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 flexible, schema-less API that accepts arbitrary custom data (klaviyo-docs-8), key-scoped authentication (klaviyo-docs-1, klaviyo-docs-14), and SDKs for production integration (klaviyo-docs-3), plus a sandbox for testing at scale (klaviyo-docs-4, klaviyo-docs-5). However, the pack never cites a specific contacts/profiles create-update-suppress endpoint (only campaign creation is shown), so explicit support for suppression workflows is unproven. Missing for 10: direct documentation of profile create/update endpoints, explicit suppression/unsubscribe API reference, and evidence of rate limits/production-scale throughput guarantees.
- [claimed-docs] “Since Klaviyo doesn't impose a rigid data schema, it's easy to send in just about any arbitrary data without having to do annoying manipulat…”
- [claimed-docs] “All `/api` endpoints use private API keys with API key scopes to authenticate requests.”
- [claimed-docs] “Adding a scope helps you protect your and your customers’ data by limiting what third parties can access.”
- [claimed-docs] “Install a Klaviyo maintained SDK to accelerate development– offered in Python, PHP, Ruby, and Node.”
- [claimed-docs] “Test custom integrations and apps without the risk of impacting your production account.”
- [claimed-docs] “Populate your test account with sample data to quickly explore our API and see how data is used in Klaviyo.”
Api segments
developerCreate and update segments, tags, or lists programmatically and read back exactly who is in them
weight 3 · round to LoopsLoops' 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”
Klaviyonone0/10The evidence pack covers general API authentication, SDKs, sandbox testing, campaign creation, and MCP server integration, but contains no documentation of specific endpoints for creating/updating segments, tags, or lists, nor for reading back their membership. Missing for 10: any reference to Lists/Segments/Tags API endpoints, membership read endpoints, or examples of programmatic segment management.
- [claimed-docs] “All `/api` endpoints use private API keys with API key scopes to authenticate requests.”
- [claimed-docs] “Creates a campaign given a set of parameters, then returns it.”
- [claimed-docs] “Since Klaviyo doesn't impose a rigid data schema, it's easy to send in just about any arbitrary data without having to do annoying manipulat…”
Segment core
marketerBuild audience segments from profile attributes, tags, and behavioral events, and they stay live as data changes
weight 3 · round to LoopsLoops 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”
Klaviyo's pricing page confirms segmentation as a core feature alongside automations and reports, but the evidence pack contains no documentation of how segments are built from profile attributes/tags/behavioral events or how they stay dynamically live as data changes. missing for 10: technical docs on segment definition logic, dynamic/live-updating behavior, and support for tags and behavioral event conditions.
- [claimed-docs] “use the drag-and-drop email/SMS editors and build automations, segmentation and reports”
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 drawnLoopsnone0/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”
Klaviyonone0/10The evidence pack covers API authentication, SDKs, sandbox testing, single-campaign creation, and the MCP server, but contains no mention of bulk/batch endpoints, mass import/export operations, or any mechanism for operating on many items at once. Missing for 10: bulk/batch API endpoints, documented rate-limit-aware batch processing, bulk data import/export tooling.
- [claimed-docs] “Creates a campaign given a set of parameters, then returns it.”
- [claimed-docs] “Since Klaviyo doesn't impose a rigid data schema, it's easy to send in just about any arbitrary data without having to do annoying manipulat…”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to LoopsLoops' 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”
Klaviyo's pricing page mentions users can 'build automations' alongside segmentation and reports, implying event-triggered flow automation exists, but the evidence pack provides no detail on rule definition, trigger types, or conditional logic. missing for 10: documentation of flow/automation trigger configuration, conditional branching, and event-based rule examples.
- [claimed-docs] “use the drag-and-drop email/SMS editors and build automations, segmentation and reports”
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.”
Klaviyo's automation platform includes 'flows'/automations (klaviyo-docs-11) and campaign creation via API (klaviyo-docs-7), but the evidence never shows an AI-native user scheduling recurring jobs via the API or MCP server—MCP docs only describe one-off campaign creation requests (klaviyo-docs-9, klaviyo-docs-10), not recurring/cron-based automation triggering. Missing for 10: API/MCP documentation of recurring schedule creation, cron-like triggers, or workflow automation exposed to AI agents specifically.
- [claimed-docs] “use the drag-and-drop email/SMS editors and build automations, segmentation and reports”
- [claimed-docs] “Creates a campaign given a set of parameters, then returns it.”
- [claimed-docs] “You’ll connect Klaviyo’s MCP server to an MCP client, i.e., an AI agent like Claude or Cursor, to get assistance with your Klaviyo data.”
- [claimed-docs] ““Create an email campaign promoting our Memorial Day sale.””
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.”
Klaviyo's API and MCP server let an agent draft/create a campaign via natural language (klaviyo-docs-7, klaviyo-docs-9, klaviyo-docs-10), which implies a campaign is created before being sent, but there's no explicit documentation describing a scheduled/queued draft state with a human-approval gate before send. Missing for 10: explicit docs on campaign draft/review states, scheduling API parameters, or an approval workflow between agent creation and send.
- [claimed-docs] “Creates a campaign given a set of parameters, then returns it.”
- [claimed-docs] “You’ll connect Klaviyo’s MCP server to an MCP client, i.e., an AI agent like Claude or Cursor, to get assistance with your Klaviyo data.”
- [claimed-docs] ““Create an email campaign promoting our Memorial Day sale.””
Api campaigns
developerCreate and schedule a campaign or broadcast entirely through a documented public API, without touching the dashboard
weight 3 · round to KlaviyoLoops 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.”
Klaviyo's public API documents a create_campaign endpoint with API key/OAuth auth and SDKs, supporting programmatic campaign creation, but the evidence pack lacks documentation of a scheduling/send endpoint or a full end-to-end example proving a campaign can be scheduled and sent without ever using the dashboard. missing for 10: documented schedule/send-campaign endpoint, evidence of full lifecycle (create+schedule+send) purely via API, independent developer confirmation this works end-to-end.
- [claimed-docs] “Creates a campaign given a set of parameters, then returns it.”
- [claimed-docs] “All `/api` endpoints use private API keys with API key scopes to authenticate requests.”
- [claimed-docs] “If you are a tech partner integrating with Klaviyo, we recommend using OAuth to authenticate your app.”
- [claimed-docs] “Install a Klaviyo maintained SDK to accelerate development– offered in Python, PHP, Ruby, and Node.”
Campaign core
marketerCompose an email campaign, pick its audience, and send or schedule it — the arena's table-stakes loop
weight 3 · round drawnDocs 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”
Docs show a Create Campaign API, a drag-and-drop email editor, and built-in segmentation/automation, and even AI-assisted campaign creation via the MCP server (e.g., 'Create an email campaign promoting our Memorial Day sale'), covering the compose+audience+send loop. Missing for 10: explicit documentation of the schedule/send UI step and audience-selection mechanics beyond generic 'segmentation' mention.
- [claimed-docs] “Creates a campaign given a set of parameters, then returns it.”
- [claimed-docs] “use the drag-and-drop email/SMS editors and build automations, segmentation and reports”
- [claimed-docs] ““Create an email campaign promoting our Memorial Day sale.””
- [claimed-docs] “You’ll connect Klaviyo’s MCP server to an MCP client, i.e., an AI agent like Claude or Cursor, to get assistance with your Klaviyo data.”
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.
Klaviyonone0/10None of the evidence items mention A/B testing, subject line testing, or automatic winner selection based on engagement; only campaign creation via API and general platform features are documented. Missing for 10: any mention of A/B test creation, variant configuration, winning metric selection, or automatic send-to-winner mechanics.
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”
Klaviyonone0/10No evidence in the pack addresses bounce, complaint, or blocklist deliverability signals, per-send reporting, or actionable guidance for deliverability degradation; the pack only covers API auth, SDKs, MCP server, and pricing. Missing for 10: any documentation of deliverability/bounce/complaint/blocklist metrics, per-send reporting, or guidance features.
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…”
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…”
Klaviyonone0/10None of the evidence items address suppression handling, unsubscribe/bounce/spam-complaint processing, or CAN-SPAM/GDPR compliance mechanics; the pack is limited to API auth, SDKs, MCP server, and pricing. missing for 10: documentation of automatic suppression lists, bounce/complaint handling, cross-channel enforcement across email/SMS sends, and compliance default behavior.
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.
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.
Klaviyonone0/10No evidence in the pack mentions webhooks, event subscriptions, or signed payloads for delivery/engagement events; the docs cover API auth, SDKs, MCP server, and pricing but nothing about webhook subscriptions or signature verification. missing for 10: webhook subscription API/docs, list of supported event types (sends, opens, clicks, bounces, unsubscribes), payload signing/verification mechanism.
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 LoopsEvidence 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.”
Evidence only vaguely mentions building 'automations' via drag-and-drop editors, without any detail on branches, delays, exit rules, or lifecycle templates like welcome/onboarding/winback series. Klaviyo is widely known for this capability but the provided evidence pack does not document it in depth. missing for 10: documentation of branching logic, time-delay steps, exit/entry conditions, and specific lifecycle flow templates (welcome, winback, onboarding).
- [claimed-docs] “use the drag-and-drop email/SMS editors and build automations, segmentation and reports”
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”
Klaviyo's docs mention flexible, schema-less data ingestion ('arbitrary data') which implies custom event tracking, but the evidence pack lacks any explicit mention of a track-event API or of flows/automations being triggered by specific custom events for an individual profile. Missing for 10: explicit custom event API documentation, explicit flow-trigger-on-event behavior, and confirmation that automations target the specific triggering profile.
- [claimed-docs] “Since Klaviyo doesn't impose a rigid data schema, it's easy to send in just about any arbitrary data without having to do annoying manipulat…”
- [claimed-docs] “All `/api` endpoints use private API keys with API key scopes to authenticate requests.”
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”
Klaviyonone0/10No evidence describes flow-level visibility into where a profile sits within an automation, nor any capability to manually pull or re-enter a person mid-flow without breaking it; evidence only covers API auth, SDKs, sandbox testing, campaign creation, and MCP server setup. Missing for 10: automation flow status view per profile, pull/remove from flow controls, re-enter flow functionality, and any documentation of flow integrity safeguards.
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 drawnLoopsnone0/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.”
Klaviyonone0/10The evidence pack covers API authentication, SDKs, sandbox testing, MCP integration, and pricing tiers, but contains no documentation of a bulk/self-serve export feature covering contacts, custom fields, tags, engagement history, and suppression lists in an open format. Missing for 10: explicit export/download documentation, confirmation of open format (CSV/JSON) output, and evidence suppression list and engagement history are included in any export.
- [claimed-docs] “Since Klaviyo doesn't impose a rigid data schema, it's easy to send in just about any arbitrary data without having to do annoying manipulat…”
- [claimed-docs] “The free plan allows you to create a Klaviyo account, import or sync your contacts and activity data”
Import migration
marketerMigrate in from another email platform with guided list import that preserves tags, custom fields, and unsubscribe state
weight 2 · round to LoopsLoops 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.”
Klaviyonone0/10Evidence pack only covers API scopes, SDKs, sandbox testing, MCP server, and pricing tiers—no mention of a guided migration tool, list import wizard, or preservation of tags/custom fields/unsubscribe state from another ESP. Klaviyo docs mention generic 'import or sync your contacts' but nothing about migration-specific data preservation guarantees.
- [claimed-docs] “The free plan allows you to create a Klaviyo account, import or sync your contacts and activity data”
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 KlaviyoLoops 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”
Klaviyo offers a documented REST API (with scoped private keys and OAuth) and a first-party MCP server explicitly built to let AI agents like Claude or Cursor interact with Klaviyo data, which supports programmatic, agent-driven access. However the evidence only shows a campaign-creation example and general API scope docs — there's no direct documentation of pulling audiences, live automation status, or campaign performance/reporting data through the API or MCP server. Missing for 10: explicit endpoints/examples for audience/segment retrieval, automation status, and campaign analytics/reporting accessible via API or MCP, plus independent confirmation of successful end-to-end reporting use.
- [claimed-docs] “All `/api` endpoints use private API keys with API key scopes to authenticate requests.”
- [claimed-docs] “If you are a tech partner integrating with Klaviyo, we recommend using OAuth to authenticate your app.”
- [claimed-docs] “Creates a campaign given a set of parameters, then returns it.”
- [claimed-docs] “You’ll connect Klaviyo’s MCP server to an MCP client, i.e., an AI agent like Claude or Cursor, to get assistance with your Klaviyo data.”
- [claimed-docs] ““Create an email campaign promoting our Memorial Day sale.””
- [probe] “official MCP server documented at https://developers.klaviyo.com/en/docs/klaviyo_mcp_server”
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”
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 to KlaviyoLoopsnone0/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”
Klaviyo docs confirm private API keys support scopes to limit third-party access (e.g., read-only vs. send permissions), directly matching the ops need to mint restricted credentials for agents/contractors. However, there's no evidence detailing granular scope options (e.g., specific read-only analytics scope vs. campaign-send scope), no UI walkthrough for creating such a key, and no independent/hands-on confirmation of enforcement. missing for 10: granular scope list/UI screenshots, independent verification that scopes actually block send actions, documentation of a dedicated read-only analytics role.
- [claimed-docs] “All `/api` endpoints use private API keys with API key scopes to authenticate requests.”
- [claimed-docs] “Adding a scope helps you protect your and your customers’ data by limiting what third parties can access.”
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”
Klaviyo's API supports many core objects (campaigns, contacts, arbitrary data) and even an MCP server for agent-driven actions, but the docs describe UI-only features like drag-and-drop email/SMS editors and visual automation builders that aren't shown to have API equivalents. Missing for 10: explicit evidence that visual template/automation building, reporting dashboards, and other UI-exclusive workflows are fully exposed via API, and independent confirmation of full UI/API parity.
- [claimed-docs] “Creates a campaign given a set of parameters, then returns it.”
- [claimed-docs] “Since Klaviyo doesn't impose a rigid data schema, it's easy to send in just about any arbitrary data without having to do annoying manipulat…”
- [claimed-docs] “You’ll connect Klaviyo’s MCP server to an MCP client, i.e., an AI agent like Claude or Cursor, to get assistance with your Klaviyo data.”
- [claimed-docs] “use the drag-and-drop email/SMS editors and build automations, segmentation and reports”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnLoopsnone0/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.
Klaviyonone0/10Klaviyo has APIs to read data programmatically, but there's no evidence of a bulk data export tool/feature in open formats, nor any documented data-portability or account-export process for users to leave with their data. missing for 10: documented bulk export feature, open-format (e.g., CSV/JSON) full-account export, data portability/exit policy.
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.
Klaviyonone0/10No evidence in the pack mentions data residency, regional storage options, or ability to choose where data is hosted; the docs focus on API scopes, SDKs, and MCP server, not data location controls. missing for 10: any mention of regional data centers, residency options, or data storage location controls.
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.
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.
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”
Klaviyonone0/10Evidence shows an MCP server for external AI agents (Claude, Cursor) to create campaigns via API, not a built-in AI assistant inside Klaviyo's own composer for drafting/refining subject lines and copy from a brief. No documentation of an in-app AI content generation feature is present.
- [claimed-docs] “You’ll connect Klaviyo’s MCP server to an MCP client, i.e., an AI agent like Claude or Cursor, to get assistance with your Klaviyo data.”
- [claimed-docs] ““Create an email campaign promoting our Memorial Day sale.””
- [claimed-docs] “use the drag-and-drop email/SMS editors and build automations, segmentation and reports”
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 …”
Evidence confirms Klaviyo has a drag-and-drop email editor and campaign creation API, supporting the visual design part of the story, but there is no mention of reusable template libraries, personalization token syntax, or cross-email-client rendering testing/previews. missing for 10: reusable template library details, personalization token documentation, cross-client rendering/testing evidence.
- [claimed-docs] “use the drag-and-drop email/SMS editors and build automations, segmentation and reports”
- [claimed-docs] “Creates a campaign given a set of parameters, then returns it.”
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…”
Klaviyonone0/10Evidence shows a campaign-creation API and drag-and-drop editors, but nothing about managing email templates as HTML/MJML code, API-managed templates with variable substitution, or version-control workflows for template content.
- [claimed-docs] “Creates a campaign given a set of parameters, then returns it.”
- [claimed-docs] “use the drag-and-drop email/SMS editors and build automations, segmentation and reports”
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 LoopsLoops 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-…”
Klaviyonone0/10Evidence shows Klaviyo's API centers on campaigns, flows, SDKs, and MCP integration for marketing sends, but nothing documents a one-to-one transactional email API (e.g., for receipts or magic links) alongside marketing sends.
- [claimed-docs] “All `/api` endpoints use private API keys with API key scopes to authenticate requests.”
- [claimed-docs] “Creates a campaign given a set of parameters, then returns it.”
- [claimed-docs] “Since Klaviyo doesn't impose a rigid data schema, it's easy to send in just about any arbitrary data without having to do annoying manipulat…”
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 LoopsDocs 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…”
Klaviyonone0/10Klaviyo is fundamentally a marketing/email-marketing platform; the evidence pack shows only marketing campaign creation, API scopes, SDKs, and an MCP server — nothing about a distinct transactional-sending pipeline, dedicated transactional templates, separate suppression logic, or isolated sending reputation that bypasses marketing unsubscribes. No mention of transactional email as a concept at all.
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”
Klaviyonone0/10Evidence shows Klaviyo ships its own MCP server so external AI agents (Claude, Cursor) can connect to it and use Klaviyo's tools — the opposite role from the story, which asks whether Klaviyo itself can plug in and consume other MCP servers' tools. No evidence indicates Klaviyo acts as an MCP client integrating third-party MCP servers.
- [claimed-docs] “You’ll connect Klaviyo’s MCP server to an MCP client, i.e., an AI agent like Claude or Cursor, to get assistance with your Klaviyo data.”
- [probe] “official MCP server documented at https://developers.klaviyo.com/en/docs/klaviyo_mcp_server”
ai-native userRead the product's source under an open license
weight 2 · not comparableLoopsnone0/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.
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.