{ "data": { "a": { "slug": "mailchimp-marketing", "name": "Mailchimp Marketing API", "vendor": "Intuit Mailchimp", "vendorUrl": "https://mailchimp.com", "kind": "http-api", "category": "lifecycle-marketing", "summary": "Intuit Mailchimp's Marketing API manages audiences, contacts, tags, segments, events, campaigns, automations and reports for a Mailchimp account. It is a REST API at `https://api.mailchimp.com/3.0/` that takes an API key or an OAuth 2 token.", "url": "https://www.anchorterminal.com/tools/mailchimp-marketing", "markdownUrl": "https://www.anchorterminal.com/tools/mailchimp-marketing.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mailchimp-marketing.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mailchimp-marketing.json", "dns": "mailchimp-marketing.grade.anchorterminal.com", "repo": "https://github.com/mailchimp/mailchimp-marketing-typescript-sdk", "license": "Proprietary service under Mailchimp's Standard Terms of Use and API Use Policy. The generated client libraries declare Apache-2.0 in their package metadata", "transports": [ "http" ], "remoteUrl": "https://api.mailchimp.com/3.0", "packages": [ { "registry": "npm", "name": "@mailchimp/mailchimp_marketing" }, { "registry": "pypi", "name": "mailchimp-marketing" } ], "auth": "mixed", "authNotes": "Self-serve API key, or an OAuth 2 token for another user's account. A user with Manager permissions or above creates a key under Profile, Extras, API keys, and it is shown once. A key has full account access, bounded only by its creator's user level, with no read-only or per-endpoint option. Keys created from 22 June 2026 expire after one year, per the help centre. OAuth uses the authorisation code grant with no scopes, no refresh token and tokens that do not expire. Registering an OAuth app is done in the account, and a Marketplace listing needs OAuth. Both credentials go in HTTP Basic or `Authorization: Bearer`.", "pricing": "freemium", "pricingNotes": "The Free plan has 250 contacts and 500 sends a month (250 a day), one audience and one seat, with no time limit. Paid plans start at $13 a month for Essentials, $20 for Standard and $350 for Premium with USD selected, and rise with the contact count. API calls are not metered. The 14-day trial of a paid plan needs payment details. An agent's owner can start on the Free plan without a contract (https://mailchimp.com/pricing/marketing/, https://mailchimp.com/help/about-mailchimp-pricing-plans/).", "priceSummary": "$13 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the OpenAPI file or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 278434, "pypiWeekly": 111433, "asOf": "2026-10-08" }, "docsUrl": "https://mailchimp.com/developer/marketing/", "llmsTxt": "https://mailchimp.com/developer/marketing/llms.txt", "openapi": "https://api.mailchimp.com/schema/openapi/OpenAPI.json?expand", "capabilities": [ "marketing.profiles", "marketing.events", "marketing.segments", "marketing.campaigns", "marketing.journeys", "email.templates" ], "tags": [ "official", "hosted", "closed-source", "api-key", "oauth", "openapi", "llms-txt", "free-tier", "webhooks", "cli", "typescript", "python", "go", "java", "status-page", "soc2" ], "lastRelease": "2026-10-05", "graded": true, "anchor": { "graded": true, "score": 60.2, "grade": "C", "agentReady": false, "rank": 663, "ranked": true, "rankOf": 1510, "categoryRank": 8, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 68, "payments": 25, "reliability": 72, "schema": 76, "security": 46, "transparency": 74 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -2, "negativeNotes": [ "8 October 2026. The quick start tells users to run `npm install @mailchimp/mailchimp-marketing`, and the npm registry answered 404 for that name. On 4 November the quick start still gave the same command, and the registry couldn't be reached from our shell to re-check. So 2 for a published install step the listing couldn't meet for its TypeScript library (https://mailchimp.com/developer/marketing/build/start-developing/send-your-first-api-request.md, https://registry.npmjs.org/@mailchimp%2fmailchimp-marketing)." ], "verdict": "A public OpenAPI 3.1 file covers all 297 operations, every docs page has a Markdown copy, and responses can be trimmed with `fields`. An API key carries full account access with no read-only option. The quick start's TypeScript package was not on npm on 8 October 2026, and the changelog's newest entry is 19 August 2025.", "bestFor": "Small businesses already on Mailchimp that want an agent to sync contacts, tag and segment them, record events, draft and schedule campaigns and read reports.", "strengths": [ "OpenAPI 3.1 file for all 297 operations at `https://api.mailchimp.com/schema/openapi/OpenAPI.json`, with an error response on every operation", "`fields` and `exclude_fields` trim responses on 130 operations, and `count` pages up to 1,000 records", "Every docs page has a Markdown copy at the URL plus `.md`, with llms.txt indexes and four published agent skills", "Errors are `application/problem+json` with `title`, `status`, `detail` and `instance`, and an `X-Trigger-Error` header lets a client test its handling", "Free plan with 250 contacts and 500 sends a month, and a status page with an API component for each of 21 data centres" ], "weaknesses": [ "An API key has full account access. The docs say there is no read-only key and no way to limit a key to chosen endpoints", "OAuth 2 tokens carry no scopes and never expire, and no approval step before `actions/send` was found", "The quick start's `npm install @mailchimp/mailchimp-marketing` answered 404 on npm on 8 October, and the quick start still gives it", "The only stated limit is 10 simultaneous connections per user. No `Retry-After` header, idempotency key or SLA was found", "The developer changelog's newest entry is 19 August 2025, and the docs say keys never expire while the help centre says new keys expire after one year", "Click tracking was lost for about 25 hours on 3 and 4 August 2026 and cannot be backfilled, per the status page" ], "agentNotes": [ "Send the key or OAuth token as `Authorization: Bearer` to `https://api.mailchimp.com/3.0/`. Treat it as full account access and keep it server-side", "Address a contact by the MD5 hash of the lowercase email address, and use PUT on `/lists/{list_id}/members/{subscriber_hash}` so a retry does not create a duplicate", "Ask a person before POST `/campaigns/{campaign_id}/actions/send`. Read `/campaigns/{campaign_id}/send-checklist` and use `actions/test` first", "Keep to 10 concurrent requests per user, and send large jobs to `/batches`. A 429 names no wait time, so back off and retry", "Add `fields=` to every list call and set `count` (default 10, maximum 1,000) with `offset`", "Set `is_syncing` to true when loading historical events so they do not trigger automations" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60.2 } ], "editorialScores": { "ergonomics": 73, "maintenance": 68, "payments": 25, "reliability": 72, "schema": 76, "security": 46, "transparency": 55 }, "provenanceScore": 93, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -sS \\\n \"https://api.mailchimp.com/3.0/ping\" \\\n --user \"anystring:${apikey}\"", "claudeCode": "claude mcp add --transport http fern_mcp_mailchimp-docs \\\n https://mailchimp.com/developer/_mcp/server", "config": { "mcpServers": { "mailchimp-docs": { "type": "http", "url": "https://mailchimp.com/developer/_mcp/server" } } } }, "letme": { "capability": "https://letme.dev/marketing.profiles", "tool": "https://letme.dev/mailchimp-marketing" }, "sameCompany": [ "mandrill" ], "area": "communication", "unitPrices": [ { "item": "Essentials plan, up to 500 contacts", "unit": "month", "usd": 13, "note": "starting price with USD selected, rises with contacts" }, { "item": "Standard plan, up to 500 contacts", "unit": "month", "usd": 20, "note": "starting price with USD selected, rises with contacts" }, { "item": "Premium plan, starting price", "unit": "month", "usd": 350, "note": "starting price with USD selected, rises with contacts" } ], "provenance": { "legalEntity": "The Rocket Science Group LLC d/b/a Mailchimp", "domain": "mailchimp.com", "domainRegistered": "2001-06-29", "endpointOnVendorDomain": true, "terms": "https://mailchimp.com/legal/terms/", "privacy": "https://www.intuit.com/privacy/statement/", "statusPage": "https://status.mailchimp.com", "changelog": "https://mailchimp.com/developer/release-notes/", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The Standard Terms of Use, updated and effective 10 October 2025, name The Rocket Science Group LLC d/b/a Mailchimp, 405 N Angier Ave. NE, Atlanta, Georgia. API use is also governed by the API Use Policy at https://mailchimp.com/legal/api_use/, updated 1 August 2023, which the terms incorporate.", "The privacy field points at the Intuit Global Privacy Statement, last updated 9 March 2026. mailchimp.com/legal/privacy redirects to it, the terms name it as the privacy document for the service, and it names The Rocket Science Group LLC d/b/a Mailchimp. Mailchimp publishes no separate privacy policy.", "The API answers at api.mailchimp.com. An unauthenticated request to `/3.0/ping` returned 401 as `application/problem+json` on 8 October 2026.", "mailchimp.com/.well-known/security.txt holds one Contact line that points at the responsible disclosure section of the security page, with no Expires field. The value follows the reading on the Mailchimp Transactional listing.", "The changelog covers the Marketing and Transactional APIs together. Its newest entry is dated 19 August 2025, and its newest Marketing entry 7 August 2025.", "RDAP for mailchimp.com gives a registration date of 2001-06-29 (Verisign)." ], "score": 93 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mailchimp-marketing.json", "live": { "slug": "mailchimp-marketing", "probe": { "target": "https://api.mailchimp.com/3.0", "method": "get", "lastAt": "2026-11-07T19:22:17.747085503Z", "lastOk": true, "lastStatus": 401, "lastMs": 354, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.96, "p50ms24h": 327, "p95ms24h": 574, "samples24h": 238, "samples30d": 7299, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 168 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 252 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 184 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.mailchimp.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:01.419069576Z" }, "versions": [ { "registry": "github", "name": "mailchimp/mailchimp-marketing-typescript-sdk", "version": "1.0.03", "released": "2026-10-13", "seenAt": "2026-11-06T23:41:45.729509572Z" }, { "registry": "npm", "name": "@mailchimp/mailchimp_marketing", "version": "3.0.80", "seenAt": "2026-11-06T23:41:45.3139476Z" }, { "registry": "pypi", "name": "mailchimp-marketing", "version": "3.0.80", "released": "2022-11-02", "seenAt": "2026-11-06T23:41:45.530035552Z" } ], "githubStars": 0, "npmWeekly": 301365, "pypiWeekly": 132999, "securityTxt": { "url": "https://mailchimp.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T15:59:41.954623744Z" }, "llmsTxt": { "url": "https://mailchimp.com/developer/marketing/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:56.071091893Z" }, "domain": { "domain": "mailchimp.com", "registered": "2001-06-29", "source": "https://rdap.verisign.com/com/v1/domain/mailchimp.com", "checkedAt": "2026-11-01T14:09:51.942989092Z" }, "pages": [ { "url": "https://mailchimp.com/developer/release-notes/", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:13:39.881243603Z", "changedAt": "2026-10-28T04:38:15.917860338Z", "fingerprint": "eabe4136d3fd" }, { "url": "https://mailchimp.com/help/about-mailchimp-pricing-plans/", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:13:42.858283668Z", "changedAt": "2026-11-05T12:36:58.984421063Z", "fingerprint": "174dbb82057e" }, { "url": "https://mailchimp.com/pricing/marketing/", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:13:46.116551259Z", "changedAt": "2026-11-07T14:13:46.116551259Z", "fingerprint": "981e7e834f1c" }, { "url": "https://www.intuit.com/privacy/statement/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:30:20.272991469Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "bdf88eaea616" }, { "url": "https://mailchimp.com/legal/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:13:44.070635532Z", "changedAt": "2026-10-30T05:43:29.265979329Z", "fingerprint": "24853a4c12ab" } ], "mcpTools": { "url": "https://mailchimp.com/developer/_mcp/server", "checkedAt": "2026-11-07T01:46:04.506267404Z", "status": "error", "note": "initialize: HTTP 404", "changedAt": "2026-11-07T01:46:04.506267404Z" }, "github": { "repo": "mailchimp/mailchimp-marketing-typescript-sdk", "checkedAt": "2026-11-02T09:02:20.928892212Z", "stars": 0, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-13T15:15:39Z", "openIssues": 1, "openPRs": 0, "issuesOpened90d": 1, "issuesClosed90d": 0, "prsMerged90d": 4, "ci": { "branch": "main", "runs": 7, "success": 7, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-10-13T15:16:30Z" }, "replies": { "sampled": 1, "unanswered": 1 } }, "updatedAt": "2026-11-07T19:22:17.747085503Z" } }, "answer": "Sequenzy scores 63.7 (B) on agent readiness against Mailchimp Marketing API's 60.2 (C), and leads in 4 of 7 scored categories. Mailchimp Marketing API leads on reliability and transparency \u0026 trust.", "b": { "slug": "sequenzy", "name": "Sequenzy", "vendor": "Nic Tech Solutions, LLC", "vendorUrl": "https://www.sequenzy.com", "kind": "http-api", "category": "lifecycle-marketing", "summary": "Sequenzy is an email marketing and lifecycle automation platform for SaaS and ecommerce teams, with sequences, campaigns, transactional email, an agent inbox, push and SMS. It has a REST API, an MCP server, a CLI and a TypeScript SDK.", "url": "https://www.anchorterminal.com/tools/sequenzy", "markdownUrl": "https://www.anchorterminal.com/tools/sequenzy.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sequenzy.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sequenzy.json", "dns": "sequenzy.grade.anchorterminal.com", "repo": "https://github.com/Sequenzy/mcp", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.sequenzy.com/v1/mcp", "packages": [ { "registry": "npm", "name": "sequenzy" }, { "registry": "npm", "name": "@sequenzy/mcp" }, { "registry": "npm", "name": "@sequenzy/cli" } ], "auth": "mixed", "authNotes": "Workspace API keys (`seq_live_`) and account keys (`seq_user_`) sent as Bearer tokens, each with permission scopes such as `transactional:send`, `subscribers:tag` and explicit `*:delete`, and presets including read-only and drafts-only. Account keys keep the user's workspace role. Agents can also register through the `service_auth` OAuth flow, where the user confirms a code in a Sequenzy browser page.", "pricing": "freemium", "pricingNotes": "Free plan of 2,500 emails a month with unlimited contacts and API, MCP and CLI access, no card, with a Sequenzy footer. Paid plans by monthly email volume, $19 for 15,000, $29 for 30,000, $49 for 60,000, $99 for 120,000, up to $2,999 for 5 million. SMS add-on $16 a month with 1,000 credits.", "priceSummary": "$19 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms.txt, auth.md, the pricing page or the OpenAPI spec (checked 2026-11-06).", "endpoints": [] }, "toolCount": 306, "popularity": { "githubStars": null, "npmWeekly": 2363, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.sequenzy.com", "llmsTxt": "https://www.sequenzy.com/llms.txt", "openapi": "https://docs.sequenzy.com/openapi.yaml", "registryName": "io.github.polnikale/sequenzy-mcp", "capabilities": [ "marketing.profiles", "marketing.events", "marketing.segments", "marketing.campaigns", "marketing.journeys", "email.send", "email.templates", "email.inbound" ], "tags": [ "hosted", "closed-source", "mcp", "remote-mcp", "mcp-registry", "oauth", "api-key", "openapi", "llms-txt", "webhooks", "idempotency", "smtp", "sms", "no-card", "free-tier", "typescript", "cli", "no-status-page" ], "lastRelease": "2026-11-06", "graded": true, "anchor": { "graded": true, "score": 63.7, "grade": "B", "agentReady": false, "rank": 506, "ranked": true, "rankOf": 1510, "categoryRank": 6, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 78, "payments": 40, "reliability": 38, "schema": 95, "security": 67, "transparency": 67 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Scoped keys with read-only and drafts-only presets, a 475-operation OpenAPI spec, idempotent sends and near-daily dated releases make it workable for an agent. The MCP server lists about 306 tools, which is heavy on context, and there is no status page, SLA or published request limit table.", "bestFor": "SaaS and ecommerce lifecycle email run from code or an agent, with billing-event triggers from Stripe, Paddle and others.", "strengths": [ "Every key and MCP grant carries permission scopes, with read-only and drafts-only presets and explicit delete permissions", "OpenAPI 3.1 with 475 described operations, llms.txt and Markdown twins of the docs", "Tool and API errors return a code, a fix and a docs link, and sends take an `Idempotency-Key`", "Free plan of 2,500 emails a month with no card and full API, MCP and CLI access", "Dated changelog entries almost every day, 353 since December 2025" ], "weaknesses": [ "About 306 MCP tools, with no toolsets or dynamic loading found", "No status page, incident history or SLA found", "Request rate limits appear only as response headers and a few per-route notes, with no published table", "The registry entry io.github.polnikale/sequenzy-mcp is at 0.0.36 while npm is at 0.0.246", "The terms' governing-law clause doesn't name a jurisdiction" ], "agentNotes": [ "Connect with a drafts-only or read-only key unless the task must send, and widen permissions only when an error names the missing scope", "Send an `Idempotency-Key` with each transactional send and reuse it unchanged after an uncertain result", "Read `structuredContent.error.code` and `howToFix` on a failed tool call before retrying; the client doesn't retry", "Call `get_account` and `select_company` first when the key can reach more than one workspace", "On 429 wait for Retry-After and read the RateLimit-Remaining header" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.7 } ], "editorialScores": { "ergonomics": 69, "maintenance": 78, "payments": 40, "reliability": 38, "schema": 95, "security": 67, "transparency": 64 }, "provenanceScore": 70, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install sequenzy", "claudeCode": "claude mcp add --scope user --env=SEQUENZY_API_KEY=seq_user_your_key_here sequenzy -- npx -y @sequenzy/mcp", "config": { "mcpServers": { "sequenzy": { "args": [ "-y", "@sequenzy/mcp" ], "command": "npx", "env": { "SEQUENZY_API_KEY": "seq_user_your_key_here" } } } } }, "letme": { "capability": "https://letme.dev/marketing.profiles", "tool": "https://letme.dev/sequenzy" }, "alsoIn": [ "email" ], "area": "communication", "unitPrices": [ { "item": "15,000 emails", "unit": "month", "usd": 19 }, { "item": "60,000 emails", "unit": "month", "usd": 49 }, { "item": "120,000 emails", "unit": "month", "usd": 99 }, { "item": "300,000 emails", "unit": "month", "usd": 199 }, { "item": "SMS add-on", "unit": "month", "usd": 16, "note": "1,000 credits a month" } ], "provenance": { "legalEntity": "Nic Tech Solutions, LLC", "domain": "sequenzy.com", "domainRegistered": "2025-11-25", "endpointOnVendorDomain": true, "terms": "https://www.sequenzy.com/terms", "privacy": "https://www.sequenzy.com/privacy", "statusPage": "", "changelog": "https://docs.sequenzy.com/changelog", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The site footer and contact page name Nic Tech Solutions, LLC in Delaware. The terms (30 June 2026) say they're governed by the laws of the jurisdiction in which Sequenzy operates, without naming it.", "Privacy policy last updated 16 September 2026, security page 3 July 2026, and a public DPA with a named sub-processor list.", "www.sequenzy.com/robots.txt disallows /api/, /dashboard/ and app paths only; docs.sequenzy.com disallows /_next/ and /cdn-cgi/. Both carry Content-Signal ai-input=yes.", "RDAP gives sequenzy.com a registration date of 25 November 2025.", "/.well-known/security.txt returns 404; the security page gives security@sequenzy.com for disclosure. No status page found." ], "score": 70 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/sequenzy.json", "live": { "slug": "sequenzy", "probe": { "target": "https://api.sequenzy.com/v1/mcp", "method": "get", "lastAt": "2026-11-07T19:22:32.315745023Z", "lastOk": true, "lastStatus": 401, "lastMs": 513, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 430, "p95ms24h": 963, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "versions": [ { "registry": "mcp-registry", "name": "io.github.polnikale/sequenzy-mcp", "version": "0.0.80", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "@sequenzy/cli", "version": "0.0.202", "seenAt": "2026-11-07T00:04:47.709534287Z" }, { "registry": "npm", "name": "@sequenzy/mcp", "version": "0.0.246", "seenAt": "2026-11-07T00:04:46.382384788Z" }, { "registry": "npm", "name": "sequenzy", "version": "2.1.56", "seenAt": "2026-11-07T00:04:45.470371029Z" } ], "githubStars": 3, "npmWeekly": 2363, "securityTxt": { "url": "https://sequenzy.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:21.983534364Z" }, "llmsTxt": { "url": "https://www.sequenzy.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:54.221757235Z" }, "pages": [ { "url": "https://docs.sequenzy.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:07:55.051332773Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c2d75327efad" }, { "url": "https://www.sequenzy.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:34:21.090752788Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "03a493105931" }, { "url": "https://www.sequenzy.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:34:23.45384067Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "a816dc038eb6" } ], "updatedAt": "2026-11-07T19:22:32.315745023Z" } }, "edges": [ { "by": 34, "category": "reliability", "leads": "mailchimp-marketing", "name": "Reliability", "reasons": { "a": "Graded on the hosted REST API with the hosted lines. status.mailchimp.com lists an API component for each of 21 data centres and keeps event history by month, re-read on 4 November (20). In the 90 days from 6 August 2026 the marketing events are campaign links returning 500 errors on 13 August, delayed audience updates on 11 September, cropped images disappearing in campaigns from 9 October, and access issues on some app pages \"for some Mailchimp users\" on 27 to 29 October. Each hit one function or some users, none names the API component, and November has none, so minor only (20). The loss of click tracking from 3 to 4 August ended before the window. The three Transactional delays belong to the Mailchimp Transactional listing. The docs give 10 simultaneous connections per user, a 120-second timeout and 500 pending batches, with no per-minute figure (12 of 15, partly met). 429 is documented with its cause. The official Python library's README says it retries 408, 409, 429 and 5xx with exponential backoff, two retries by default. No `Retry-After` header, idempotency key or safe-retry guidance for writes was found in the docs, so backoff alone (10). No SLA found (0). Version 3.0 is generally available, and the Audiences endpoints are beta (10). 20 + 20 + 12 + 10 + 0 + 10 = 72.", "b": "Graded with the hosted lines. No status page was found; none is linked from the site, llms.txt or docs, and status.sequenzy.com doesn't resolve (0). With no history to read, the incident line takes 5. 429 responses carry RateLimit-Limit and RateLimit-Remaining headers for a per-minute policy, and some routes state numbers (20 requests a minute per workspace for AI copy), but no table of limits per key was found (8 of 15). 429s carry Retry-After, sends take an `Idempotency-Key`, a reused key with a different body returns IDEMPOTENCY_KEY_REUSED, and the MCP docs say a retry hint alone doesn't make a write safe to repeat (15). No SLA found (0). No beta label on the API or MCP server (10). Total 38." }, "scores": { "a": 72, "b": 38 } }, { "by": 21, "category": "security", "leads": "sequenzy", "name": "Security \u0026 auth", "reasons": { "a": "API keys are named, several to an account, revocable, and bounded by the creating user's level. A key has full account access, and the docs say there is no read-only key and no per-endpoint limit. Keys made from 22 June 2026 expire after one year per the help centre. OAuth 2 uses the authorisation code grant with no scopes, and its tokens never expire. Credentials travel in a header, not the URL (20). No read-only mode. `send-checklist`, `actions/test`, `actions/unschedule` and `actions/cancel-send` exist, with no approval step before a send or a permanent contact delete (6). The API returns contact fields, conversation messages and survey answers, which are untrusted text, and no guidance on prompt injection was found (2). `/authorized-apps` lists the OAuth apps on an account and each response carries a request id. No API call log or audit log was found in the docs we read (4). A responsible disclosure programme with no rewards, a security.txt with a contact and no Expires field, SOC 2 reports, ISO 27001, regular penetration tests and optional two-factor sign-in. No public advisory feed found (14).", "b": "Workspace and account API keys with fine-grained permission scopes, presets and explicit `*:delete` rights, revocable in settings, plus an OAuth `service_auth` flow for agents with user confirmation (30). Read-only and drafts-only presets let an agent prepare mail without sending, and account keys keep the user's workspace role (20). The agent inbox and reply tracking give the agent inbound mail, and no prompt-injection guidance was found in the MCP, permissions or inbox docs (4 of 15). The DPA lists administrative audit logs and MCP events report replies and bounces; no per-call API log for the customer was found (8 of 15). A responsible disclosure address on the security page, no security.txt (404), bug bounty or certification (5 of 20). Total 67." }, "scores": { "a": 46, "b": 67 } }, { "by": 19, "category": "schema", "leads": "sequenzy", "name": "Schema \u0026 documentation", "reasons": { "a": "An OpenAPI 3.1.1 file with all 297 operations is public on the API host, and the docs site serves a 1.2 MB copy (25). llms.txt at each level of the docs and a Markdown copy of every page at the URL plus `.md` (10). Every operation has a description, averaging about 60 characters. They say what a call does and seldom when not to use it, and four agent skills cover consent, OAuth, webhooks and bulk jobs (10). The smaller file carries 498 enums and required fields on request bodies. Merge fields and event properties are free-form objects (12). The API's own file has examples throughout and a `default` error response on every operation, and the docs have an error glossary. The docs-site copy lists only 200 and 204 responses (12). The version is in the path and has been 3.0 since 2016. The public changelog's newest entry is 19 August 2025, so key expiry from 22 June 2026, webhook signing and the new client libraries are not in it, and the specification's version label is 0.1.0-dev (7).", "b": "OpenAPI 3.1 at docs.sequenzy.com/openapi.yaml with 349 paths and 475 operations, all described (25). llms.txt on both hosts, llms-full.txt, auth.md, agents.md and Markdown twins of the docs (10). Operation and tool descriptions give purpose, the scope each needs and the alternative, such as the deprecated generate-sequence alias (18 of 20). Typed inputs, and tools reject undeclared arguments with an error naming the supported ones (13 of 15). Errors on nearly every operation (401 on 442, 404 on 330, 400 on 290) with examples, and a structured error with code, `howToFix` and `docsUrl` for tools (14 of 15). Version in the path and spec, and a dated changelog (15). Total 95." }, "scores": { "a": 76, "b": 95 } }, { "by": 15, "category": "payments", "leads": "sequenzy", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Plan prices are public without a login, from $13 a month for Essentials, $20 for Standard and $350 for Premium with USD selected, rising with contacts through a selector. Nothing is priced per API call (10). The Free plan has 250 contacts and 500 sends a month with no time limit. We could not confirm that signup asks for no card, and the 14-day trial of a paid plan needs payment details, so 15 of 20. A person signs up in a browser and creates a key or approves OAuth (0).", "b": "No x402, MPP or L402 (0). Prices are public as volume tiers from $19 for 15,000 emails to $2,999 for 5 million, without a per-email overage rate (10 of 20). Free plan of 2,500 emails a month with no card (20). Agents can register through `service_auth`, but the user has to confirm a code in a Sequenzy browser page, and plan payment is through Stripe (10 of 20). Total 40." }, "scores": { "a": 25, "b": 40 } }, { "by": 10, "category": "maintenance", "leads": "sequenzy", "name": "Maintenance \u0026 community", "reasons": { "a": "Release 1.0.3 of the TypeScript, Python and Go client libraries, the first tag in each, is dated 5 October 2026, 30 days before this check (30). The TypeScript library's 1.0.03 of 13 October changes only version strings and the lockfile, so it counts half and doesn't set recency. Dated releases in the 90 days from 6 August include the CLI's 0.0.212 and 0.0.213 and Swift 1.0.0 on 18 September, Java 1.0.0 and C# 1.0.0 and 1.0.1 on 21 September, and 1.0.3 across the libraries on 5 October (20). The API changelog has no entry in that time. A public changelog whose newest entry is 19 August 2025, an API help address, and a help centre article saying support is not trained for in-depth API questions. We saw no public issue replies (5 of 15). Nine official client libraries generated from the current specification, with the TypeScript package absent from npm on 8 October (8 of 15, partly met). Each repository has a workflow that compiles and tests, whose results we could not see, and release 1.0.3 removed the `LICENSE` and `NOTICE` files added on 18 September (5 of 10, partly met). 30 + 20 + 5 + 8 + 5 = 68.", "b": "sequenzy 2.1.56, @sequenzy/mcp 0.0.246 and @sequenzy/cli 0.0.202 were all published on 6 November 2026 (30). 18 SDK, 105 MCP and 93 CLI releases in the 90 days from 8 August, and dated changelog entries on most days (20). A closed service with a public changelog and support answered by the cofounders per the about page. GitHub issues weren't read, as the GitHub API refused our requests for its rate limit (12 of 15). Listed in the official MCP registry as io.github.polnikale/sequenzy-mcp, but the entry is at 0.0.36 against npm's 0.0.246, and the TypeScript SDK is current (10 of 15). MIT packages released daily, the MCP server and CLI still at 0.0.x (6 of 10). Total 78." }, "scores": { "a": 68, "b": 78 } }, { "by": 7, "category": "transparency", "leads": "mailchimp-marketing", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service with published terms, an API Use Policy and a named contracting entity. The client libraries declare Apache-2.0 in package metadata (15). A data processing addendum effective 26 September 2024 covers deletion or return on termination without a stated period, and the Intuit Global Privacy Statement of 9 March 2026 is the privacy document. The terms let Mailchimp use inputs and outputs of its AI functions, customer data included, for machine learning, with a preference in account settings. No retention periods for marketing data were found (18). No deprecation policy was found. The API Use Policy says the APIs can change by a posting or an email. Dated notices exist, such as key expiry from 22 June 2026 in the help centre (8). A sub-processor list with locations is public and was last updated on 29 February 2024, and the security page places Mailchimp's own servers in United States data centres (14).", "b": "A closed service. The SDK, MCP server and CLI are MIT on npm. The terms (30 June 2026) don't name the contracting entity in their text or a governing jurisdiction; the footer names Nic Tech Solutions, LLC (15 of 30). Privacy policy of 16 September 2026 and a public DPA agree on processing, and the terms say data is deleted within 30 days of termination (24 of 30). Deprecated endpoints are marked and kept as compatibility aliases; no written deprecation policy with notice periods (10 of 20). The DPA names its core sub-processors with their purpose; data locations aren't stated (15 of 20). Total 64." }, "scores": { "a": 74, "b": 67 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Intuit Mailchimp", "b": "Nic Tech Solutions, LLC", "name": "Vendor" }, { "a": "https://api.mailchimp.com/3.0", "b": "https://api.sequenzy.com/v1/mcp", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP, stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Mailchimp's Standard Terms of Use and API Use Policy. The generated client libraries declare Apache-2.0 in their package metadata", "b": "none", "name": "Licence" }, { "a": "none", "b": "306", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.polnikale/sequenzy-mcp", "name": "MCP registry" }, { "a": "2026-10-05", "b": "2026-11-06", "name": "Last release" }, { "a": "no date given", "b": "2026-06-30", "name": "Terms last updated" }, { "a": "2026-03-09", "b": "2026-09-16", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "278k npm/wk, 111k PyPI/wk", "b": "2.4k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Sequenzy scores 63.7 (B) on agent readiness against Mailchimp Marketing API's 60.2 (C), and leads in 4 of 7 scored categories. Mailchimp Marketing API leads on reliability and transparency \u0026 trust.", "question": "Which is better for AI agents, Mailchimp Marketing API or Sequenzy?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Mailchimp Marketing API and Sequenzy need an API key?" }, { "answer": "Yes. Mailchimp Marketing API has a hosted endpoint at https://api.mailchimp.com/3.0 and Sequenzy at https://api.sequenzy.com/v1/mcp.", "question": "Can an agent call Mailchimp Marketing API and Sequenzy without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 72 against 38", "Transparency \u0026 trust, 74 against 67" ], "also": null, "goodFor": "Small businesses already on Mailchimp that want an agent to sync contacts, tag and segment them, record events, draft and schedule campaigns and read reports.", "slug": "mailchimp-marketing", "watchFor": "An API key has full account access. The docs say there is no read-only key and no way to limit a key to chosen endpoints" }, { "aheadOn": [ "Schema \u0026 documentation, 95 against 76", "Security \u0026 auth, 67 against 46", "Payments \u0026 pricing, 40 against 25", "Maintenance \u0026 community, 78 against 68" ], "also": [ "Runs on your own machine", "Free to start without a card" ], "goodFor": "SaaS and ecommerce lifecycle email run from code or an agent, with billing-event triggers from Stripe, Paddle and others.", "slug": "sequenzy", "watchFor": "About 306 MCP tools, with no toolsets or dynamic loading found" } ], "history": { "mailchimp-marketing": [ { "causes": [ "correction", "time" ], "date": "2026-11-04", "delta": 2.8, "from": 57.4, "fromGrade": "C", "to": 60.2, "toGrade": "C" } ], "sequenzy": null }, "job": { "capability": "marketing.profiles", "name": "Marketing audiences" }, "others": [ { "json": "https://www.anchorterminal.com/compare/activecampaign-vs-mailchimp-marketing.json", "title": "ActiveCampaign vs Mailchimp Marketing API", "url": "https://www.anchorterminal.com/compare/activecampaign-vs-mailchimp-marketing" }, { "json": "https://www.anchorterminal.com/compare/activecampaign-vs-sequenzy.json", "title": "ActiveCampaign vs Sequenzy", "url": "https://www.anchorterminal.com/compare/activecampaign-vs-sequenzy" }, { "json": "https://www.anchorterminal.com/compare/braze-vs-mailchimp-marketing.json", "title": "Braze vs Mailchimp Marketing API", "url": "https://www.anchorterminal.com/compare/braze-vs-mailchimp-marketing" }, { "json": "https://www.anchorterminal.com/compare/braze-vs-sequenzy.json", "title": "Braze vs Sequenzy", "url": "https://www.anchorterminal.com/compare/braze-vs-sequenzy" }, { "json": "https://www.anchorterminal.com/compare/clevertap-vs-mailchimp-marketing.json", "title": "CleverTap vs Mailchimp Marketing API", "url": "https://www.anchorterminal.com/compare/clevertap-vs-mailchimp-marketing" }, { "json": "https://www.anchorterminal.com/compare/clevertap-vs-sequenzy.json", "title": "CleverTap vs Sequenzy", "url": "https://www.anchorterminal.com/compare/clevertap-vs-sequenzy" }, { "json": "https://www.anchorterminal.com/compare/customer-io-vs-mailchimp-marketing.json", "title": "Customer.io vs Mailchimp Marketing API", "url": "https://www.anchorterminal.com/compare/customer-io-vs-mailchimp-marketing" }, { "json": "https://www.anchorterminal.com/compare/customer-io-vs-sequenzy.json", "title": "Customer.io vs Sequenzy", "url": "https://www.anchorterminal.com/compare/customer-io-vs-sequenzy" }, { "json": "https://www.anchorterminal.com/compare/iterable-vs-mailchimp-marketing.json", "title": "Iterable vs Mailchimp Marketing API", "url": "https://www.anchorterminal.com/compare/iterable-vs-mailchimp-marketing" }, { "json": "https://www.anchorterminal.com/compare/iterable-vs-sequenzy.json", "title": "Iterable vs Sequenzy", "url": "https://www.anchorterminal.com/compare/iterable-vs-sequenzy" }, { "json": "https://www.anchorterminal.com/compare/klaviyo-vs-mailchimp-marketing.json", "title": "Klaviyo API + MCP vs Mailchimp Marketing API", "url": "https://www.anchorterminal.com/compare/klaviyo-vs-mailchimp-marketing" }, { "json": "https://www.anchorterminal.com/compare/klaviyo-vs-sequenzy.json", "title": "Klaviyo API + MCP vs Sequenzy", "url": "https://www.anchorterminal.com/compare/klaviyo-vs-sequenzy" }, { "json": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-moengage.json", "title": "Mailchimp Marketing API vs MoEngage", "url": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-moengage" }, { "json": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-nitrosend.json", "title": "Mailchimp Marketing API vs Nitrosend", "url": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-nitrosend" }, { "json": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-omnisend.json", "title": "Mailchimp Marketing API vs Omnisend", "url": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-omnisend" }, { "json": "https://www.anchorterminal.com/compare/moengage-vs-sequenzy.json", "title": "MoEngage vs Sequenzy", "url": "https://www.anchorterminal.com/compare/moengage-vs-sequenzy" }, { "json": "https://www.anchorterminal.com/compare/nitrosend-vs-sequenzy.json", "title": "Nitrosend vs Sequenzy", "url": "https://www.anchorterminal.com/compare/nitrosend-vs-sequenzy" }, { "json": "https://www.anchorterminal.com/compare/omnisend-vs-sequenzy.json", "title": "Omnisend vs Sequenzy", "url": "https://www.anchorterminal.com/compare/omnisend-vs-sequenzy" }, { "json": "https://www.anchorterminal.com/compare/dreamlit-vs-mailchimp-marketing.json", "title": "Dreamlit vs Mailchimp Marketing API", "url": "https://www.anchorterminal.com/compare/dreamlit-vs-mailchimp-marketing" }, { "json": "https://www.anchorterminal.com/compare/dreamlit-vs-sequenzy.json", "title": "Dreamlit vs Sequenzy", "url": "https://www.anchorterminal.com/compare/dreamlit-vs-sequenzy" } ], "panel": null, "scores": [ { "by": 34, "edge": "mailchimp-marketing", "key": "reliability", "mailchimp-marketing": 72, "name": "Reliability", "sequenzy": 38, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 19, "edge": "sequenzy", "key": "schema", "mailchimp-marketing": 76, "name": "Schema \u0026 documentation", "sequenzy": 95, "weight": 13 }, { "by": 4, "edge": "mailchimp-marketing", "key": "ergonomics", "mailchimp-marketing": 73, "name": "Agent ergonomics", "sequenzy": 69, "weight": 13 }, { "by": 21, "edge": "sequenzy", "key": "security", "mailchimp-marketing": 46, "name": "Security \u0026 auth", "sequenzy": 67, "weight": 14 }, { "by": 15, "edge": "sequenzy", "key": "payments", "mailchimp-marketing": 25, "name": "Payments \u0026 pricing", "sequenzy": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 10, "edge": "sequenzy", "key": "maintenance", "mailchimp-marketing": 68, "name": "Maintenance \u0026 community", "sequenzy": 78, "weight": 7 }, { "by": 7, "edge": "mailchimp-marketing", "key": "transparency", "mailchimp-marketing": 74, "name": "Transparency \u0026 trust", "sequenzy": 67, "weight": 7 } ], "summary": "Sequenzy scores 63.7 (B) on agent readiness against Mailchimp Marketing API's 60.2 (C), and leads in 4 of 7 scored categories. Mailchimp Marketing API leads on reliability and transparency \u0026 trust. Both do marketing audiences.", "tasks": null, "tutorials": [], "verdicts": { "mailchimp-marketing": "A public OpenAPI 3.1 file covers all 297 operations, every docs page has a Markdown copy, and responses can be trimmed with `fields`. An API key carries full account access with no read-only option. The quick start's TypeScript package was not on npm on 8 October 2026, and the changelog's newest entry is 19 August 2025.", "sequenzy": "Scoped keys with read-only and drafts-only presets, a 475-operation OpenAPI spec, idempotent sends and near-daily dated releases make it workable for an agent. The MCP server lists about 306 tools, which is heavy on context, and there is no status page, SLA or published request limit table." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-sequenzy", "json": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-sequenzy.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-sequenzy.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-sequenzy.min.md" }, "markdown": "Sequenzy scores 63.7 (B) on agent readiness against Mailchimp Marketing API's 60.2 (C), and leads in 4 of 7 scored categories. Mailchimp Marketing API leads on reliability and transparency \u0026 trust. Both do marketing audiences.\n\n- Mailchimp Marketing API: grade C, 60.2/100, rank #663 of 1510. Markdown https://www.anchorterminal.com/tools/mailchimp-marketing.md · JSON https://www.anchorterminal.com/api/v1/tools/mailchimp-marketing.json\n- Sequenzy: grade B, 63.7/100, rank #506 of 1510. Markdown https://www.anchorterminal.com/tools/sequenzy.md · JSON https://www.anchorterminal.com/api/v1/tools/sequenzy.json\n- Best lifecycle marketing and customer engagement platforms for AI agents: https://www.anchorterminal.com/best/lifecycle-marketing/index.md\n- All 66 lifecycle marketing comparisons: https://www.anchorterminal.com/compare/lifecycle-marketing/index.md\n- Best email delivery APIs for AI agents: https://www.anchorterminal.com/best/email/index.md\n- All 174 email comparisons: https://www.anchorterminal.com/compare/email/index.md\n\n## Which one, for what\n\n### Mailchimp Marketing API (C)\n\nGood for: Small businesses already on Mailchimp that want an agent to sync contacts, tag and segment them, record events, draft and schedule campaigns and read reports.\n\nAhead on:\n- Reliability, 72 against 38\n- Transparency \u0026 trust, 74 against 67\n\nWatch for: An API key has full account access. The docs say there is no read-only key and no way to limit a key to chosen endpoints\n\n### Sequenzy (B)\n\nGood for: SaaS and ecommerce lifecycle email run from code or an agent, with billing-event triggers from Stripe, Paddle and others.\n\nAhead on:\n- Schema \u0026 documentation, 95 against 76\n- Security \u0026 auth, 67 against 46\n- Payments \u0026 pricing, 40 against 25\n- Maintenance \u0026 community, 78 against 68\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: About 306 MCP tools, with no toolsets or dynamic loading found\n\n\n## Why the edge\n\n### Reliability: Mailchimp Marketing API +34\n\n- Mailchimp Marketing API (72): Graded on the hosted REST API with the hosted lines. status.mailchimp.com lists an API component for each of 21 data centres and keeps event history by month, re-read on 4 November (20). In the 90 days from 6 August 2026 the marketing events are campaign links returning 500 errors on 13 August, delayed audience updates on 11 September, cropped images disappearing in campaigns from 9 October, and access issues on some app pages \"for some Mailchimp users\" on 27 to 29 October. Each hit one function or some users, none names the API component, and November has none, so minor only (20). The loss of click tracking from 3 to 4 August ended before the window. The three Transactional delays belong to the Mailchimp Transactional listing. The docs give 10 simultaneous connections per user, a 120-second timeout and 500 pending batches, with no per-minute figure (12 of 15, partly met). 429 is documented with its cause. The official Python library's README says it retries 408, 409, 429 and 5xx with exponential backoff, two retries by default. No `Retry-After` header, idempotency key or safe-retry guidance for writes was found in the docs, so backoff alone (10). No SLA found (0). Version 3.0 is generally available, and the Audiences endpoints are beta (10). 20 + 20 + 12 + 10 + 0 + 10 = 72.\n- Sequenzy (38): Graded with the hosted lines. No status page was found; none is linked from the site, llms.txt or docs, and status.sequenzy.com doesn't resolve (0). With no history to read, the incident line takes 5. 429 responses carry RateLimit-Limit and RateLimit-Remaining headers for a per-minute policy, and some routes state numbers (20 requests a minute per workspace for AI copy), but no table of limits per key was found (8 of 15). 429s carry Retry-After, sends take an `Idempotency-Key`, a reused key with a different body returns IDEMPOTENCY_KEY_REUSED, and the MCP docs say a retry hint alone doesn't make a write safe to repeat (15). No SLA found (0). No beta label on the API or MCP server (10). Total 38.\n\n### Security \u0026 auth: Sequenzy +21\n\n- Mailchimp Marketing API (46): API keys are named, several to an account, revocable, and bounded by the creating user's level. A key has full account access, and the docs say there is no read-only key and no per-endpoint limit. Keys made from 22 June 2026 expire after one year per the help centre. OAuth 2 uses the authorisation code grant with no scopes, and its tokens never expire. Credentials travel in a header, not the URL (20). No read-only mode. `send-checklist`, `actions/test`, `actions/unschedule` and `actions/cancel-send` exist, with no approval step before a send or a permanent contact delete (6). The API returns contact fields, conversation messages and survey answers, which are untrusted text, and no guidance on prompt injection was found (2). `/authorized-apps` lists the OAuth apps on an account and each response carries a request id. No API call log or audit log was found in the docs we read (4). A responsible disclosure programme with no rewards, a security.txt with a contact and no Expires field, SOC 2 reports, ISO 27001, regular penetration tests and optional two-factor sign-in. No public advisory feed found (14).\n- Sequenzy (67): Workspace and account API keys with fine-grained permission scopes, presets and explicit `*:delete` rights, revocable in settings, plus an OAuth `service_auth` flow for agents with user confirmation (30). Read-only and drafts-only presets let an agent prepare mail without sending, and account keys keep the user's workspace role (20). The agent inbox and reply tracking give the agent inbound mail, and no prompt-injection guidance was found in the MCP, permissions or inbox docs (4 of 15). The DPA lists administrative audit logs and MCP events report replies and bounces; no per-call API log for the customer was found (8 of 15). A responsible disclosure address on the security page, no security.txt (404), bug bounty or certification (5 of 20). Total 67.\n\n### Schema \u0026 documentation: Sequenzy +19\n\n- Mailchimp Marketing API (76): An OpenAPI 3.1.1 file with all 297 operations is public on the API host, and the docs site serves a 1.2 MB copy (25). llms.txt at each level of the docs and a Markdown copy of every page at the URL plus `.md` (10). Every operation has a description, averaging about 60 characters. They say what a call does and seldom when not to use it, and four agent skills cover consent, OAuth, webhooks and bulk jobs (10). The smaller file carries 498 enums and required fields on request bodies. Merge fields and event properties are free-form objects (12). The API's own file has examples throughout and a `default` error response on every operation, and the docs have an error glossary. The docs-site copy lists only 200 and 204 responses (12). The version is in the path and has been 3.0 since 2016. The public changelog's newest entry is 19 August 2025, so key expiry from 22 June 2026, webhook signing and the new client libraries are not in it, and the specification's version label is 0.1.0-dev (7).\n- Sequenzy (95): OpenAPI 3.1 at docs.sequenzy.com/openapi.yaml with 349 paths and 475 operations, all described (25). llms.txt on both hosts, llms-full.txt, auth.md, agents.md and Markdown twins of the docs (10). Operation and tool descriptions give purpose, the scope each needs and the alternative, such as the deprecated generate-sequence alias (18 of 20). Typed inputs, and tools reject undeclared arguments with an error naming the supported ones (13 of 15). Errors on nearly every operation (401 on 442, 404 on 330, 400 on 290) with examples, and a structured error with code, `howToFix` and `docsUrl` for tools (14 of 15). Version in the path and spec, and a dated changelog (15). Total 95.\n\n### Payments \u0026 pricing: Sequenzy +15\n\n- Mailchimp Marketing API (25): No x402, MPP or L402 (0). Plan prices are public without a login, from $13 a month for Essentials, $20 for Standard and $350 for Premium with USD selected, rising with contacts through a selector. Nothing is priced per API call (10). The Free plan has 250 contacts and 500 sends a month with no time limit. We could not confirm that signup asks for no card, and the 14-day trial of a paid plan needs payment details, so 15 of 20. A person signs up in a browser and creates a key or approves OAuth (0).\n- Sequenzy (40): No x402, MPP or L402 (0). Prices are public as volume tiers from $19 for 15,000 emails to $2,999 for 5 million, without a per-email overage rate (10 of 20). Free plan of 2,500 emails a month with no card (20). Agents can register through `service_auth`, but the user has to confirm a code in a Sequenzy browser page, and plan payment is through Stripe (10 of 20). Total 40.\n\n### Maintenance \u0026 community: Sequenzy +10\n\n- Mailchimp Marketing API (68): Release 1.0.3 of the TypeScript, Python and Go client libraries, the first tag in each, is dated 5 October 2026, 30 days before this check (30). The TypeScript library's 1.0.03 of 13 October changes only version strings and the lockfile, so it counts half and doesn't set recency. Dated releases in the 90 days from 6 August include the CLI's 0.0.212 and 0.0.213 and Swift 1.0.0 on 18 September, Java 1.0.0 and C# 1.0.0 and 1.0.1 on 21 September, and 1.0.3 across the libraries on 5 October (20). The API changelog has no entry in that time. A public changelog whose newest entry is 19 August 2025, an API help address, and a help centre article saying support is not trained for in-depth API questions. We saw no public issue replies (5 of 15). Nine official client libraries generated from the current specification, with the TypeScript package absent from npm on 8 October (8 of 15, partly met). Each repository has a workflow that compiles and tests, whose results we could not see, and release 1.0.3 removed the `LICENSE` and `NOTICE` files added on 18 September (5 of 10, partly met). 30 + 20 + 5 + 8 + 5 = 68.\n- Sequenzy (78): sequenzy 2.1.56, @sequenzy/mcp 0.0.246 and @sequenzy/cli 0.0.202 were all published on 6 November 2026 (30). 18 SDK, 105 MCP and 93 CLI releases in the 90 days from 8 August, and dated changelog entries on most days (20). A closed service with a public changelog and support answered by the cofounders per the about page. GitHub issues weren't read, as the GitHub API refused our requests for its rate limit (12 of 15). Listed in the official MCP registry as io.github.polnikale/sequenzy-mcp, but the entry is at 0.0.36 against npm's 0.0.246, and the TypeScript SDK is current (10 of 15). MIT packages released daily, the MCP server and CLI still at 0.0.x (6 of 10). Total 78.\n\n### Transparency \u0026 trust: Mailchimp Marketing API +7\n\n- Mailchimp Marketing API (74): Closed service with published terms, an API Use Policy and a named contracting entity. The client libraries declare Apache-2.0 in package metadata (15). A data processing addendum effective 26 September 2024 covers deletion or return on termination without a stated period, and the Intuit Global Privacy Statement of 9 March 2026 is the privacy document. The terms let Mailchimp use inputs and outputs of its AI functions, customer data included, for machine learning, with a preference in account settings. No retention periods for marketing data were found (18). No deprecation policy was found. The API Use Policy says the APIs can change by a posting or an email. Dated notices exist, such as key expiry from 22 June 2026 in the help centre (8). A sub-processor list with locations is public and was last updated on 29 February 2024, and the security page places Mailchimp's own servers in United States data centres (14).\n- Sequenzy (67): A closed service. The SDK, MCP server and CLI are MIT on npm. The terms (30 June 2026) don't name the contracting entity in their text or a governing jurisdiction; the footer names Nic Tech Solutions, LLC (15 of 30). Privacy policy of 16 September 2026 and a public DPA agree on processing, and the terms say data is deleted within 30 days of termination (24 of 30). Deprecated endpoints are marked and kept as compatibility aliases; no written deprecation policy with notice periods (10 of 20). The DPA names its core sub-processors with their purpose; data locations aren't stated (15 of 20). Total 64.\n\n## Score by category\n\n| Category | Weight | Mailchimp Marketing API | Sequenzy | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 72 | 38 | Mailchimp Marketing API +34 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 76 | 95 | Sequenzy +19 |\n| Agent ergonomics | 13% (16.2 this run) | 73 | 69 | Mailchimp Marketing API +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 46 | 67 | Sequenzy +21 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 40 | Sequenzy +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 68 | 78 | Sequenzy +10 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 74 | 67 | Mailchimp Marketing API +7 |\n| Negative events | ≤15 | -2 | 0 | |\n| **Total** | | **60.2 · C** | **63.7 · B** | |\n\n## Facts side by side\n\n| Fact | Mailchimp Marketing API | Sequenzy |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Intuit Mailchimp | Nic Tech Solutions, LLC |\n| Hosted endpoint | `https://api.mailchimp.com/3.0` | `https://api.sequenzy.com/v1/mcp` |\n| Transports | HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under Mailchimp's Standard Terms of Use and API Use Policy. The generated client libraries declare Apache-2.0 in their package metadata | none |\n| Tools exposed | none | 306 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.polnikale/sequenzy-mcp` |\n| Last release | 2026-10-05 | 2026-11-06 |\n| Terms last updated | no date given | 2026-06-30 |\n| Privacy policy last updated | 2026-03-09 | 2026-09-16 |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 278k npm/wk, 111k PyPI/wk | 2.4k npm/wk |\n\n## How the scores have moved\n\n### Mailchimp Marketing API\n\n- +2.8 on 4 November 2026: correction, time\n\n### Sequenzy\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Mailchimp Marketing API.** A public OpenAPI 3.1 file covers all 297 operations, every docs page has a Markdown copy, and responses can be trimmed with `fields`. An API key carries full account access with no read-only option. The quick start's TypeScript package was not on npm on 8 October 2026, and the changelog's newest entry is 19 August 2025.\n\n**Sequenzy.** Scoped keys with read-only and drafts-only presets, a 475-operation OpenAPI spec, idempotent sends and near-daily dated releases make it workable for an agent. The MCP server lists about 306 tools, which is heavy on context, and there is no status page, SLA or published request limit table.\n\n## Before you call either\n\n### Mailchimp Marketing API\n\n1. Send the key or OAuth token as `Authorization: Bearer` to `https://api.mailchimp.com/3.0/`. Treat it as full account access and keep it server-side\n2. Address a contact by the MD5 hash of the lowercase email address, and use PUT on `/lists/{list_id}/members/{subscriber_hash}` so a retry does not create a duplicate\n3. Ask a person before POST `/campaigns/{campaign_id}/actions/send`. Read `/campaigns/{campaign_id}/send-checklist` and use `actions/test` first\n4. Keep to 10 concurrent requests per user, and send large jobs to `/batches`. A 429 names no wait time, so back off and retry\n5. Add `fields=` to every list call and set `count` (default 10, maximum 1,000) with `offset`\n6. Set `is_syncing` to true when loading historical events so they do not trigger automations\n\n### Sequenzy\n\n1. Connect with a drafts-only or read-only key unless the task must send, and widen permissions only when an error names the missing scope\n2. Send an `Idempotency-Key` with each transactional send and reuse it unchanged after an uncertain result\n3. Read `structuredContent.error.code` and `howToFix` on a failed tool call before retrying; the client doesn't retry\n4. Call `get_account` and `select_company` first when the key can reach more than one workspace\n5. On 429 wait for Retry-After and read the RateLimit-Remaining header\n\n## Questions\n\n### Which is better for AI agents, Mailchimp Marketing API or Sequenzy?\n\nSequenzy scores 63.7 (B) on agent readiness against Mailchimp Marketing API's 60.2 (C), and leads in 4 of 7 scored categories. Mailchimp Marketing API leads on reliability and transparency \u0026 trust.\n\n### Do Mailchimp Marketing API and Sequenzy need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Mailchimp Marketing API and Sequenzy without installing anything?\n\nYes. Mailchimp Marketing API has a hosted endpoint at https://api.mailchimp.com/3.0 and Sequenzy at https://api.sequenzy.com/v1/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/mailchimp-marketing-vs-sequenzy.json, and with the fewest tokens: https://www.anchorterminal.com/compare/mailchimp-marketing-vs-sequenzy.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"mailchimp-marketing\", \"b\": \"sequenzy\"}`. From a terminal: `anchor compare mailchimp-marketing sequenzy`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/mailchimp-marketing.json and https://www.anchorterminal.com/api/v1/tools/sequenzy.json\n\n## Other comparisons with Mailchimp Marketing API or Sequenzy\n\n- [ActiveCampaign vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/activecampaign-vs-mailchimp-marketing.md)\n- [ActiveCampaign vs Sequenzy](https://www.anchorterminal.com/compare/activecampaign-vs-sequenzy.md)\n- [Braze vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/braze-vs-mailchimp-marketing.md)\n- [Braze vs Sequenzy](https://www.anchorterminal.com/compare/braze-vs-sequenzy.md)\n- [CleverTap vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/clevertap-vs-mailchimp-marketing.md)\n- [CleverTap vs Sequenzy](https://www.anchorterminal.com/compare/clevertap-vs-sequenzy.md)\n- [Customer.io vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/customer-io-vs-mailchimp-marketing.md)\n- [Customer.io vs Sequenzy](https://www.anchorterminal.com/compare/customer-io-vs-sequenzy.md)\n- [Iterable vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/iterable-vs-mailchimp-marketing.md)\n- [Iterable vs Sequenzy](https://www.anchorterminal.com/compare/iterable-vs-sequenzy.md)\n- [Klaviyo API + MCP vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/klaviyo-vs-mailchimp-marketing.md)\n- [Klaviyo API + MCP vs Sequenzy](https://www.anchorterminal.com/compare/klaviyo-vs-sequenzy.md)\n- [Mailchimp Marketing API vs MoEngage](https://www.anchorterminal.com/compare/mailchimp-marketing-vs-moengage.md)\n- [Mailchimp Marketing API vs Nitrosend](https://www.anchorterminal.com/compare/mailchimp-marketing-vs-nitrosend.md)\n- [Mailchimp Marketing API vs Omnisend](https://www.anchorterminal.com/compare/mailchimp-marketing-vs-omnisend.md)\n- [MoEngage vs Sequenzy](https://www.anchorterminal.com/compare/moengage-vs-sequenzy.md)\n- [Nitrosend vs Sequenzy](https://www.anchorterminal.com/compare/nitrosend-vs-sequenzy.md)\n- [Omnisend vs Sequenzy](https://www.anchorterminal.com/compare/omnisend-vs-sequenzy.md)\n- [Dreamlit vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/dreamlit-vs-mailchimp-marketing.md)\n- [Dreamlit vs Sequenzy](https://www.anchorterminal.com/compare/dreamlit-vs-sequenzy.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Mailchimp Marketing API vs Sequenzy", "url": "" } ], "description": "Sequenzy scores 63.7 (B) to Mailchimp Marketing's 60.2 (C) for marketing audiences. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Mailchimp Marketing API C 60.2", "Sequenzy B 63.7", "scores" ], "h1": "Mailchimp Marketing API vs Sequenzy", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/mailchimp-marketing-vs-sequenzy", "published": "2026-10-01", "section": "tools", "title": "Mailchimp Marketing vs Sequenzy for AI agents (2026) | Anchor Terminal", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-sequenzy" }, "tokens": { "markdown": 5200, "slim": 3330 }, "version": 1 }