Klaviyo vs Mailchimp

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Mailchimp
   Klaviyo—none0/10

   A 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”

   proof ↗⚑ flag

   Mailchimp✓fullprobed7/10

   A direct probe confirms Mailchimp serves an llms.txt file at the expected URL returning HTTP 200 with structured content summarizing the site, which is exactly what this story asks for. However, there's no evidence of broader agent-oriented documentation beyond this single file, nor independent corroboration of its usefulness or completeness. Missing for 10: evidence of dedicated agent/AI-native docs beyond llms.txt, third-party confirmation of quality/usefulness of the file, and any first-party announcement of this feature.

   • [probe] “PROBE llms.txt: HTTP 200 at https://mailchimp.com/llms.txt # Mailchimp - Complete Web Content Analysis > Comprehensive analysis and documen…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Klaviyo
   Klaviyo~partialclaimed6/10

   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.”

   proof ↗⚑ flag

   Mailchimp~partialcommunity4/10

   Mailchimp exposes REST APIs (Marketing API, Transactional/Mandrill API and SMTP) that could in principle be called headlessly from scripts or CI pipelines to create contacts, send campaigns, or send transactional messages (mailchimp-docs-1,2,4,5,6). However there is no first-party guidance on CI/automation workflows, official SDKs, or CLI tooling, and community reports describe accounts being auto-banned or automation silently shut off (e.g., devtools-triggered blocks and Mandrill sending disabled without notice) which undercuts reliable unattended/headless use (mailchimp-comm-4,5,9,11). missing for 10: documented CI/headless automation examples, official CLI/SDK support, evidence of stable unattended operation without account/service suspension.

   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
   • [claimed-docs] “Send a new SMS message through Mandrill”
   • [community] “A similar thing happened to me while using their Mandrill system. After years of using it with no issues, all of a sudden no emails were get…”
   • [community] “Someone sent a marketing email another customer complained about (just one complaint) and Mailchimp silently shut off our incoming email pro…”
   • [community] “MailChimp blacklists your IP if you open the browser's dev tools; as a developer who often has devtools open, I get banned from Mailchimp fo…”
   • [community] “I had to use their drag-and-drop email builder because a non-dev would edit it; when a Code module became inaccessible via UI, I tried injec…”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Klaviyo
   Klaviyo✓fullprobed8/10

   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”

   proof ↗⚑ flag

   Mailchimp—none0/10

   No evidence of an official MCP server for Mailchimp; only Marketing/Transactional REST APIs and an llms.txt file are documented, none of which constitute an MCP server. missing for 10: any mention of MCP protocol support, an official MCP server endpoint, or agent-connection tooling.

   ⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Klaviyo—none0/10

   Evidence 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”

   proof ↗⚑ flag

   Mailchimp—none0/10

   Evidence pack only shows Mailchimp's REST APIs (Marketing, Transactional, Commerce) and an llms.txt file; there is no mention of an official CLI tool for AI-native workflows. missing for 10: existence of any official CLI, documentation of CLI installation/usage, evidence of AI-native tooling built on a CLI.

   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
   • [claimed-docs] “Mailchimp Open Commerce (formerly Reaction Commerce) is an open source, API-first, modular commerce stack made for technical, growth-minded …”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Klaviyo
   Klaviyo✓fullclaimed9/10

   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.”

   proof ↗⚑ flag

   Mailchimp✓fullclaimed8/10

   Mailchimp exposes well-documented REST APIs (Marketing API, Transactional/Mandrill API, Commerce API) with concrete endpoint-level documentation (contacts, campaigns, SMS, routes) suitable for programmatic/AI-driven control. Missing for 10: independent third-party corroboration of API robustness/rate limits for automated agent use, and no evidence of official SDKs or AI-specific tooling beyond raw REST docs.

   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
   • [claimed-docs] “Send a new SMS message through Mandrill”
   • [claimed-docs] “Add a new route to an inbound domain or SMS program. Provide either domain or phone (not both).”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Klaviyo
   Klaviyo~partialclaimed6/10

   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.”

   proof ↗⚑ flag

   Mailchimp—none0/10

   No evidence of scoped or least-privilege API key/credential issuance for AI agents; Mailchimp docs only describe standard API endpoints for campaigns, contacts, and transactional email with no mention of granular permission scopes or agent-specific credential management.

   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [claimed-docs] “Send a new SMS message through Mandrill”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Klaviyo
   Klaviyo✓fullclaimed8/10

   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.”

   proof ↗⚑ flag

   Mailchimp—none0/10

   Evidence shows Mailchimp's Marketing and Transactional REST APIs and endpoint documentation, but nowhere does it mention official client SDKs/libraries for building against these APIs. Missing for 10: any mention of official SDKs in specific languages, SDK repos, or versioned client libraries.

   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [claimed-docs] “Send a new SMS message through Mandrill”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Klaviyo—none0/10

   The evidence pack contains no mention of webhooks or event subscription mechanisms—only API key auth, SDKs, sandbox testing, and an MCP server for AI agents. Missing for 10: any documentation of a webhooks API, event subscription endpoints, or push-notification mechanism.

   ⚑ flag

   Mailchimp—none0/10

   No evidence pack item mentions webhooks or event subscription mechanisms for Mailchimp; only API endpoints for campaigns, contacts, and transactional sending are documented. Absence of evidence for this applicable API capability yields 'none'. missing for 10: webhook documentation, event subscription setup, webhook payload/event types.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Mailchimp
   Klaviyo—none0/10

   The 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”

   proof ↗⚑ flag

   Mailchimp~partialclaimed5/10

   Mailchimp's marketing pages list 'Predictive Segmentation', 'Generative AI features', and 'Actionable insights into audience growth and conversion funnels', suggesting some AI-driven analytics/suggestions exist inside the product, but these are thin pricing-page bullet points with no detailed documentation of how insights are generated or surfaced. Missing for 10: first-party docs explaining the AI insight/suggestion features in depth, independent/hands-on evidence confirming these work as described, and concrete examples of generated insights.

   • [claimed-docs] “Multivariate and A/B Testing”
   • [claimed-docs] “Predictive Segmentation”
   • [claimed-docs] “Generative AI features”
   • [claimed-docs] “Actionable insights into audience growth and conversion funnels”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Klaviyo
   Klaviyo~partialclaimed5/10

   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.””

   proof ↗⚑ flag

   Mailchimp~partialclaimed3/10

   Evidence shows only that RSS campaigns send on a schedule and that the Marketing/Transactional APIs allow event-driven, API-triggered messages, which implies some autonomous background behavior, but there is no direct documentation of Mailchimp's automation/journey-builder feature or AI-native automation setup. Missing for 10: explicit documentation of the Customer Journey/automation builder, evidence of AI-driven or agent-configurable automation setup, and independent confirmation that automations run reliably unattended.

   • [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Mailchimp
   Klaviyo—none0/10

   Evidence 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”

   proof ↗⚑ flag

   Mailchimp~partialclaimed3/10

   The pricing page lists 'Generative AI features' as an included capability, suggesting some AI assistance exists, but there is no documentation describing a built-in assistant that can be delegated tasks (e.g., autonomously drafting/sending campaigns, managing audiences) rather than just generating content snippets. missing for 10: concrete docs on an AI assistant's task scope, autonomy/delegation workflow, and independent/hands-on confirmation it functions as an agent rather than a content-suggestion tool.

   • [claimed-docs] “Generative AI features”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Klaviyo
   Klaviyo~partialprobed6/10

   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”

   proof ↗⚑ flag

   Mailchimp—none0/10

   Evidence shows only traditional REST/API endpoints and generic 'Generative AI features' mention, with no natural-language command interface, chat/agent UI, or NL-to-action capability documented. No evidence of an AI assistant that lets users operate Mailchimp via conversational commands.

   • [claimed-docs] “Generative AI features”
   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Klaviyo
   Klaviyo~partialclaimed5/10

   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.”

   proof ↗⚑ flag

   Mailchimp—none0/10

   Evidence only shows standard API reference pages listing endpoints (create contact, send campaign, etc.) with no mention of an interactive console, runnable code samples, or try-it-now sandbox features expected for an AI-native exploratory API reference.

   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
   • [claimed-docs] “Send a new SMS message through Mandrill”
   • [claimed-docs] “Requests an additional dedicated IP for your account. Accounts may have one outstanding request at any time, and provisioning requests are p…”
   • [claimed-docs] “Add a new route to an inbound domain or SMS program. Provide either domain or phone (not both).”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Klaviyo—none0/10

   Klaviyo'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”

   proof ↗⚑ flag

   Mailchimp—none0/10

   The evidence pack shows Mailchimp's developer docs describe API endpoints (Marketing, Transactional) but never mentions an OpenAPI/Swagger spec or any downloadable machine-readable schema; the only spec-like artifact found is an llms.txt content summary, not an API spec. Missing for 10: explicit OpenAPI/Swagger file, published schema download link, or documentation referencing machine-readable spec format.

   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://mailchimp.com/llms.txt # Mailchimp - Complete Web Content Analysis > Comprehensive analysis and documen…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Klaviyo
   Klaviyo✓fullclaimed7/10

   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.”

   proof ↗⚑ flag

   Mailchimp—none0/10

   No evidence of a sandbox/test environment or test API keys for Mailchimp's API; docs only describe production endpoints (campaigns, contacts, transactional sends) with no mention of a sandbox mode. Missing for 10: any documentation of a sandbox/test environment, test API keys, or dry-run mode that avoids touching production data.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Klaviyo—none0/10

   The evidence pack covers authentication, SDKs, sandbox testing, and MCP server support, but contains no mention of API versioning scheme or a documented deprecation policy anywhere in the docs excerpts provided.

   ⚑ flag

   Mailchimp—none0/10

   Evidence confirms Mailchimp has Marketing, Transactional, and Commerce APIs with documented endpoints, but nothing in the pack describes API versioning scheme or a deprecation policy for AI-native reliability; community evidence even shows abrupt, unannounced account/API access shutdowns, undermining trust in predictable API lifecycle.

   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
   • [community] “A similar thing happened to me while using their Mandrill system. After years of using it with no issues, all of a sudden no emails were get…”
   • [community] “Someone sent a marketing email another customer complained about (just one complaint) and Mailchimp silently shut off our incoming email pro…”

   proof ↗⚑ flag

Api metrics

1. developerPull campaign and flow performance metrics through the API into my own warehouse or dashboards

   weight 2 · round drawn
   Klaviyo—none0/10

   The 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.”

   proof ↗⚑ flag

   Mailchimp—none0/10

   The evidence pack shows Mailchimp has a general Marketing API (contacts, campaign send, transactional email) but contains no documentation of report/analytics endpoints for pulling campaign or automation (flow) performance metrics into an external warehouse or dashboard. Missing for 10: explicit reports/analytics API endpoints, examples of exporting campaign/flow metrics, and any dashboard/warehouse integration evidence.

   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
   • [claimed-docs] “Actionable insights into audience growth and conversion funnels”

   proof ↗⚑ flag

Attribution

1. founderAttribute signups or revenue to specific emails and flows, not just opens and clicks

   weight 2 · round drawn
   Klaviyo—none0/10

   No evidence in the pack addresses revenue/signup attribution to specific emails or flows, conversion tracking, or attribution reporting features; documentation only covers API auth, SDKs, MCP server, and pricing tiers.

   ⚑ flag

   Mailchimp—none0/10

   The evidence pack only shows generic marketing/API docs and vague analytics claims (e.g., 'actionable insights into audience growth and conversion funnels', 'predictive segmentation') with no documentation of revenue/signup attribution tied to specific emails or automation flows. No reporting feature, e-commerce revenue-per-campaign dashboard, or flow-level conversion tracking is evidenced.

   • [claimed-docs] “Actionable insights into audience growth and conversion funnels”
   • [claimed-docs] “Predictive Segmentation”

   proof ↗⚑ flag

Reporting core

1. marketerRead opens, clicks, unsubscribes, and conversions per campaign and per automation step, over time

   weight 3 · round to Mailchimp
   Klaviyo—none0/10

   The 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.

   ⚑ flag

   Mailchimp~partialclaimed3/10

   The evidence only vaguely gestures at analytics ('actionable insights into audience growth and conversion funnels') without any documentation of per-campaign or per-automation-step reporting on opens, clicks, unsubscribes, or conversions over time. Missing for 10: campaign report API/dashboard details, automation-step-level analytics, time-series breakdowns, and independent corroboration that these metrics are accessible and reliable.

   • [claimed-docs] “Actionable insights into audience growth and conversion funnels”

   proof ↗⚑ flag

Agent segments

1. 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 Klaviyo
   Klaviyo~partialprobed4/10

   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”

   proof ↗⚑ flag

   Mailchimp—none0/10

   The evidence pack shows generic Marketing API capabilities (create contacts, send campaigns) and mentions 'Predictive Segmentation' as a paid feature, but there is no documentation of an API endpoint or agent-facing surface that translates a plain-language audience description into a concrete segment. Missing for 10: any segment-creation API reference, any NL-to-criteria translation mechanism, and any example of an agent invoking this programmatically.

   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [claimed-docs] “Predictive Segmentation”
   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”

   proof ↗⚑ flag

Api contacts

1. developerCreate, update, and suppress contacts with custom properties through the API at production scale

   weight 3 · round to Klaviyo
   Klaviyo~partialclaimed5/10

   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.”

   proof ↗⚑ flag

   Mailchimp~partialcommunity3/10

   Docs confirm a Marketing API contact-creation endpoint ('Create a new omni-channel contact for an audience') and general API access to custom app data, but the pack lacks any explicit documentation of update or suppression (unsubscribe/cleaned) endpoints, custom merge-field schemas, or batch/production-scale operations. Community reports of accounts being banned, contacts wiped, and automated API/browser access blocked (e.g., dev-tools-triggered bans) raise real doubts about reliability of sustained programmatic contact management at scale. Missing for 10: documented update/suppress endpoints, custom property/merge-field API docs, evidence of bulk/batch operations, and independent confirmation of stable production-scale API usage.

   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [community] “MailChimp deleted my account with no warning after a period of inactivity, giving no notice, and support offered no path to recover the mail…”
   • [community] “MailChimp removed half my users from a mailing list claiming lots of unverified sign-ups and spam complaints, even though the sign-ups were …”
   • [community] “MailChimp blacklists your IP if you open the browser's dev tools; as a developer who often has devtools open, I get banned from Mailchimp fo…”
   • [community] “I had to use their drag-and-drop email builder because a non-dev would edit it; when a Code module became inaccessible via UI, I tried injec…”

   proof ↗⚑ flag

Api segments

1. developerCreate and update segments, tags, or lists programmatically and read back exactly who is in them

   weight 3 · round drawn
   Klaviyo—none0/10

   The 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…”

   proof ↗⚑ flag

   Mailchimp—none0/10

   The evidence pack only shows generic mentions of Mailchimp's Marketing API and a single endpoint for creating a contact (mailchimp-docs-4), with no documentation of segment, tag, or list CRUD operations or reading back exact membership. Missing for 10: explicit API endpoints for creating/updating segments or tags, listing/reading segment membership, and any developer or hands-on confirmation that programmatic read-back works as described.

   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Create a new omni-channel contact for an audience.”

   proof ↗⚑ flag

Segment core

1. marketerBuild audience segments from profile attributes, tags, and behavioral events, and they stay live as data changes

   weight 3 · round to Mailchimp
   Klaviyo~partialclaimed3/10

   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”

   proof ↗⚑ flag

   Mailchimp~partialclaimed4/10

   Evidence shows Mailchimp offers 'Predictive Segmentation' and audience growth insights, and the Marketing API supports contact creation and custom data ingestion, which implies segmentation capability, but no direct documentation describes building segments from tags or behavioral events or confirms segments update live as data changes. missing for 10: explicit docs on tag-based segmentation, event-based triggers, and dynamic/live segment updating.

   • [claimed-docs] “Predictive Segmentation”
   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [claimed-docs] “Actionable insights into audience growth and conversion funnels”
   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Mailchimp
   Klaviyo—none0/10

   The 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…”

   proof ↗⚑ flag

   Mailchimp!disputedcontradicted4/10

   Mailchimp's Marketing API allows creating/sending campaigns and contacts (mailchimp-docs-1, mailchimp-docs-4, mailchimp-docs-5), implying some bulk-capable API surface, but there is no documented batch/bulk-specific endpoint in the evidence, and multiple hands-on reports show that performing bulk operations like migrating or importing large contact lists triggered account bans or data loss (mailchimp-comm-3, mailchimp-comm-6), directly contradicting reliable bulk-operation support. missing for 10: explicit batch API documentation, evidence of successful large-scale bulk imports/exports, and independent confirmation that bulk workflows don't trigger account suspension.

   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
   • [community] “They banned me after migrating an email list over because they said I couldn't confirm how I got the emails, even though they were legitimat…”
   • [community] “MailChimp removed half my users from a mailing list claiming lots of unverified sign-ups and spam complaints, even though the sign-ups were …”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Mailchimp
   Klaviyo~partialclaimed3/10

   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”

   proof ↗⚑ flag

   Mailchimp~partialclaimed4/10

   Mailchimp’s Transactional API supports event-driven messaging (mailchimp-docs-2) and the Marketing API can trigger campaign sends via API calls, suggesting some rule/event-based automation capability, but no evidence describes a dedicated 'automation rules' or 'journey builder' engine that lets users define custom trigger-action logic. missing for 10: explicit documentation of a rule-builder/automation-journey feature, examples of user-defined trigger conditions, and independent confirmation that such automations work reliably.

   • [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
   • [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Klaviyo~partialclaimed3/10

   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.””

   proof ↗⚑ flag

   Mailchimp~partialclaimed3/10

   The only recurring-schedule evidence is RSS campaigns that send 'according to its schedule' (mailchimp-docs-5); all other campaigns send immediately, and there is no documentation of an API or workflow engine (e.g., Customer Journeys automation) for AI-native users to configure arbitrary recurring jobs. Missing for 10: explicit automation/workflow API docs, recurring-trigger configuration beyond RSS, and any independent confirmation of automation reliability.

   • [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Klaviyo—none0/10

   No evidence of versioning, review workflows, or rollback capability for Klaviyo automations/flows; docs cover API auth, SDKs, sandbox testing, and MCP server but nothing about automation version history or revert functionality.

   ⚑ flag

   Mailchimp—none0/10

   No evidence of automation versioning, review workflows, or rollback capability in Mailchimp's docs or API; only campaign creation/sending and unrelated API features are documented. missing for 10: version history for automations, diff/review UI, rollback/restore functionality, audit trail of automation changes.

   • [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
   • [claimed-docs] “Multivariate and A/B Testing”
   • [claimed-docs] “Predictive Segmentation”

   proof ↗⚑ flag

Agent campaigns

1. 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 Klaviyo
   Klaviyo~partialclaimed4/10

   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.””

   proof ↗⚑ flag

   Mailchimp—none0/10

   The evidence shows only that the Marketing API can create campaigns and send them (with immediate send noted explicitly in mailchimp-docs-5), but there is no evidence of a scheduling/queuing mechanism that lets an agent draft a campaign and leave it pending for human approval before it goes out. No API endpoint, workflow, or documentation describing draft/approval states is present in the evidence pack.

   • [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”

   proof ↗⚑ flag

Api campaigns

1. developerCreate and schedule a campaign or broadcast entirely through a documented public API, without touching the dashboard

   weight 3 · round to Klaviyo
   Klaviyo~partialclaimed6/10

   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.”

   proof ↗⚑ flag

   Mailchimp~partialclaimed5/10

   Mailchimp's Marketing API docs confirm creating audience contacts and sending campaigns via API (mailchimp-docs-4, mailchimp-docs-5), showing the core send-via-API capability exists, but the cited evidence only describes immediate sending or RSS-based scheduling, not a general 'schedule campaign' endpoint or full campaign-creation-to-send workflow purely via API. Missing for 10: explicit documented schedule-campaign endpoint, full campaign creation API details, and independent/developer corroboration that the entire flow works without dashboard use.

   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”

   proof ↗⚑ flag

Campaign core

1. marketerCompose an email campaign, pick its audience, and send or schedule it — the arena's table-stakes loop

   weight 3 · round drawn
   Klaviyo✓fullclaimed7/10

   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.”

   proof ↗⚑ flag

   Mailchimp✓fullcommunity7/10

   Docs show core loop elements: creating audience contacts (docs-4), sending campaigns with scheduling support for RSS campaigns (docs-5), and email design/testing tools (docs-9, docs-14) — this is Mailchimp's flagship product function. Missing for 10: explicit first-party documentation of scheduled (non-RSS) send-later flow and independent hands-on confirmation of a full compose-audience-send cycle; some community reports (mailchimp-comm-12) note deliverability issues on lower tiers that add minor quality risk.

   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
   • [claimed-docs] “Multivariate and A/B Testing”
   • [claimed-docs] “Design better emails”
   • [community] “I tried Mailchimp's free tier a few years ago; everything was great except the email servers had terrible reputation and most of what I sent…”

   proof ↗⚑ flag

Experiments

1. marketerA/B test subject lines or content variants and have the winner picked from real engagement

   weight 2 · round to Mailchimp
   Klaviyo—none0/10

   None 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.

   ⚑ flag

   Mailchimp~partialclaimed5/10

   Mailchimp's pricing page lists 'Multivariate and A/B Testing' as a feature, confirming the capability exists, but the evidence pack lacks any documentation detailing automatic winner selection based on real engagement metrics (open/click rates) or how variants are configured. missing for 10: first-party docs describing the A/B test setup, winning-criteria selection (opens/clicks/revenue), and automatic winner send-out; independent/hands-on confirmation the feature works as described.

   • [claimed-docs] “Multivariate and A/B Testing”

   proof ↗⚑ flag

Deliverability signals

1. marketerSee bounce, complaint, and blocklist signals per send and get actionable guidance when deliverability degrades

   weight 2 · round drawn
   Klaviyo—none0/10

   No 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.

   ⚑ flag

   Mailchimp—none0/10

   The evidence pack contains no documentation of per-send bounce/complaint/blocklist reporting or actionable deliverability guidance—only generic API descriptions, pricing feature bullets, and community complaints about account bans and poor sender reputation, none of which describe the specific reporting/guidance capability the story asks for.

   • [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
   • [claimed-docs] “Requests an additional dedicated IP for your account. Accounts may have one outstanding request at any time, and provisioning requests are p…”
   • [community] “Someone sent a marketing email another customer complained about (just one complaint) and Mailchimp silently shut off our incoming email pro…”
   • [community] “I tried Mailchimp's free tier a few years ago; everything was great except the email servers had terrible reputation and most of what I sent…”

   proof ↗⚑ flag

Domain auth

1. ops userAuthenticate my own sending domain — SPF, DKIM, DMARC alignment — with guided DNS setup and verification

   weight 3 · round drawn
   Klaviyo—none0/10

   No evidence pack items address sending-domain authentication (SPF/DKIM/DMARC) or guided DNS setup/verification; all evidence covers API keys, OAuth, SDKs, MCP server, and pricing tiers, which are unrelated to this axis.

   ⚑ flag

   Mailchimp—none0/10

   The evidence pack contains no documentation about domain authentication, SPF/DKIM/DMARC setup, or guided DNS verification flows — only unrelated API docs, pricing feature lists, and community complaints. Missing for 10: any docs or hands-on evidence of domain authentication UI, DNS record generation, or verification status checks.

   ⚑ flag

Suppression

1. ops userUnsubscribes, bounces, and spam complaints are suppressed automatically and honored across every send type — CAN-SPAM/GDPR hygiene by default

   weight 3 · round drawn
   Klaviyo—none0/10

   None 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.

   ⚑ flag

   Mailchimp—none0/10

   No evidence in the pack documents Mailchimp's suppression list, bounce/complaint handling, or cross-send-type unsubscribe enforcement; docs cited are about API endpoints, pricing tiers, and unrelated features. Community evidence discusses account bans and deliverability reputation issues but does not confirm or deny automatic suppression hygiene, so absence of applicable evidence yields 'none'.

   ⚑ flag

First party integrations

1. 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 drawn
   Klaviyo—none0/10

   The evidence pack only shows generic API/OAuth/SDK capabilities and a flexible schema, but contains no mention of maintained first-party integrations with Shopify, Stripe, Segment, or a product database — the specific connectors the story asks about.

   ⚑ flag

   Mailchimp—none0/10

   The evidence pack only shows generic Marketing/Transactional APIs and an open-source commerce stack, but contains no mention of maintained first-party integrations with Stripe, Shopify, Segment, or product databases. Missing for 10: explicit Stripe integration docs, Shopify integration docs, Segment/CDP integration docs, and any customer/database sync integration evidence.

   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Mailchimp Open Commerce (formerly Reaction Commerce) is an open source, API-first, modular commerce stack made for technical, growth-minded …”

   proof ↗⚑ flag

Webhooks

1. developerSubscribe webhooks to delivery and engagement events — sends, opens, clicks, bounces, unsubscribes — with a documented, signed payload

   weight 3 · round drawn
   Klaviyo—none0/10

   No 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.

   ⚑ flag

   Mailchimp—none0/10

   The evidence pack includes only general Marketing/Transactional API descriptions and community complaints, with no mention of webhook subscriptions, event types (opens, clicks, bounces, unsubscribes), or signed payload verification. Absence of evidence for this applicable integrations axis means it cannot be credited as delivered.

   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”

   proof ↗⚑ flag

Automation core

1. marketerBuild multi-step lifecycle automations — welcome series, onboarding, winback — with branches, delays, and exit rules

   weight 3 · round to Klaviyo
   Klaviyo~partialclaimed4/10

   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”

   proof ↗⚑ flag

   Mailchimp—none0/10

   The evidence pack contains no documentation of Mailchimp's journey/automation builder, branching logic, delays, or exit rules — only generic API references (campaigns, transactional email, contacts) and pricing-page feature bullets (A/B testing, predictive segmentation, AI) that don't address multi-step lifecycle automations.

   ⚑ flag

Event triggers

1. developerFire a custom event from my product and have it trigger an automation for exactly that person

   weight 3 · round to Klaviyo
   Klaviyo~partialclaimed3/10

   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.”

   proof ↗⚑ flag

   Mailchimp—none0/10

   The evidence pack references Mailchimp's Marketing API pulling 'custom data' from apps and creating contacts, but nowhere documents a specific Events API or mechanism for firing a custom event that triggers a Customer Journey/automation for a single contact. Without an explicit events endpoint or automation-trigger documentation, there is no evidence this capability is delivered.

   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Create a new omni-channel contact for an audience.”

   proof ↗⚑ flag

Flow operations

1. ops userSee where any individual person sits inside an automation and pull or re-enter them without breaking the flow

   weight 2 · round drawn
   Klaviyo—none0/10

   No 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.

   ⚑ flag

   Mailchimp—none0/10

   No evidence describes Customer Journey Builder subscriber-level visibility, or the ability to locate a specific contact within an automation and pull/re-enter them without disrupting the flow; docs only cover general API/campaign features. Missing for 10: journey/automation visual map showing contact position, per-contact pull/remove/re-entry controls, documentation or hands-on confirmation that this doesn't break the automation state.

   ⚑ flag

Export

1. founderExport my entire audience — contacts, custom fields, tags, engagement history, and suppression list — in an open format, self-serve

   weight 3 · round drawn
   Klaviyo—none0/10

   The 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”

   proof ↗⚑ flag

   Mailchimp—none0/10

   The evidence pack contains no documentation of a self-serve export feature covering contacts, custom fields, tags, engagement history, and suppression list in an open format — API docs cover creating contacts and sending campaigns, not exporting. Community reports actually describe cases where audience data could not be self-serve recovered after account issues (mailchimp-comm-1, mailchimp-comm-2), reinforcing the absence of a documented reliable export path. missing for 10: no first-party docs on CSV/data export, no mention of engagement history or suppression list export, no confirmation of open-format guarantee.

   • [community] “MailChimp deleted my account with no warning after a period of inactivity, giving no notice, and support offered no path to recover the mail…”
   • [community] “I had a mailing list with them removed with all contacts lost and account banned without notification. Support falsely claimed data was wipe…”
   • [claimed-docs] “Create a new omni-channel contact for an audience.”

   proof ↗⚑ flag

Import migration

1. marketerMigrate in from another email platform with guided list import that preserves tags, custom fields, and unsubscribe state

   weight 2 · round to Mailchimp
   Klaviyo—none0/10

   Evidence 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”

   proof ↗⚑ flag

   Mailchimp~partialclaimed2/10

   Mailchimp's marketing site references a 'Switch from another tool' migration feature, but the evidence pack contains no documentation or hands-on detail confirming that tags, custom fields, or unsubscribe state are actually preserved during import. missing for 10: detailed migration/import API or guide docs, evidence of tag/custom-field mapping, evidence of unsubscribe-state preservation, independent confirmation of successful migrations.

   • [claimed-docs] “Switch from another tool”

   proof ↗⚑ flag

Agent access

1. 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 Klaviyo
   Klaviyo~partialprobed6/10

   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”

   proof ↗⚑ flag

   Mailchimp~partialclaimed5/10

   Mailchimp's Marketing API (mailchimp-docs-1, mailchimp-docs-4, mailchimp-docs-5) confirms programmatic access to audiences/contacts and campaign sending, implying an API surface an agent could query, but the evidence pack contains no explicit endpoints for automations or campaign performance/reports data, nor any AI-agent/MCP integration proof. Missing for 10: documented reporting/analytics endpoints, automation-status endpoints, and evidence of an agent actually consuming this data end-to-end.

   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”

   proof ↗⚑ flag

Api access

1. developerRead per-person engagement history — what was sent, opened, clicked — through the API for any contact

   weight 3 · round drawn
   Klaviyo—none0/10

   No evidence pack items reference an events/metrics API, per-profile activity/timeline endpoint, or any way to retrieve sent/opened/clicked history for a contact — only general API overview, SDKs, campaign creation, and MCP server docs are cited.

   ⚑ flag

   Mailchimp—none0/10

   Evidence shows generic Marketing API endpoints for creating contacts and sending campaigns, but no documentation of an endpoint or object returning per-contact engagement history (sent/opened/clicked activity log) via the API. Mailchimp does have an 'activity' endpoint in reality, but no evidence pack item mentions it, so per the rules absence must be judged as none. missing for 10: any docs referencing a contact activity/engagement history endpoint, example response showing opens/clicks/sends per contact, independent confirmation of this API capability.

   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”

   proof ↗⚑ flag

Scoped access

1. 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 Klaviyo
   Klaviyo~partialclaimed6/10

   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.”

   proof ↗⚑ flag

   Mailchimp—none0/10

   No evidence of API key scoping or read-only/permission-restricted credentials in Mailchimp's docs; the only API key model referenced is a single full-access account key with no mention of granular scopes for analytics-only or contractor access. Missing for 10: any documentation of scoped/read-only API keys, role-based API access, or OAuth scopes limiting an agent to analytics without send permission.

   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round drawn
   Klaviyo~partialclaimed5/10

   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”

   proof ↗⚑ flag

   Mailchimp~partialcommunity5/10

   Mailchimp exposes a fairly complete Marketing API (contacts, campaigns, sending) and a separate Transactional API, showing broad coverage of core UI actions, but there is no first-party claim of full UI/API parity, and community evidence suggests some UI-only features (e.g., the drag-and-drop email builder's advanced editing) are not fully replicable via API/inspector access. missing for 10: explicit vendor statement of full API/UI parity, evidence that advanced design/template features available in the UI builder are fully scriptable via API, independent confirmation of parity across all account/admin settings.

   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
   • [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
   • [community] “I had to use their drag-and-drop email builder because a non-dev would edit it; when a Code module became inaccessible via UI, I tried injec…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Mailchimp
   Klaviyo—none0/10

   Klaviyo 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.

   ⚑ flag

   Mailchimp!disputedcontradicted3/10

   Mailchimp's Marketing API allows programmatic access to contacts/campaigns (mailchimp-docs-4), which could support data export, but there's no documented bulk/open-format export-and-leave feature, and community reports describe accounts being banned or deleted with contact lists lost entirely, support falsely claiming data was wiped, and only providing a data dump under public pressure — directly contradicting a smooth 'export all my data and leave' experience. Missing for 10: an official bulk export/data-portability doc, an open standard export format, and confirmation that account closure preserves user access to their data.

   • [claimed-docs] “Create a new omni-channel contact for an audience.”
   • [community] “MailChimp deleted my account with no warning after a period of inactivity, giving no notice, and support offered no path to recover the mail…”
   • [community] “I had a mailing list with them removed with all contacts lost and account banned without notification. Support falsely claimed data was wipe…”
   • [community] “MailChimp removed half my users from a mailing list claiming lots of unverified sign-ups and spam complaints, even though the sign-ups were …”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Klaviyo—none0/10

   No 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.

   ⚑ flag

   Mailchimp—none0/10

   No evidence pack items mention data residency, region selection, or geographic storage controls for Mailchimp; the docs focus on API features and pricing tiers, not data location controls. Missing for 10: any documentation of region/residency selection, data center choice, or geographic storage controls.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Klaviyo—none0/10

   No evidence in the pack addresses AI-training data usage policies, opt-outs, or any statement about whether customer data is used to train AI/ML models. missing for 10: explicit AI-training data policy, opt-out mechanism, any privacy/DPA statement about model training.

   ⚑ flag

   Mailchimp—none0/10

   No evidence in the pack addresses AI-training opt-out or data-use controls for Mailchimp; the evidence is limited to product feature descriptions and unrelated account-management/community complaints. Missing for 10: any documentation of an AI-training opt-out setting, privacy policy language on model training, or admin controls to exclude data from AI/ML use.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Klaviyo—none0/10

   No evidence pack items address data retention policies, deletion controls, or export/erasure mechanisms; only API scoping and general auth/testing docs are provided, which don't speak to retention/deletion controls.

   ⚑ flag

   Mailchimp—none0/10

   No documentation is provided showing Mailchimp gives AI-native users explicit APIs or settings to control data retention/deletion policies; the evidence pack only covers marketing/API features unrelated to retention controls. Community reports actually describe Mailchimp unilaterally deleting accounts and data without user consent or recourse, further indicating the user lacks control over retention/deletion.

   • [community] “MailChimp deleted my account with no warning after a period of inactivity, giving no notice, and support offered no path to recover the mail…”
   • [community] “I had a mailing list with them removed with all contacts lost and account banned without notification. Support falsely claimed data was wipe…”
   • [community] “We wanted to pause our paid MailChimp account and return to free tier, but they said there was no way to do that — you either keep paying or…”

   proof ↗⚑ flag

Ai content

1. marketerHave the platform's built-in AI draft or refine subject lines and email copy from a brief, inside the composer

   weight 2 · round drawn
   Klaviyo—none0/10

   Evidence 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”

   proof ↗⚑ flag

   Mailchimp—none0/10

   The evidence pack only mentions 'Generative AI features' as a pricing line item with no description of composer-integrated subject line/copy drafting from a brief, and no docs or hands-on confirmation of this specific workflow. missing for 10: documentation or demo of AI subject-line/copy generation inside the composer, any first-party feature description, independent/hands-on confirmation it works as described.

   • [claimed-docs] “Generative AI features”

   proof ↗⚑ flag

Editor

1. marketerDesign on-brand emails with a visual editor, reusable templates, and personalization tokens that render correctly across clients

   weight 2 · round to Klaviyo
   Klaviyo~partialclaimed4/10

   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.”

   proof ↗⚑ flag

   Mailchimp~partialcommunity3/10

   Only a generic marketing-site blurb ('Design better emails') hints at a visual editor, with no documentation of reusable templates, personalization/merge tags, or cross-client rendering testing; one community report also describes the drag-and-drop/CKText editor failing to load, undermining reliability. missing for 10: docs on template library, merge-tag personalization, cross-client rendering QA, and independent corroboration of editor quality.

   • [claimed-docs] “Design better emails”
   • [community] “I used ChatGPT to get a refund from Mailchimp when their CKText editor failed to load on International Women's Day, preventing sending an em…”
   • [community] “I had to use their drag-and-drop email builder because a non-dev would edit it; when a Code module became inaccessible via UI, I tried injec…”

   proof ↗⚑ flag

Templates as code

1. developerManage email templates as code — HTML/MJML or API-managed templates with variable substitution — under version control

   weight 2 · round drawn
   Klaviyo—none0/10

   Evidence 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”

   proof ↗⚑ flag

   Mailchimp—none0/10

   The evidence pack contains no documentation of Mailchimp's Templates API, HTML/MJML template management, merge-tag variable substitution, or any version-control workflow for templates; only general marketing API mentions are present. Missing for 10: Templates API docs, variable/merge-tag substitution details, MJML/HTML support, version-control integration examples.

   • [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
   • [claimed-docs] “Create a new omni-channel contact for an audience.”

   proof ↗⚑ flag

Transactional api

1. developerSend one-to-one transactional email — receipts, magic links, notifications — through the same platform's API alongside marketing sends

   weight 3 · round to Mailchimp
   Klaviyo—none0/10

   Evidence 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…”

   proof ↗⚑ flag

   Mailchimp~partialcommunity5/10

   Mailchimp Transactional (formerly Mandrill) provides API/SMTP-based transactional sending (receipts, event-driven messages) per docs-2, docs-6, docs-7, docs-8, satisfying the core capability, but it is a separate product with its own distinct API endpoint rather than truly unified with the Marketing API, and community reports confirm it was never fully integrated post-acquisition (mailchimp-comm-8) and has suffered abrupt, unexplained shutdowns of transactional sending (mailchimp-comm-4, mailchimp-comm-5). missing for 10: evidence of a single unified API/dashboard combining marketing and transactional sends, and confirmation of reliable uptime for transactional messages without account suspension risk.

   • [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
   • [claimed-docs] “Send a new SMS message through Mandrill”
   • [claimed-docs] “Requests an additional dedicated IP for your account. Accounts may have one outstanding request at any time, and provisioning requests are p…”
   • [claimed-docs] “Add a new route to an inbound domain or SMS program. Provide either domain or phone (not both).”
   • [community] “Some years ago MailChimp decided to act as a cash cow, invest very little except a recent redesign. Mandrill still isn't integrated after th…”
   • [community] “A similar thing happened to me while using their Mandrill system. After years of using it with no issues, all of a sudden no emails were get…”
   • [community] “Someone sent a marketing email another customer complained about (just one complaint) and Mailchimp silently shut off our incoming email pro…”

   proof ↗⚑ flag

Transactional hygiene

1. 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 Mailchimp
   Klaviyo—none0/10

   Klaviyo 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.

   ⚑ flag

   Mailchimp~partialcommunity4/10

   Mailchimp Transactional (Mandrill) is documented as a distinct product with its own API/SMTP, dedicated IPs, and routing separate from the Marketing API, which supports the general premise of separated transactional infrastructure. However, there is no direct evidence that transactional sends bypass marketing suppression/unsubscribe lists or that templates are kept fully separate, and community reports (e.g., Mandrill sends being silently shut off after a single complaint, poor integration between the two products) suggest the separation is imperfect and reputation is fragile rather than cleanly isolated. Missing for 10: explicit documentation of suppression-list independence for transactional sends, confirmation that unsubscribed marketing contacts still receive transactional receipts, and evidence of fully separate templates/reputation management.

   • [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
   • [claimed-docs] “Send a new SMS message through Mandrill”
   • [claimed-docs] “Requests an additional dedicated IP for your account. Accounts may have one outstanding request at any time, and provisioning requests are p…”
   • [claimed-docs] “Add a new route to an inbound domain or SMS program. Provide either domain or phone (not both).”
   • [community] “A similar thing happened to me while using their Mandrill system. After years of using it with no issues, all of a sudden no emails were get…”
   • [community] “Someone sent a marketing email another customer complained about (just one complaint) and Mailchimp silently shut off our incoming email pro…”
   • [community] “Some years ago MailChimp decided to act as a cash cow, invest very little except a recent redesign. Mandrill still isn't integrated after th…”

   proof ↗⚑ flag