Customer.io vs Mailchimp

Agent access

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

   weight 2 · round to Customer.io
   Customer.io✓fullprobed9/10

   A probe confirms a working llms.txt at docs.customer.io/llms.txt returning structured documentation content, and Customer.io also publishes agent-oriented docs like the MCP get-started guide and CLI/skills for AI assistants. missing for 10: no independent third-party report of an agent successfully consuming llms.txt in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.customer.io/llms.txt # Customer.io Documentation > Customer.io is a messaging automation platform …”
   • [claimed-docs] “Install the CLI and the skills that teach your AI assistant to use it”
   • [claimed-docs] “List all active automations in my workspace.”
   • [probe] “official MCP server documented at https://docs.customer.io/ai/mcp/get-started/”

   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 Customer.io
   Customer.io~partialprobed6/10

   Customer.io exposes a documented CLI, REST APIs (Track/Pipelines), an OpenAPI spec, and Postman collection, all of which allow scripting/automation outside the UI — the core building blocks for headless/CI use. However, there is no explicit documentation or example of running these in a CI pipeline (e.g., auth/token setup for automated jobs, CI examples, idempotent scripting patterns), so headless-in-CI is inferred rather than directly evidenced. Missing for 10: explicit CI/pipeline integration docs or examples, authentication guidance for automated/headless contexts, and independent confirmation of CLI use outside interactive sessions.

   • [claimed-docs] “Install the CLI and the skills that teach your AI assistant to use it”
   • [claimed-docs] “To get data into Customer.io, use an SDK or the Pipelines API. This is the API that most of our integrations are based on and likely the API…”
   • [claimed-docs] “Our Track API provides ways to send real-time customer data to your Customer.io workspace including customer identification and event tracki…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.customer.io/openapi.json — contains "openapi" key”
   • [claimed-docs] “We've generated a Postman collection to help you get started with our APIs.”

   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 Customer.io
   Customer.io✓fullprobed8/10

   Customer.io publishes an official MCP server (docs.customer.io/ai/mcp/get-started/) that lets an agent list automations, draft emails in Design Studio, and separates reads from writes/deletes for approval control, confirmed by a live probe of the docs page. Missing for 10: independent/hands-on third-party confirmation that the MCP server works as documented and broader detail on setup/auth steps.

   • [claimed-docs] “List all active automations in my workspace.”
   • [claimed-docs] “Reads are separated from writes and deletes... so you can approve each category independently.”
   • [claimed-docs] “Draft a welcome email in Design Studio.”
   • [probe] “official MCP server documented at https://docs.customer.io/ai/mcp/get-started/”

   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 to Customer.io
   Customer.io~partialclaimed5/10

   Docs explicitly mention installing 'the CLI and the skills that teach your AI assistant to use it,' confirming an official CLI exists for AI-native workflows, but no further detail (commands, docs page, install instructions) or independent corroboration is provided. Missing for 10: dedicated CLI reference/docs page, example commands, and independent/hands-on confirmation of the CLI's use.

   • [claimed-docs] “Install the CLI and the skills that teach your AI assistant to use it”
   • [claimed-docs] “Your AI can do anything you'd do by clicking or typing in Customer.io. That means you can have it build automations, draft messages, analyze…”

   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 Customer.io
   Customer.io✓fullprobed9/10

   Customer.io publishes a documented public API (Track API, Pipelines API, Postman collection) confirmed live via OpenAPI spec probe, plus additional documented programmatic surfaces (CLI, MCP server) for AI-driven use. Missing for 10: independent third-party developer corroboration of API robustness/completeness beyond docs and probes.

   • [claimed-docs] “To get data into Customer.io, use an SDK or the Pipelines API. This is the API that most of our integrations are based on and likely the API…”
   • [claimed-docs] “Our Track API provides ways to send real-time customer data to your Customer.io workspace including customer identification and event tracki…”
   • [claimed-docs] “We've generated a Postman collection to help you get started with our APIs.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.customer.io/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.customer.io/llms.txt # Customer.io Documentation > Customer.io is a messaging automation platform …”
   • [claimed-docs] “Install the CLI and the skills that teach your AI assistant to use it”
   • [probe] “official MCP server documented at https://docs.customer.io/ai/mcp/get-started/”

   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 Customer.io
   Customer.io~partialprobed5/10

   The MCP integration separates reads from writes/deletes so users can approve each category independently, which is a form of scoped permissioning for agent actions, but there's no evidence of true API-key-level least-privilege credential issuance (e.g., scoped tokens, role-based API keys, or workspace-level permission scoping for agents) beyond this read/write approval gate. missing for 10: scoped API key/token generation, documented credential-level permission granularity, independent verification of the approval mechanism's enforcement.

   • [claimed-docs] “Reads are separated from writes and deletes... so you can approve each category independently.”
   • [probe] “official MCP server documented at https://docs.customer.io/ai/mcp/get-started/”
   • [claimed-docs] “List all active automations in my workspace.”

   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 Customer.io
   Customer.io~partialprobed6/10

   Customer.io documents official Track/Pipelines APIs and SDKs for ingesting data, backed by a Postman collection and machine-readable OpenAPI spec (docs-3, docs-6, docs-7, docs-8, probe-2), which supports building AI-native/agentic integrations. However, there's no explicit enumeration of language-specific SDKs (e.g., Node, Python, Java) or independent developer corroboration of SDK quality/completeness beyond one community complaint about lack of code-based flexibility (comm-3). Missing for 10: named list of official SDK languages/repos, independent hands-on corroboration of SDK usability, and versioning/maintenance details.

   • [claimed-docs] “To get data into Customer.io, use an SDK or the Pipelines API. This is the API that most of our integrations are based on and likely the API…”
   • [claimed-docs] “The Pipelines API natively supports objects and relationships through the /group endpoint.”
   • [claimed-docs] “Our Track API provides ways to send real-time customer data to your Customer.io workspace including customer identification and event tracki…”
   • [claimed-docs] “We've generated a Postman collection to help you get started with our APIs.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.customer.io/openapi.json — contains "openapi" key”
   • [community] “Developer built an open-source alternative 'after getting frustrated with Customer.io's limitations,' citing lack of code-based flexibility …”

   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
   Customer.io—none0/10

   The evidence pack contains no mention of a webhook subscription mechanism (e.g., outbound event notifications for opens, clicks, unsubscribes, etc.); it only covers inbound Track/Pipelines APIs, broadcasts, and the MCP server for AI agent actions. Webhooks are a plausible capability for a messaging platform like Customer.io, but nothing here documents or demonstrates the ability to subscribe to events via webhooks.

   ⚑ 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 drawn
   Customer.io~partialclaimed5/10

   Docs show a broader AI assistant that can 'analyze performance' and 'build automations' (docs-1) plus AI in Slack (docs-20) and AI-generated design elements (docs-15/16), suggesting some data-informed suggestions, but there's no dedicated analytics/insights feature that surfaces AI-generated observations or recommendations from customer data specifically. Missing for 10: a documented insights/analytics dashboard powered by AI, concrete examples of data-driven suggestions (e.g. segment or campaign optimization tips), and independent confirmation of this capability in practice.

   • [claimed-docs] “Your AI can do anything you'd do by clicking or typing in Customer.io. That means you can have it build automations, draft messages, analyze…”
   • [claimed-docs] “Use Customer.io AI in Slack”
   • [claimed-docs] “AI-generated global styles”
   • [claimed-docs] “Draft a welcome email in Design Studio.”

   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 Customer.io
   Customer.io✓fullclaimed8/10

   Customer.io's core product is journey/automation building that runs autonomously in the background, triggered by events or segment membership, independent of user presence (docs-12, docs-13, docs-18), and this can even be managed/listed via AI/MCP tooling (docs-9). This is well-documented first-party functionality central to the platform's purpose. Missing for 10: independent hands-on verification that automations run reliably at scale without manual intervention (community evidence only discusses unrelated outages/bugs, not automation autonomy specifically).

   • [claimed-docs] “You can trigger automations when profiles perform events, when they join Segments (e.g. they meet attribute conditions), and so on.”
   • [claimed-docs] “Broadcasts send a message to a list of recipients. Broadcast messages are queued to send to all the defined recipients at a time you specify…”
   • [claimed-docs] “Chain multiple delays together in a single _Wait Until_ block”
   • [claimed-docs] “List all active automations in my workspace.”
   • [claimed-docs] “If you go to the Segments page, you'll see segments like "Paying Customers", "Have not logged in recently" and "Unsubscribed".”

   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 Customer.io
   Customer.io~partialprobed6/10

   Customer.io documents a 'Customer.io AI' capable of building automations, drafting messages, and analyzing performance (docs-1, docs-16), with a Slack-based assistant interface (docs-20) and AI-generated design features (docs-15), suggesting some built-in assistant functionality. However, most detailed evidence describes this AI working through an external MCP server/CLI-skills setup (docs-2, docs-9, docs-10, probe-3) rather than a fully native in-product chat assistant, and there's no independent/hands-on confirmation of its reliability. Missing for 10: clear documentation of a native in-app assistant UI (vs. MCP/CLI-only access), and third-party corroboration of task delegation working well.

   • [claimed-docs] “Your AI can do anything you'd do by clicking or typing in Customer.io. That means you can have it build automations, draft messages, analyze…”
   • [claimed-docs] “Draft a welcome email in Design Studio.”
   • [claimed-docs] “Use Customer.io AI in Slack”
   • [claimed-docs] “AI-generated global styles”
   • [claimed-docs] “List all active automations in my workspace.”
   • [claimed-docs] “Install the CLI and the skills that teach your AI assistant to use it”
   • [probe] “official MCP server documented at https://docs.customer.io/ai/mcp/get-started/”

   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 Customer.io
   Customer.io✓fullprobed8/10

   Customer.io documents an official MCP server plus CLI+skills that let an AI assistant perform actions via natural language (list automations, draft emails, build automations) with read/write permission separation, and a Slack AI interface for natural-language operation. Missing for 10: independent/hands-on corroboration of these NL workflows actually working end-to-end beyond first-party docs.

   • [claimed-docs] “Your AI can do anything you'd do by clicking or typing in Customer.io. That means you can have it build automations, draft messages, analyze…”
   • [claimed-docs] “Install the CLI and the skills that teach your AI assistant to use it”
   • [claimed-docs] “List all active automations in my workspace.”
   • [claimed-docs] “Reads are separated from writes and deletes... so you can approve each category independently.”
   • [claimed-docs] “Draft a welcome email in Design Studio.”
   • [claimed-docs] “Use Customer.io AI in Slack”
   • [probe] “official MCP server documented at https://docs.customer.io/ai/mcp/get-started/”

   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 Customer.io
   Customer.io~partialprobed5/10

   Customer.io provides an OpenAPI spec (confirmed live at openapi.json) and a downloadable Postman collection for hands-on API testing, but there's no evidence of an in-browser interactive reference (e.g., Swagger-style 'try it' console) with runnable examples embedded directly in the docs site. Missing for 10: an embedded interactive try-it-now console in the docs, independent confirmation of usability/coverage of the OpenAPI spec.

   • [claimed-docs] “We've generated a Postman collection to help you get started with our APIs.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.customer.io/openapi.json — contains "openapi" key”

   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 to Customer.io
   Customer.io✓fullprobed9/10

   A probe confirms a live, machine-readable OpenAPI spec at https://docs.customer.io/openapi.json returning HTTP 200 with an 'openapi' key, plus a Postman collection is also provided for API onboarding. Missing for 10: independent/community corroboration of developers actually consuming the OpenAPI spec (e.g., via SDK generation).

   • [probe] “PROBE openapi: HTTP 200 at https://docs.customer.io/openapi.json — contains "openapi" key”
   • [claimed-docs] “We've generated a Postman collection to help you get started with our APIs.”

   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 drawn
   Customer.io—none0/10

   No evidence of a sandbox/staging environment or test workspace separate from production; the evidence pack covers API docs, MCP tooling, and pricing features, but nothing about isolated test data or sandbox mode. Community evidence even notes self-serve sign-in/testing was removed after a pricing shift, reinforcing the absence of a documented sandbox capability. missing for 10: dedicated sandbox/staging environment, documentation of test workspaces, isolation guarantees for AI testing without touching production data.

   • [community] “After Series A/leadership change: price hikes based on contact count (not usage), AE outreach began, forced onto annual commitment plans, se…”

   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
   Customer.io—none0/10

   Evidence shows API docs, OpenAPI spec, and Postman collections exist, but there is no mention of API versioning scheme or a documented deprecation policy anywhere in the pack. Missing for 10: explicit API version numbers/headers, changelog or migration guides, and a stated deprecation/sunset policy for older API versions.

   • [claimed-docs] “To get data into Customer.io, use an SDK or the Pipelines API. This is the API that most of our integrations are based on and likely the API…”
   • [claimed-docs] “Our Track API provides ways to send real-time customer data to your Customer.io workspace including customer identification and event tracki…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.customer.io/openapi.json — contains "openapi" key”

   proof ↗⚑ 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
   Customer.io—none0/10

   The evidence covers Track/Pipelines APIs for sending data in, broadcast triggering, and MCP for listing automations, but there is no mention of a Reporting/Analytics API or documented endpoints for pulling campaign or flow performance metrics (opens, clicks, conversions, etc.) out to a warehouse or BI tool. Missing for 10: any reporting/metrics API documentation, export/webhook mechanism for performance data, or dashboard-sync examples.

   • [claimed-docs] “To get data into Customer.io, use an SDK or the Pipelines API. This is the API that most of our integrations are based on and likely the API…”
   • [claimed-docs] “Our Track API provides ways to send real-time customer data to your Customer.io workspace including customer identification and event tracki…”
   • [claimed-docs] “List all active automations in my workspace.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.customer.io/openapi.json — contains "openapi" key”

   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
   Customer.io—none0/10

   The evidence pack covers messaging setup, broadcasts, segments, APIs, and MCP/AI tooling, but contains no mention of conversion/revenue attribution reporting tied to specific emails or flows beyond opens/clicks. Missing for 10: any documentation of conversion goals, revenue tracking, or attribution reports linking signups/revenue to specific campaigns or flows.

   ⚑ 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
   Customer.io—none0/10

   The evidence pack contains no documentation of campaign/automation reporting dashboards, open/click/unsubscribe/conversion metrics, or time-series analytics views—only references to triggers, segments, and messaging setup. Missing for 10: any mention of a reporting/analytics UI, per-step conversion tracking, or historical metrics API/export.

   ⚑ 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 Customer.io
   Customer.io~partialprobed4/10

   Customer.io has an MCP server and programmatic APIs (Pipelines/Track) that could plausibly let an AI agent create segments, and docs show natural-language MCP commands like listing automations or drafting emails, but no evidence explicitly shows an agent translating a plain-language description into a created segment via API/MCP. missing for 10: a concrete example of segment creation through the API/MCP, documentation of segment-definition endpoints, and independent confirmation this works end-to-end.

   • [claimed-docs] “List all active automations in my workspace.”
   • [claimed-docs] “Reads are separated from writes and deletes... so you can approve each category independently.”
   • [claimed-docs] “If you go to the Segments page, you'll see segments like "Paying Customers", "Have not logged in recently" and "Unsubscribed".”
   • [probe] “official MCP server documented at https://docs.customer.io/ai/mcp/get-started/”
   • [claimed-docs] “To get data into Customer.io, use an SDK or the Pipelines API. This is the API that most of our integrations are based on and likely the API…”

   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 Customer.io
   Customer.io~partialprobed6/10

   Docs confirm the Pipelines/Track API for creating/updating profiles with custom properties, plus a documented pattern for suppression (sending a 'Suppress Person' event) and deletion, and an OpenAPI spec/Postman collection support production integration. However, there is no explicit evidence of rate limits, batch/bulk endpoints, or production-scale guarantees, and one community report cites bugs with the system as a reason for switching providers. missing for 10: explicit production-scale/rate-limit documentation, independent verification of suppression at scale, and confirmation that the 'delete/suppress via event' pattern is robust in practice.

   • [claimed-docs] “To get data into Customer.io, use an SDK or the Pipelines API. This is the API that most of our integrations are based on and likely the API…”
   • [claimed-docs] “if you wanted to delete a profile, you'd send a track event with a name parameter called Delete Person. If you want to suppress a profile, y…”
   • [claimed-docs] “Our Track API provides ways to send real-time customer data to your Customer.io workspace including customer identification and event tracki…”
   • [claimed-docs] “We've generated a Postman collection to help you get started with our APIs.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.customer.io/openapi.json — contains "openapi" key”
   • [community] “'We used customer.io for the past few months but due to bugs with the system, we switched to sendwithus with sendgrid as our ESP. We've been…”

   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 to Customer.io
   Customer.io~partialcommunity3/10

   Docs confirm segments exist as a concept (docs-11) and that objects/relationships can be managed via the Track/Pipelines API's /group endpoint (docs-6, docs-7), implying some programmatic control over customer data groupings, but there is no direct evidence of an API to create/update segments, tags, or lists, nor any documented way to read back exact membership. A community report even cites 'lack of code-based flexibility for defining segments' as a driver for building an alternative (comm-3), suggesting real limitations in programmatic segment management. missing for 10: explicit API endpoints for segment/tag/list CRUD, membership read-back examples, and independent confirmation that these work as described.

   • [claimed-docs] “The Pipelines API natively supports objects and relationships through the /group endpoint.”
   • [claimed-docs] “Our Track API provides ways to send real-time customer data to your Customer.io workspace including customer identification and event tracki…”
   • [claimed-docs] “If you go to the Segments page, you'll see segments like "Paying Customers", "Have not logged in recently" and "Unsubscribed".”
   • [community] “Developer built an open-source alternative 'after getting frustrated with Customer.io's limitations,' citing lack of code-based flexibility …”

   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 Customer.io
   Customer.io✓fullcommunity7/10

   Docs describe building segments (e.g., 'Paying Customers', 'Have not logged in recently') from attribute conditions and events, and automations can trigger when profiles join segments, implying live-updating segment membership as data changes. However, tags-based segmentation isn't explicitly documented, and one community post notes frustration with 'lack of code-based flexibility for defining segments,' suggesting some limitations in segment logic sophistication. Missing for 10: explicit tag-criteria documentation, independent confirmation of real-time segment recalculation, and rebuttal to the code-flexibility complaint.

   • [claimed-docs] “If you go to the Segments page, you'll see segments like "Paying Customers", "Have not logged in recently" and "Unsubscribed".”
   • [claimed-docs] “You can trigger automations when profiles perform events, when they join Segments (e.g. they meet attribute conditions), and so on.”
   • [claimed-docs] “Our Track API provides ways to send real-time customer data to your Customer.io workspace including customer identification and event tracki…”
   • [community] “Developer built an open-source alternative 'after getting frustrated with Customer.io's limitations,' citing lack of code-based flexibility …”

   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 Customer.io
   Customer.io~partialclaimed5/10

   Customer.io supports bulk-style actions like triggering a Broadcast to an entire list of recipients at once and triggering automations when profiles join a Segment (docs-4, docs-13, docs-12), which are genuine bulk operations. However there's no explicit evidence of a bulk/batch API endpoint for mass profile updates, imports, or deletions, nor of the MCP/CLI AI tools performing multi-item bulk actions in one command. Missing for 10: documented bulk/batch API endpoints (e.g. batch import, bulk update/delete), evidence of AI assistant executing bulk operations across many items via MCP/CLI, and independent confirmation of bulk operation reliability at scale.

   • [claimed-docs] “Trigger broadcasts: you'll set up a broadcast in our UI and then trigger it with a single call.”
   • [claimed-docs] “Broadcasts send a message to a list of recipients. Broadcast messages are queued to send to all the defined recipients at a time you specify…”
   • [claimed-docs] “You can trigger automations when profiles perform events, when they join Segments (e.g. they meet attribute conditions), and so on.”
   • [claimed-docs] “if you wanted to delete a profile, you'd send a track event with a name parameter called Delete Person. If you want to suppress a profile, y…”
   • [claimed-docs] “The Pipelines API natively supports objects and relationships through the /group endpoint.”

   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 Customer.io
   Customer.io✓fullclaimed8/10

   Customer.io's journeys/automations natively trigger actions when profiles perform events or join segments, with rich workflow features like Wait Until delays and branching, and this is fully documented as core product functionality. missing for 10: independent/hands-on verification of automation reliability at scale, and more detail on complex multi-condition rule logic beyond events/segments.

   • [claimed-docs] “You can trigger automations when profiles perform events, when they join Segments (e.g. they meet attribute conditions), and so on.”
   • [claimed-docs] “If you go to the Segments page, you'll see segments like "Paying Customers", "Have not logged in recently" and "Unsubscribed".”
   • [claimed-docs] “Chain multiple delays together in a single _Wait Until_ block”
   • [claimed-docs] “Broadcasts send a message to a list of recipients. Broadcast messages are queued to send to all the defined recipients at a time you specify…”
   • [claimed-docs] “Transactional messages are ideal for: Purchase receipts, Registration confirmations, Password resets, Event reminders, Shipping updates”

   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 to Customer.io
   Customer.io~partialprobed6/10

   Customer.io's core platform natively supports recurring/triggered workflows (automations triggered by events/segments, chained Wait Until delays, scheduled broadcasts) and docs claim AI can 'build automations' via the CLI/MCP, with MCP able to list active automations. However, there is no concrete evidence of an AI agent actually creating or scheduling a new recurring workflow end-to-end (writes/deletes require separate approval, and only read/list and draft-email examples are shown). missing for 10: a documented example of AI creating/editing a recurring automation via MCP or CLI, independent confirmation of AI-driven automation authoring succeeding.

   • [claimed-docs] “Your AI can do anything you'd do by clicking or typing in Customer.io. That means you can have it build automations, draft messages, analyze…”
   • [claimed-docs] “List all active automations in my workspace.”
   • [claimed-docs] “Reads are separated from writes and deletes... so you can approve each category independently.”
   • [claimed-docs] “You can trigger automations when profiles perform events, when they join Segments (e.g. they meet attribute conditions), and so on.”
   • [claimed-docs] “Broadcasts send a message to a list of recipients. Broadcast messages are queued to send to all the defined recipients at a time you specify…”
   • [claimed-docs] “Chain multiple delays together in a single _Wait Until_ block”
   • [probe] “official MCP server documented at https://docs.customer.io/ai/mcp/get-started/”

   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
   Customer.io—none0/10

   No evidence of version control, review/approval workflows for automation changes, or rollback of automations. The MCP docs mention read/write approval separation for actions but nothing about versioning or reverting automation states over time.

   • [claimed-docs] “List all active automations in my workspace.”
   • [claimed-docs] “Reads are separated from writes and deletes... so you can approve each category independently.”

   proof ↗⚑ 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 Customer.io
   Customer.io~partialprobed5/10

   Customer.io's MCP server explicitly separates reads from writes/deletes so a human can approve each category independently, and docs show AI drafting content (welcome emails, automations) and broadcasts being queued to send at a specified time to a defined recipient list/segment — this supports an approval-gated, agent-drafted campaign workflow. However, there's no direct evidence of an agent drafting a full campaign against a segment specifically and leaving it in a 'scheduled/queued pending human approval' state as one integrated flow; the approval mechanism (read/write separation) and scheduled broadcast feature are documented separately, not as a combined AI-driven approval-to-send pipeline. missing for 10: an end-to-end example of an agent creating a segment-targeted campaign draft and explicitly queuing it for human approval before send, and independent/hands-on confirmation this works as described.

   • [claimed-docs] “List all active automations in my workspace.”
   • [claimed-docs] “Reads are separated from writes and deletes... so you can approve each category independently.”
   • [claimed-docs] “Broadcasts send a message to a list of recipients. Broadcast messages are queued to send to all the defined recipients at a time you specify…”
   • [claimed-docs] “Draft a welcome email in Design Studio.”
   • [probe] “official MCP server documented at https://docs.customer.io/ai/mcp/get-started/”

   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 Mailchimp
   Customer.io~partialclaimed3/10

   Customer.io's own docs state that broadcasts must first be configured in the UI and can then only be triggered via a single API call, directly contradicting the 'entirely through API' requirement; there is no documented endpoint to create or schedule a broadcast/campaign purely programmatically. Missing for 10: a documented API endpoint for creating/scheduling broadcasts or campaigns (not just triggering pre-built ones), and confirmation that campaign scheduling doesn't require dashboard configuration.

   • [claimed-docs] “Trigger broadcasts: you'll set up a broadcast in our UI and then trigger it with a single call.”
   • [claimed-docs] “Broadcasts send a message to a list of recipients. Broadcast messages are queued to send to all the defined recipients at a time you specify…”
   • [claimed-docs] “Our Track API provides ways to send real-time customer data to your Customer.io workspace including customer identification and event tracki…”

   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
   Customer.io✓fullclaimed7/10

   Docs show the core loop: segments for audience selection (docs-11), broadcasts queued to defined recipients at a specified time (docs-13), UI-based broadcast setup with trigger API (docs-4), and Design Studio/drag-and-drop editor for composing messages (docs-16, docs-17). This covers compose, pick audience, and send/schedule as table-stakes. Missing for 10: independent hands-on corroboration of the end-to-end flow and explicit UI screenshots/docs of a scheduling calendar interface (only inferred from 'time you specify').

   • [claimed-docs] “If you go to the Segments page, you'll see segments like "Paying Customers", "Have not logged in recently" and "Unsubscribed".”
   • [claimed-docs] “Broadcasts send a message to a list of recipients. Broadcast messages are queued to send to all the defined recipients at a time you specify…”
   • [claimed-docs] “Trigger broadcasts: you'll set up a broadcast in our UI and then trigger it with a single call.”
   • [claimed-docs] “Draft a welcome email in Design Studio.”
   • [claimed-docs] “Drag-and-drop visual editor Included Included Included Code editor Included”

   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
   Customer.io—none0/10

   No evidence in the pack mentions A/B testing of subject lines or content variants, nor any mechanism for automatically selecting a winner based on engagement metrics; broadcasts, transactional messages, and automations are described but split-testing is never referenced.

   ⚑ 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
   Customer.io—none0/10

   No evidence in the pack mentions bounce, complaint, or blocklist tracking, deliverability dashboards, or actionable guidance for degraded sending reputation; the docs focus on automations, broadcasts, AI/MCP tooling, and pricing features unrelated to deliverability signals.

   ⚑ 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
   Customer.io—none0/10

   No evidence in the pack addresses domain authentication (SPF/DKIM/DMARC) setup, guided DNS configuration, or verification workflows for sending domains — all evidence concerns AI/MCP integrations, APIs, journeys, and pricing.

   ⚑ 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 to Customer.io
   Customer.io~partialclaimed3/10

   Docs mention a 'Suppress Person' event and an 'Unsubscribed' segment, implying some suppression capability, but there is no evidence describing automatic bounce or spam-complaint suppression, nor confirmation that suppression is honored uniformly across broadcasts, transactional, and journey sends. Missing for 10: documented bounce/spam-complaint auto-suppression, explicit cross-send-type enforcement, and any compliance (CAN-SPAM/GDPR) framing.

   • [claimed-docs] “if you wanted to delete a profile, you'd send a track event with a name parameter called Delete Person. If you want to suppress a profile, y…”
   • [claimed-docs] “If you go to the Segments page, you'll see segments like "Paying Customers", "Have not logged in recently" and "Unsubscribed".”

   proof ↗⚑ 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 to Customer.io
   Customer.io~partialclaimed4/10

   Docs confirm Customer.io has a Pipelines/Track API that 'most of our integrations are based on' and note users can 'use your preferred tools and sources to transit data through Customer.io,' implying an integrations ecosystem exists, but no evidence names or documents maintained first-party connectors for Stripe, Shopify, Segment, or a product database specifically. missing for 10: explicit documentation of named Stripe/Shopify/Segment/CDP integrations, integration marketplace listing, maintenance/versioning details for these connectors.

   • [claimed-docs] “To get data into Customer.io, use an SDK or the Pipelines API. This is the API that most of our integrations are based on and likely the API…”
   • [claimed-docs] “you can also use your preferred tools and sources to transit data through Customer.io. It's up to you!”
   • [claimed-docs] “Our Track API provides ways to send real-time customer data to your Customer.io workspace including customer identification and event tracki…”

   proof ↗⚑ 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
   Customer.io—none0/10

   The evidence pack covers inbound APIs (Track/Pipelines API), MCP tooling, and broadcast/journey features, but contains no mention of outbound webhooks for delivery/engagement events (sends, opens, clicks, bounces, unsubscribes) or of signed payload verification. missing for 10: documentation of webhook subscription endpoints/UI, event types supported, payload signing/verification mechanism, and any independent confirmation of reliability.

   • [claimed-docs] “To get data into Customer.io, use an SDK or the Pipelines API. This is the API that most of our integrations are based on and likely the API…”
   • [claimed-docs] “Our Track API provides ways to send real-time customer data to your Customer.io workspace including customer identification and event tracki…”
   • [claimed-docs] “Broadcasts send a message to a list of recipients. Broadcast messages are queued to send to all the defined recipients at a time you specify…”

   proof ↗⚑ 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 Customer.io
   Customer.io~partialcommunity6/10

   Docs confirm core lifecycle-automation building blocks: triggering journeys off events/segments (docs-12), chaining multiple delays in a Wait Until block (docs-18), listing active automations (docs-9), and segment-based audience targeting (docs-11). However, the evidence pack never explicitly documents branching logic or exit-rule configuration, the two specific mechanics named in the story, and one community report cites frustration with limited flexibility in defining email flows (customer-io-comm-3). Missing for 10: explicit documentation of conditional branch splits and exit-rule/goal settings within a journey, plus independent hands-on confirmation of multi-step welcome/onboarding/winback builds.

   • [claimed-docs] “You can trigger automations when profiles perform events, when they join Segments (e.g. they meet attribute conditions), and so on.”
   • [claimed-docs] “Chain multiple delays together in a single _Wait Until_ block”
   • [claimed-docs] “List all active automations in my workspace.”
   • [claimed-docs] “If you go to the Segments page, you'll see segments like "Paying Customers", "Have not logged in recently" and "Unsubscribed".”
   • [community] “Developer built an open-source alternative 'after getting frustrated with Customer.io's limitations,' citing lack of code-based flexibility …”

   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 Customer.io
   Customer.io✓fullclaimed8/10

   Docs clearly describe sending real-time custom events via the Track/Pipelines API (docs-3, docs-7) and triggering automations specifically when a profile performs an event (docs-12), which directly matches the developer story of firing an event to trigger a person-specific automation. Missing for 10: independent/hands-on confirmation that per-person triggering works reliably at scale, and more detail on event payload/attribute matching nuances.

   • [claimed-docs] “To get data into Customer.io, use an SDK or the Pipelines API. This is the API that most of our integrations are based on and likely the API…”
   • [claimed-docs] “Our Track API provides ways to send real-time customer data to your Customer.io workspace including customer identification and event tracki…”
   • [claimed-docs] “You can trigger automations when profiles perform events, when they join Segments (e.g. they meet attribute conditions), and so on.”
   • [claimed-docs] “you can also use your preferred tools and sources to transit data through Customer.io. It's up to you!”

   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
   Customer.io—none0/10

   No evidence describes a per-person view of automation/journey progress or an ops action to pull or re-enter a profile without breaking the flow; docs cover triggering automations, segments, and broadcasts but not individual journey-state visibility or manual re-entry controls.

   • [claimed-docs] “You can trigger automations when profiles perform events, when they join Segments (e.g. they meet attribute conditions), and so on.”
   • [claimed-docs] “If you go to the Segments page, you'll see segments like "Paying Customers", "Have not logged in recently" and "Unsubscribed".”

   proof ↗⚑ 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
   Customer.io—none0/10

   The evidence pack only documents APIs for sending data INTO Customer.io (Track API, Pipelines API, suppression via events) and MCP-based automation reads, but contains no mention of a bulk data export, audience/contact export tool, or open-format download of engagement history and suppression lists. No self-serve export capability is evidenced anywhere in the pack. Missing for 10: any documentation of an export/download feature, open-format (CSV/JSON) audience export, or bulk API read endpoint for full contact/tag/engagement/suppression data.

   • [claimed-docs] “To get data into Customer.io, use an SDK or the Pipelines API. This is the API that most of our integrations are based on and likely the API…”
   • [claimed-docs] “if you wanted to delete a profile, you'd send a track event with a name parameter called Delete Person. If you want to suppress a profile, y…”
   • [claimed-docs] “Our Track API provides ways to send real-time customer data to your Customer.io workspace including customer identification and event tracki…”

   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
   Customer.io—none0/10

   No evidence of a guided migration tool or import wizard that preserves tags, custom fields, and unsubscribe state from another ESP. Docs discuss general data ingestion via Track/Pipelines API and profile suppression events, but nothing about a dedicated migration/import feature for list portability.

   ⚑ 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 Customer.io
   Customer.io~partialprobed6/10

   Customer.io ships an official MCP server (customer-io-probe-3) that lets an AI list automations (customer-io-docs-9) and separates reads from writes for safe automated access (customer-io-docs-10); docs also describe segments/audiences (customer-io-docs-11) and broadcast/automation structures (customer-io-docs-12, customer-io-docs-13) that an agent could query. However, the story also asks for 'recent campaign results' reporting, and evidence only vaguely claims AI can 'analyze performance' (customer-io-docs-1) without showing a concrete reporting/analytics API or MCP tool for campaign metrics. Missing for 10: explicit documentation of a reporting/analytics endpoint or MCP tool for campaign results, and independent/hands-on confirmation that an agent can actually pull full program state (audiences+automations+results) end-to-end.

   • [probe] “official MCP server documented at https://docs.customer.io/ai/mcp/get-started/”
   • [claimed-docs] “List all active automations in my workspace.”
   • [claimed-docs] “Reads are separated from writes and deletes... so you can approve each category independently.”
   • [claimed-docs] “If you go to the Segments page, you'll see segments like "Paying Customers", "Have not logged in recently" and "Unsubscribed".”
   • [claimed-docs] “You can trigger automations when profiles perform events, when they join Segments (e.g. they meet attribute conditions), and so on.”
   • [claimed-docs] “Broadcasts send a message to a list of recipients. Broadcast messages are queued to send to all the defined recipients at a time you specify…”
   • [claimed-docs] “Your AI can do anything you'd do by clicking or typing in Customer.io. That means you can have it build automations, draft messages, analyze…”

   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
   Customer.io—none0/10

   The evidence pack covers sending data in (Track/Pipelines API), triggering broadcasts, and AI/MCP automation management, but contains no documentation of an API endpoint for reading a contact's engagement history (messages sent, opened, clicked). Missing for 10: any mention of an Activities/Customer Journey read API, endpoint docs for per-person message history, or examples returning open/click events for a contact.

   • [claimed-docs] “To get data into Customer.io, use an SDK or the Pipelines API. This is the API that most of our integrations are based on and likely the API…”
   • [claimed-docs] “Our Track API provides ways to send real-time customer data to your Customer.io workspace including customer identification and event tracki…”

   proof ↗⚑ 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 drawn
   Customer.io—none0/10

   The evidence shows Customer.io's MCP integration separates reads from writes for AI-action approval (customer-io-docs-10), but there is no evidence of an admin-configurable mechanism to mint scoped or read-only API keys/credentials for external agents or contractors to access analytics data without send capability.

   • [claimed-docs] “Reads are separated from writes and deletes... so you can approve each category independently.”

   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 to Mailchimp
   Customer.io!disputedcontradicted4/10

   Customer.io explicitly claims 'Your AI can do anything you'd do by clicking or typing' (docs-1) and ships a Pipelines/Track API plus MCP server, but its own docs contradict full parity: broadcasts must be set up in the UI and only triggered via API (docs-4), and segments/journeys are shown as UI-defined constructs (docs-11, docs-12). Independent evidence reinforces this gap—a developer built an open-source alternative specifically due to 'lack of code-based flexibility for defining segments and email flows' (customer-io-comm-3). missing for 10: API-only creation of broadcasts/segments/email flows without prior UI setup, and independent confirmation that MCP/API coverage matches 100% of UI functionality.

   • [claimed-docs] “Your AI can do anything you'd do by clicking or typing in Customer.io. That means you can have it build automations, draft messages, analyze…”
   • [claimed-docs] “Trigger broadcasts: you'll set up a broadcast in our UI and then trigger it with a single call.”
   • [claimed-docs] “If you go to the Segments page, you'll see segments like "Paying Customers", "Have not logged in recently" and "Unsubscribed".”
   • [claimed-docs] “You can trigger automations when profiles perform events, when they join Segments (e.g. they meet attribute conditions), and so on.”
   • [community] “Developer built an open-source alternative 'after getting frustrated with Customer.io's limitations,' citing lack of code-based flexibility …”
   • [probe] “official MCP server documented at https://docs.customer.io/ai/mcp/get-started/”

   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
   Customer.io—none0/10

   Evidence shows APIs for getting data in and out (Track/Pipelines API) but no documented bulk data export tool or open-format full account export/portability feature, nor any 'leave with your data' guarantee. No mention of GDPR-style export or data portability commitments.

   ⚑ 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
   Customer.io—none0/10

   No evidence in the pack mentions data residency options, regional storage selection, or EU/US hosting choices for Customer.io.

   ⚑ 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
   Customer.io—none0/10

   No evidence in the pack addresses AI-model training opt-out or data usage controls for Customer.io; all citations concern messaging automation, APIs, and MCP tooling, not AI training data policy.

   ⚑ 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 to Customer.io
   Customer.io~partialclaimed6/10

   Customer.io documents explicit mechanisms to delete or suppress profile data via the Track API (Delete Person / Suppress Person events), and its MCP server separates delete operations from reads/writes for explicit approval, giving AI-native users some control over data removal. However, there's no documented retention-policy settings, automated data expiry, bulk/GDPR-scale deletion tooling, or audit trail for deletions. Missing for 10: configurable retention periods, bulk/automated deletion workflows, compliance/audit documentation, independent verification that deletion requests are honored.

   • [claimed-docs] “if you wanted to delete a profile, you'd send a track event with a name parameter called Delete Person. If you want to suppress a profile, y…”
   • [claimed-docs] “Reads are separated from writes and deletes... so you can approve each category independently.”

   proof ↗⚑ 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 to Customer.io
   Customer.io~partialclaimed5/10

   Docs confirm broad AI drafting ability ('draft messages', 'Draft a welcome email in Design Studio', 'AI-generated global styles') and an AI assistant reachable via MCP/CLI/Slack, implying some copy-generation capability, but none of the evidence specifically describes subject-line drafting/refinement or copy editing embedded directly inside the message composer UI. Missing for 10: explicit documentation of an in-composer AI subject-line/body-copy assistant, a described 'brief-to-draft' workflow, and independent/hands-on confirmation of this specific feature.

   • [claimed-docs] “Your AI can do anything you'd do by clicking or typing in Customer.io. That means you can have it build automations, draft messages, analyze…”
   • [claimed-docs] “Draft a welcome email in Design Studio.”
   • [claimed-docs] “AI-generated global styles”
   • [claimed-docs] “Use Customer.io AI in Slack”

   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 Customer.io
   Customer.io~partialclaimed5/10

   Docs confirm a drag-and-drop visual editor, code editor, AI-generated global styles, and a Design Studio for drafting emails, showing on-brand visual design tooling. However, there is no explicit evidence of reusable template libraries, personalization token syntax, or cross-email-client rendering/testing guarantees, which are core parts of this story. Missing for 10: reusable template management, personalization token documentation, cross-client rendering testing/preview evidence.

   • [claimed-docs] “AI-generated global styles”
   • [claimed-docs] “Draft a welcome email in Design Studio.”
   • [claimed-docs] “Drag-and-drop visual editor Included Included Included Code editor Included”

   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 to Customer.io
   Customer.io~partialcommunity3/10

   Docs mention a 'Code editor' included in the Design Studio for building emails (docs-17) and a Pipelines/Track API for data, but there is no evidence of dedicated template CRUD API endpoints, MJML support, or a documented git/version-control workflow for templates; a community developer even built an OSS alternative citing lack of code-based flexibility for email flows (customer-io-comm-3). missing for 10: template API endpoints with variable substitution docs, MJML/HTML-as-code workflow, version-control integration or CLI template sync.

   • [claimed-docs] “Drag-and-drop visual editor Included Included Included Code editor Included”
   • [claimed-docs] “Draft a welcome email in Design Studio.”
   • [community] “Developer built an open-source alternative 'after getting frustrated with Customer.io's limitations,' citing lack of code-based flexibility …”

   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 Customer.io
   Customer.io~partialclaimed6/10

   Docs confirm transactional message use cases (receipts, password resets, shipping updates) and a Track/Pipelines API for sending real-time customer data and events, alongside the same platform's broadcast/marketing capabilities, supporting one-to-one and marketing sends via one API. However, there is no explicit developer-facing example of sending a single transactional message via API call (e.g., a dedicated Transactional API endpoint with code sample) or confirmation of independent/hands-on verification of transactional deliverability. missing for 10: explicit Transactional API code example/endpoint documentation, independent hands-on confirmation of transactional send reliability, clarification on rate/latency guarantees for one-to-one sends.

   • [claimed-docs] “Transactional messages are ideal for: Purchase receipts, Registration confirmations, Password resets, Event reminders, Shipping updates”
   • [claimed-docs] “Our Track API provides ways to send real-time customer data to your Customer.io workspace including customer identification and event tracki…”
   • [claimed-docs] “To get data into Customer.io, use an SDK or the Pipelines API. This is the API that most of our integrations are based on and likely the API…”
   • [claimed-docs] “Broadcasts send a message to a list of recipients. Broadcast messages are queued to send to all the defined recipients at a time you specify…”

   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 Customer.io
   Customer.io~partialclaimed5/10

   Docs confirm transactional messaging exists for receipts, confirmations, password resets, etc. (customer-io-docs-14), and separate suppression events can be sent via API (customer-io-docs-5), but there is no explicit documentation of separate deliverability/reputation isolation between transactional and marketing sending, nor confirmation that suppressing a marketing contact does not block transactional receipts. missing for 10: explicit statement that transactional sending reputation/IP pool is isolated from marketing, documented suppression-list scoping (transactional vs marketing), and independent/hands-on confirmation that an unsubscribed contact still receives a transactional receipt.

   • [claimed-docs] “Transactional messages are ideal for: Purchase receipts, Registration confirmations, Password resets, Event reminders, Shipping updates”
   • [claimed-docs] “if you wanted to delete a profile, you'd send a track event with a name parameter called Delete Person. If you want to suppress a profile, y…”
   • [claimed-docs] “If you go to the Segments page, you'll see segments like "Paying Customers", "Have not logged in recently" and "Unsubscribed".”

   proof ↗⚑ 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