{ "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", "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": 57.4, "grade": "C", "agentReady": false, "rank": 609, "ranked": true, "rankOf": 950, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 63, "payments": 25, "reliability": 60, "schema": 76, "security": 46, "transparency": 74 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": -2, "negativeNotes": [ "8 October 2026. The quick start tells users to run `npm install @mailchimp/mailchimp-marketing`, and the npm registry answers 404 for that name. Its `pip install mailchimp-marketing` installs version 3.0.80 from November 2022, which has no `MailchimpClient` class as the quick start's code needs. The Go, Ruby, Rust and PHP names resolve, so 2 for a claim the listing can't meet in two of nine languages (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, and `pip install mailchimp-marketing` installs a 2022 library with a different client class", "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.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57.4 } ], "editorialScores": { "ergonomics": 73, "maintenance": 63, "payments": 25, "reliability": 60, "schema": 76, "security": 46, "transparency": 55 }, "provenanceScore": 92 }, "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": 92 }, "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-10-10T03:53:33.145593099Z", "lastOk": true, "lastStatus": 401, "lastMs": 292, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 99.52, "uptime30d": 99.52, "p50ms24h": 315, "p95ms24h": 509, "samples24h": 209, "samples30d": 209, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 168 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.mailchimp.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:50:46.815731894Z" }, "versions": [ { "registry": "github", "name": "mailchimp/mailchimp-marketing-typescript-sdk", "version": "1.0.3", "released": "2026-10-05", "seenAt": "2026-10-09T17:03:25.010553211Z" }, { "registry": "npm", "name": "@mailchimp/mailchimp_marketing", "version": "3.0.80", "seenAt": "2026-10-09T17:03:23.925729063Z" }, { "registry": "pypi", "name": "mailchimp-marketing", "version": "3.0.80", "released": "2022-11-02", "seenAt": "2026-10-09T17:03:24.813754429Z" } ], "githubStars": 0, "npmWeekly": 230835, "pypiWeekly": 111727, "securityTxt": { "url": "https://mailchimp.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-10-09T15:40:06.339407223Z" }, "llmsTxt": { "url": "https://mailchimp.com/developer/marketing/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:02:15.064783349Z" }, "pages": [ { "url": "https://mailchimp.com/developer/release-notes/", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:41:40.46239945Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "73f208452255" }, { "url": "https://mailchimp.com/help/about-mailchimp-pricing-plans/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:41:43.291283234Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "174dbb82057e" }, { "url": "https://mailchimp.com/pricing/marketing/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:41:46.531152174Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9acf2507300c" }, { "url": "https://www.intuit.com/privacy/statement/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:51:15.940538743Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "bdf88eaea616" }, { "url": "https://mailchimp.com/legal/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:41:44.586074781Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "24853a4c12ab" } ], "updatedAt": "2026-10-10T03:53:33.145593099Z" } }, "answer": "MoEngage scores 65.2 (B) on agent readiness against Mailchimp Marketing API's 57.4 (C), and leads in 5 of 7 scored categories. Mailchimp Marketing API leads on agent ergonomics and payments \u0026 pricing.", "b": { "slug": "moengage", "name": "MoEngage", "vendor": "MoEngage, Inc.", "vendorUrl": "https://www.moengage.com", "kind": "http-api", "category": "lifecycle-marketing", "summary": "MoEngage is a hosted customer engagement platform that stores user profiles and events, builds segments and sends campaigns and flows by push, email, SMS and WhatsApp. Agents reach it through REST APIs and a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/moengage", "markdownUrl": "https://www.anchorterminal.com/tools/moengage.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/moengage.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/moengage.json", "license": "Proprietary service under MoEngage's Terms of Use and a customer agreement", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://mcp.moengage.com", "packages": [], "auth": "mixed", "authNotes": "Access needs a MoEngage customer workspace, which is sold through sales. A dashboard user creates API keys under Settings, Account, APIs. The default is HTTP Basic with the Workspace ID as username and the API key as password, with separate keys for Data, Push, Inform, Campaigns and Personalise. An API key dashboard, in early access and enabled on request, adds named keys scoped to chosen API groups, OAuth 2.0 client credentials (access tokens of 5 to 60 minutes, refresh tokens of 30 days, issued at `https://oauth2-{dc}.moengage.com`) and AWS STS role ARNs. Segmentation and Inform accept Basic only. The MCP server uses OAuth with the user's own MoEngage login and role, a second factor, and a 30-day session with a 7-day idle timeout. No app review or partner approval was found.", "pricing": "paid", "pricingNotes": "No public prices. https://www.moengage.com/plans-and-pricing/ lists Growth and Enterprise plans, counted in monthly tracked users, with a sales contact and a one-year minimum commitment. No free tier, trial or self-serve signup was found. Each workspace has Live and Test environments and Inform has a sandbox host, but both sit inside a customer account, so an agent can't start without a contract. API and MCP calls aren't priced per call in any page read (checked 2026-10-09).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API documentation, the OpenAPI files, the pricing page or the legal pages (checked 2026-10-09).", "endpoints": [] }, "toolCount": 52, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://www.moengage.com/docs/api/introduction", "llmsTxt": "https://www.moengage.com/docs/llms.txt", "openapi": "https://www.moengage.com/docs/api/data/data.yaml", "capabilities": [ "marketing.profiles", "marketing.events", "marketing.segments", "marketing.campaigns", "marketing.journeys", "email.templates", "notify.push" ], "tags": [ "official", "hosted", "mcp", "oauth", "api-key", "openapi", "llms-txt", "closed-source", "sales-led", "enterprise", "eu-region", "status-page", "soc2", "sla" ], "lastRelease": "2026-10-09", "graded": true, "anchor": { "graded": true, "score": 65.2, "grade": "B", "agentReady": false, "rank": 327, "ranked": true, "rankOf": 950, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 68, "maintenance": 75, "payments": 0, "reliability": 74, "schema": 87, "security": 69, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "MoEngage publishes 36 OpenAPI files covering 140 operations, a per-endpoint rate limit table, Markdown docs and a hosted MCP server that builds drafts and leaves publishing to a person. No price, trial or self-serve signup is published, and on 17 August 2026 the Inform API in one data centre accepted requests for about 16 hours without sending the messages.", "bestFor": "A team already on MoEngage that wants an agent to update profiles, track events, build filter segments, draft Push and Email campaigns and read campaign, flow and analytics results.", "strengths": [ "36 public OpenAPI files with 140 operations, every one with a summary and description, and a 429 response documented on 103", "A rate limit table with numbers for every endpoint group, plus `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset` response headers", "The hosted MCP server at mcp.moengage.com uses OAuth tied to the user's role, masks PII attributes and cannot publish a campaign", "API keys can be scoped to chosen API groups, use OAuth 2.0 tokens of 5 to 60 minutes or AWS STS roles, and be limited by IP address", "A published SLA of 99.9 per cent monthly availability, a public DPA and a sub-processor list with locations dated 1 September 2026" ], "weaknesses": [ "No public price, free tier or trial. The pricing page lists Growth and Enterprise plans with a one-year minimum and a sales contact only", "On 17 August 2026 the Inform API in DC-03 returned HTTP 200 for about 16 hours while some messages were never sent, per the status page", "Scoped keys, OAuth 2.0 and AWS STS keys sit in an API key dashboard that is in early access and enabled on request", "Segmentation and Inform accept Basic authentication only, and new Push API keys can't be created", "No API deprecation policy was found, and no official server-side API client library was found in the documentation" ], "agentNotes": [ "Take the data centre number from the dashboard URL and call `https://api-{dc}.moengage.com`. Data can't be moved between data centres", "Send an `Idempotency-Key` header (UUID v4) on V5 campaign writes and test sends, and a `transaction_id` on Inform alerts, which deduplicates for 5 minutes", "Use internal event and attribute names in segment filters, and run `deep_validate_segment_filters` first. A wrong event name is accepted and the count later fails with no reason", "Use `in` with a list for text equality in segment filters. `equals` returns a 400 that names no field", "Reuse an OAuth access token until it nears expiry. The token endpoint allows 5 requests a minute and 30 per 10 minutes for each key" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 65.2 } ], "editorialScores": { "ergonomics": 68, "maintenance": 75, "payments": 0, "reliability": 74, "schema": 87, "security": 69, "transparency": 60 }, "provenanceScore": 89 }, "connect": { "http": "curl --request POST \\\n --url https://api-{dc}.moengage.com/v1/customer/YOUR_WORKSPACE_ID \\\n --header 'Authorization: Bearer YOUR_ACCESS_TOKEN' \\\n --header 'Content-Type: application/json' \\\n --data '{ \"type\": \"customer\", \"customer_id\": \"user_12345\" }'", "config": { "mcpServers": { "moengage": { "url": "https://mcp.moengage.com" } } } }, "letme": { "capability": "https://letme.dev/marketing.profiles", "tool": "https://letme.dev/moengage" }, "area": "communication", "provenance": { "legalEntity": "MoEngage, Inc.", "domain": "moengage.com", "domainRegistered": "2014-04-19", "endpointOnVendorDomain": true, "terms": "https://www.moengage.com/terms-of-use/", "privacy": "https://www.moengage.com/privacy-policy/", "statusPage": "https://status.moengage.com", "changelog": "https://www.moengage.com/docs/release-notes/product/2026/september-2026", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Terms of Use name MoEngage, Inc., a Delaware corporation, and say they govern the website and related software and services. They carry no date. The DPA and sub-processor list name MoEngage Global Inc.", "The acceptable use policy (last updated 14 May 2026) refers to a Master Service Agreement between MoEngage and its customers. That agreement isn't published.", "The privacy policy was last updated on 26 August 2026 and covers MoEngage as processor for its customers' end users.", "The API answers at api-{dc}.moengage.com and the MCP server at mcp.moengage.com, both on the vendor's domain.", "https://www.moengage.com/.well-known/security.txt returns 404. Reports go to the address in the responsible disclosure policy.", "Release notes are one page a month under /docs/release-notes/product/, with separate dated changelogs for each SDK.", "RDAP for moengage.com gives a registration date of 2014-04-19." ], "score": 89 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/moengage.json", "live": { "slug": "moengage", "probe": { "target": "https://mcp.moengage.com", "method": "get", "lastAt": "2026-10-10T03:53:35.125620945Z", "lastOk": true, "lastStatus": 401, "lastMs": 31, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 99.2, "uptime30d": 99.2, "p50ms24h": 36, "p95ms24h": 134, "samples24h": 125, "samples30d": 125, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 40, "ok": 39 } ] }, "vendorStatus": { "page": "https://status.moengage.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T03:58:28.483064795Z" }, "pages": [ { "url": "https://www.moengage.com/docs/release-notes/product/2026/september-2026", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:52:19.636830436Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "01e807658b5c" }, { "url": "https://www.moengage.com/plans-and-pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:52:23.984233527Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "159b4036728b" }, { "url": "https://www.moengage.com/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:52:24.146105363Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "cf0f65af7274" }, { "url": "https://www.moengage.com/terms-of-use/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:52:26.055494253Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3a3cf18334cc" } ], "updatedAt": "2026-10-10T03:58:28.483064795Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Intuit Mailchimp", "b": "MoEngage, Inc.", "name": "Vendor" }, { "a": "https://api.mailchimp.com/3.0", "b": "https://mcp.moengage.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "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": "Proprietary service under MoEngage's Terms of Use and a customer agreement", "name": "Licence" }, { "a": "none", "b": "52", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-05", "b": "2026-10-09", "name": "Last release" }, { "a": "no date given", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-03-09", "b": "2026-08-26", "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": "none", "name": "Popularity" } ], "faq": [ { "answer": "MoEngage scores 65.2 (B) on agent readiness against Mailchimp Marketing API's 57.4 (C), and leads in 5 of 7 scored categories. Mailchimp Marketing API leads on agent ergonomics and payments \u0026 pricing.", "question": "Which is better for AI agents, Mailchimp Marketing API or MoEngage?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Mailchimp Marketing API and MoEngage need an API key?" }, { "answer": "Yes. Mailchimp Marketing API has a hosted endpoint at https://api.mailchimp.com/3.0 and MoEngage at https://mcp.moengage.com.", "question": "Can an agent call Mailchimp Marketing API and MoEngage without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 73 against 68", "Payments \u0026 pricing, 25 against 0" ], "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": [ "Reliability, 74 against 60", "Schema \u0026 documentation, 87 against 76", "Security \u0026 auth, 69 against 46", "Maintenance \u0026 community, 75 against 63" ], "also": null, "goodFor": "A team already on MoEngage that wants an agent to update profiles, track events, build filter segments, draft Push and Email campaigns and read campaign, flow and analytics results.", "slug": "moengage", "watchFor": "No public price, free tier or trial. The pricing page lists Growth and Enterprise plans with a one-year minimum and a sales contact only" } ], "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-moengage.json", "title": "ActiveCampaign vs MoEngage", "url": "https://www.anchorterminal.com/compare/activecampaign-vs-moengage" }, { "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-moengage.json", "title": "Braze vs MoEngage", "url": "https://www.anchorterminal.com/compare/braze-vs-moengage" }, { "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-moengage.json", "title": "CleverTap vs MoEngage", "url": "https://www.anchorterminal.com/compare/clevertap-vs-moengage" }, { "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-moengage.json", "title": "Customer.io vs MoEngage", "url": "https://www.anchorterminal.com/compare/customer-io-vs-moengage" }, { "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-moengage.json", "title": "Iterable vs MoEngage", "url": "https://www.anchorterminal.com/compare/iterable-vs-moengage" }, { "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-moengage.json", "title": "Klaviyo API + MCP vs MoEngage", "url": "https://www.anchorterminal.com/compare/klaviyo-vs-moengage" }, { "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-omnisend.json", "title": "MoEngage vs Omnisend", "url": "https://www.anchorterminal.com/compare/moengage-vs-omnisend" } ], "scores": [ { "by": 14, "edge": "moengage", "key": "reliability", "mailchimp-marketing": 60, "moengage": 74, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 11, "edge": "moengage", "key": "schema", "mailchimp-marketing": 76, "moengage": 87, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 5, "edge": "mailchimp-marketing", "key": "ergonomics", "mailchimp-marketing": 73, "moengage": 68, "name": "Agent ergonomics", "weight": 13 }, { "by": 23, "edge": "moengage", "key": "security", "mailchimp-marketing": 46, "moengage": 69, "name": "Security \u0026 auth", "weight": 14 }, { "by": 25, "edge": "mailchimp-marketing", "key": "payments", "mailchimp-marketing": 25, "moengage": 0, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 12, "edge": "moengage", "key": "maintenance", "mailchimp-marketing": 63, "moengage": 75, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 1, "edge": "moengage", "key": "transparency", "mailchimp-marketing": 74, "moengage": 75, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "MoEngage scores 65.2 (B) on agent readiness against Mailchimp Marketing API's 57.4 (C), and leads in 5 of 7 scored categories. Mailchimp Marketing API leads on agent ergonomics and payments \u0026 pricing. Both do marketing audiences.", "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.", "moengage": "MoEngage publishes 36 OpenAPI files covering 140 operations, a per-endpoint rate limit table, Markdown docs and a hosted MCP server that builds drafts and leaves publishing to a person. No price, trial or self-serve signup is published, and on 17 August 2026 the Inform API in one data centre accepted requests for about 16 hours without sending the messages." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-moengage", "json": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-moengage.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-moengage.md", "slim": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-moengage.min.md" }, "markdown": "MoEngage scores 65.2 (B) on agent readiness against Mailchimp Marketing API's 57.4 (C), and leads in 5 of 7 scored categories. Mailchimp Marketing API leads on agent ergonomics and payments \u0026 pricing. Both do marketing audiences.\n\n- Mailchimp Marketing API: grade C, 57.4/100, rank #609 of 950. Markdown https://www.anchorterminal.com/tools/mailchimp-marketing.md · JSON https://www.anchorterminal.com/api/v1/tools/mailchimp-marketing.json\n- MoEngage: grade B, 65.2/100, rank #327 of 950. Markdown https://www.anchorterminal.com/tools/moengage.md · JSON https://www.anchorterminal.com/api/v1/tools/moengage.json\n- Best lifecycle marketing and customer engagement platforms for AI agents: https://www.anchorterminal.com/best/lifecycle-marketing/index.md\n- All 36 lifecycle marketing comparisons: https://www.anchorterminal.com/compare/lifecycle-marketing/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- Agent ergonomics, 73 against 68\n- Payments \u0026 pricing, 25 against 0\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### MoEngage (B)\n\nGood for: A team already on MoEngage that wants an agent to update profiles, track events, build filter segments, draft Push and Email campaigns and read campaign, flow and analytics results.\n\nAhead on:\n- Reliability, 74 against 60\n- Schema \u0026 documentation, 87 against 76\n- Security \u0026 auth, 69 against 46\n- Maintenance \u0026 community, 75 against 63\n\nWatch for: No public price, free tier or trial. The pricing page lists Growth and Enterprise plans with a one-year minimum and a sales contact only\n\n\n## Score by category\n\n| Category | Weight | Mailchimp Marketing API | MoEngage | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 60 | 74 | MoEngage +14 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 76 | 87 | MoEngage +11 |\n| Agent ergonomics | 13% (16.2 this run) | 73 | 68 | Mailchimp Marketing API +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 46 | 69 | MoEngage +23 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 0 | Mailchimp Marketing API +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 63 | 75 | MoEngage +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 74 | 75 | MoEngage +1 |\n| Negative events | ≤15 | -2 | 0 | |\n| **Total** | | **57.4 · C** | **65.2 · B** | |\n\n## Facts side by side\n\n| Fact | Mailchimp Marketing API | MoEngage |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Intuit Mailchimp | MoEngage, Inc. |\n| Hosted endpoint | `https://api.mailchimp.com/3.0` | `https://mcp.moengage.com` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Paid |\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 | Proprietary service under MoEngage's Terms of Use and a customer agreement |\n| Tools exposed | none | 52 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-05 | 2026-10-09 |\n| Terms last updated | no date given | no date given |\n| Privacy policy last updated | 2026-03-09 | 2026-08-26 |\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 | none |\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**MoEngage.** MoEngage publishes 36 OpenAPI files covering 140 operations, a per-endpoint rate limit table, Markdown docs and a hosted MCP server that builds drafts and leaves publishing to a person. No price, trial or self-serve signup is published, and on 17 August 2026 the Inform API in one data centre accepted requests for about 16 hours without sending the messages.\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### MoEngage\n\n1. Take the data centre number from the dashboard URL and call `https://api-{dc}.moengage.com`. Data can't be moved between data centres\n2. Send an `Idempotency-Key` header (UUID v4) on V5 campaign writes and test sends, and a `transaction_id` on Inform alerts, which deduplicates for 5 minutes\n3. Use internal event and attribute names in segment filters, and run `deep_validate_segment_filters` first. A wrong event name is accepted and the count later fails with no reason\n4. Use `in` with a list for text equality in segment filters. `equals` returns a 400 that names no field\n5. Reuse an OAuth access token until it nears expiry. The token endpoint allows 5 requests a minute and 30 per 10 minutes for each key\n\n## Questions\n\n### Which is better for AI agents, Mailchimp Marketing API or MoEngage?\n\nMoEngage scores 65.2 (B) on agent readiness against Mailchimp Marketing API's 57.4 (C), and leads in 5 of 7 scored categories. Mailchimp Marketing API leads on agent ergonomics and payments \u0026 pricing.\n\n### Do Mailchimp Marketing API and MoEngage 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 MoEngage without installing anything?\n\nYes. Mailchimp Marketing API has a hosted endpoint at https://api.mailchimp.com/3.0 and MoEngage at https://mcp.moengage.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/mailchimp-marketing-vs-moengage.json, and with the fewest tokens: https://www.anchorterminal.com/compare/mailchimp-marketing-vs-moengage.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"mailchimp-marketing\", \"b\": \"moengage\"}`. From a terminal: `anchor compare mailchimp-marketing moengage`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/mailchimp-marketing.json and https://www.anchorterminal.com/api/v1/tools/moengage.json\n\n## Other comparisons with Mailchimp Marketing API or MoEngage\n\n- [ActiveCampaign vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/activecampaign-vs-mailchimp-marketing.md)\n- [ActiveCampaign vs MoEngage](https://www.anchorterminal.com/compare/activecampaign-vs-moengage.md)\n- [Braze vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/braze-vs-mailchimp-marketing.md)\n- [Braze vs MoEngage](https://www.anchorterminal.com/compare/braze-vs-moengage.md)\n- [CleverTap vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/clevertap-vs-mailchimp-marketing.md)\n- [CleverTap vs MoEngage](https://www.anchorterminal.com/compare/clevertap-vs-moengage.md)\n- [Customer.io vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/customer-io-vs-mailchimp-marketing.md)\n- [Customer.io vs MoEngage](https://www.anchorterminal.com/compare/customer-io-vs-moengage.md)\n- [Iterable vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/iterable-vs-mailchimp-marketing.md)\n- [Iterable vs MoEngage](https://www.anchorterminal.com/compare/iterable-vs-moengage.md)\n- [Klaviyo API + MCP vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/klaviyo-vs-mailchimp-marketing.md)\n- [Klaviyo API + MCP vs MoEngage](https://www.anchorterminal.com/compare/klaviyo-vs-moengage.md)\n- [Mailchimp Marketing API vs Omnisend](https://www.anchorterminal.com/compare/mailchimp-marketing-vs-omnisend.md)\n- [MoEngage vs Omnisend](https://www.anchorterminal.com/compare/moengage-vs-omnisend.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Mailchimp Marketing API vs MoEngage", "url": "" } ], "description": "MoEngage scores 65.2 (B) to Mailchimp Marketing's 57.4 (C) for marketing audiences. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Mailchimp Marketing API C 57.4", "MoEngage B 65.2", "scores" ], "h1": "Mailchimp Marketing API vs MoEngage", "image": "https://www.anchorterminal.com/assets/og/compare-mailchimp-marketing-vs-moengage.png", "path": "/compare/mailchimp-marketing-vs-moengage", "published": "2026-10-01", "section": "tools", "title": "Mailchimp Marketing vs MoEngage for AI agents (2026) | Anchor Terminal", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-moengage" }, "tokens": { "markdown": 2450, "slim": 730 }, "version": 1 }