{ "data": { "a": { "slug": "braze", "name": "Braze", "vendor": "Braze, Inc.", "vendorUrl": "https://www.braze.com", "kind": "http-api", "category": "lifecycle-marketing", "summary": "Braze is a hosted engagement platform that stores customer profiles and events, builds segments and sends campaigns and Canvas journeys by email, SMS, push and in-app message. Agents reach it through a REST API and an official remote MCP server.", "url": "https://www.anchorterminal.com/tools/braze", "markdownUrl": "https://www.anchorterminal.com/tools/braze.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/braze.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/braze.json", "license": "Proprietary service under Braze's Main Subscription Agreement. The deprecated local MCP server on PyPI is MIT", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://mcp.braze.com/mcp", "packages": [], "auth": "mixed", "authNotes": "Access follows a Braze contract or trial, with no app review or partner approval. The REST API takes a workspace API key as a Bearer header at the instance's own host (15 instances, such as https://rest.iad-01.braze.com). A dashboard user creates the key with per-endpoint permissions such as `users.track` or `campaigns.list` and an optional IP allowlist, and neither can be edited afterwards. The remote MCP server takes only OAuth (authorisation code with PKCE S256, dynamic client registration, scopes `mcp:tools`, `mcp:resources` and `mcp:operator`). A company admin must turn on MCP OAuth access, each user needs the Use MCP Server permission per workspace, and calls run with that user's dashboard permissions. Companies that use IP allowlisting can't use the MCP server.", "pricing": "paid", "pricingNotes": "No public prices. Braze sells four editions (Go, Select, Pro, Enterprise) by contract, sized by monthly active users and Action Credits, and the pricing page says there is no free plan. A 14-day free trial is open at try.braze.com, and we couldn't read whether it asks for a card. There's no separate sandbox, and API and MCP calls aren't priced on their own (https://www.braze.com/pricing, checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the MCP pages or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 71, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://www.braze.com/docs/api/home", "llmsTxt": "https://www.braze.com/llms.txt", "capabilities": [ "marketing.profiles", "marketing.events", "marketing.campaigns", "marketing.journeys", "marketing.segments" ], "tags": [ "official", "hosted", "mcp", "oauth", "api-key", "closed-source", "llms-txt", "sales-led", "enterprise", "eu-region", "status-page", "soc2" ], "lastRelease": "2026-09-17", "graded": true, "anchor": { "graded": true, "score": 61.2, "grade": "C", "agentReady": false, "rank": 431, "ranked": true, "rankOf": 842, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 50, "maintenance": 69, "payments": 10, "reliability": 70, "schema": 68, "security": 77, "transparency": 83 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "The REST API covers profiles, events, sends and exports with keys limited to named endpoints, and the remote MCP server adds 71 tools under OAuth with PKCE that return no user-level personal data. No OpenAPI document, idempotency keys, published price or SLA were found, and MCP writes run without a confirmation step.", "bestFor": "A company already on Braze that wants an agent to read campaign and Canvas results, manage catalogues and templates through MCP, or write profiles and trigger sends through REST.", "strengths": [ "REST API keys carry per-endpoint permissions and optional IP allowlists, and a key's scope can't be edited after creation", "Remote MCP server with OAuth, PKCE S256, dynamic client registration and three scopes, generally available since 17 September 2026", "MCP tools return no user-level personal data, and the Use MCP Server permission is off by default for each workspace", "Rate limits published per endpoint, with `X-RateLimit-Limit`, `-Remaining` and `-Reset` headers on every response", "Sub-processor list of 1 June 2026 with locations, 30 days' notice of additions and hosting regions named for six countries or regions" ], "weaknesses": [ "No public prices. Editions, monthly active users and Action Credits are sold by contract, and the pricing page says there is no free plan", "No OpenAPI document found. The machine-readable contract is a public Postman collection", "No idempotency keys on sends or `/users/track`, and Braze says it can't replay REST calls that fail during an incident", "71 MCP tools with no documented toolsets, 21 of them limited to beta programmes", "Edits made through individual MCP update tools don't appear in campaign edit history, and Operator Connect acts without per-step approval" ], "agentNotes": [ "Use the REST host for the customer's instance, such as https://rest.iad-01.braze.com or https://rest.fra-01.braze.eu. A key sent to the wrong instance returns 401", "Create a REST key with only the permissions the task needs. Scope and IP allowlist can't be edited later, so a change means a new key", "Call `get_workspaces` first on MCP. Every other tool needs the returned workspace id as `app_group_id`, and the wrong workspace is a documented failure", "Use REST for profiles, events and sends. The MCP server has no user-level tools and can't trigger a message to a named user", "Treat `\"message\": \"success\"` as queued, not delivered. Add a `group_id` to `/users/track` and poll `/users/track/status`, and don't resend a trigger call blindly" ], "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": 61.2 } ], "editorialScores": { "ergonomics": 50, "maintenance": 69, "payments": 10, "reliability": 70, "schema": 68, "security": 77, "transparency": 69 }, "provenanceScore": 96 }, "connect": { "http": "curl --location -g --request GET 'https://rest.iad-01.braze.com/campaigns/list?page=0\u0026include_archived=false\u0026sort_direction=desc' \\\n--header 'Authorization: Bearer YOUR-REST-API-KEY'", "config": { "mcpServers": { "braze": { "url": "https://mcp.braze.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/marketing.profiles", "tool": "https://letme.dev/braze" }, "area": "communication", "provenance": { "legalEntity": "Braze, Inc.", "domain": "braze.com", "domainRegistered": "2000-01-19", "endpointOnVendorDomain": true, "terms": "https://www.braze.com/company/legal/terms", "privacy": "https://www.braze.com/company/legal/privacy", "statusPage": "https://status.braze.com", "changelog": "https://www.braze.com/docs/releases/home", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The Main Subscription Agreement (last updated 13 October 2025) names Braze, Inc., and the privacy policy (last updated 23 June 2026) says it is a U.S. company headquartered in New York.", "REST hosts are on braze.com for the US, Australia, Indonesia, Japan and South Korea and on braze.eu for the EU. The MCP server is at mcp.braze.com and mcp.braze.eu.", "www.braze.com/.well-known/security.txt expires 2031-01-01, gives security@braze.com and points its policy to hackerone.com/braze_inc.", "status.braze.com redirects to braze.statuspage.io.", "RDAP for braze.com gives a registration date of 2000-01-19.", "The DPA (revision 28 August 2025), the sub-processor list (1 June 2026) and the security datasheet (14 April 2026) are PDFs linked from braze.com/company/legal." ], "score": 96 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/braze.json", "live": { "slug": "braze", "probe": { "target": "https://mcp.braze.com/mcp", "method": "get", "lastAt": "2026-10-09T10:42:38.441128834Z", "lastOk": true, "lastStatus": 401, "lastMs": 275, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 263, "p95ms24h": 295, "samples24h": 207, "samples30d": 207, "days": [ { "date": "2026-10-08", "probes": 93, "ok": 93 }, { "date": "2026-10-09", "probes": 114, "ok": 114 } ] }, "vendorStatus": { "page": "https://status.braze.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T10:41:26.952769129Z" }, "securityTxt": { "url": "https://braze.com/.well-known/security.txt", "state": "valid", "expires": "2031-01-01T04:59:00.000Z", "checkedAt": "2026-10-08T15:39:06.359227057Z" }, "pages": [ { "url": "https://www.braze.com/docs/releases/home", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:26:48.434408153Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c84a0deb311a" }, { "url": "https://www.braze.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:26:50.345609932Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "90f9bf6b6c9c" }, { "url": "https://www.braze.com/company/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:26:44.004338511Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "2328a04f813f" }, { "url": "https://www.braze.com/company/legal/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:26:46.13034848Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "066935a8590e" } ], "updatedAt": "2026-10-09T10:42:38.441128834Z" } }, "answer": "Braze scores 61.2 (C) on agent readiness against Mailchimp Marketing API's 57.4 (C), and leads in 4 of 7 scored categories. Mailchimp Marketing API leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing.", "b": { "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": 549, "ranked": true, "rankOf": 842, "categoryRank": 4, "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-09T10:42:48.242583118Z", "lastOk": true, "lastStatus": 401, "lastMs": 333, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 305, "p95ms24h": 415, "samples24h": 33, "samples30d": 33, "days": [ { "date": "2026-10-09", "probes": 33, "ok": 33 } ] }, "vendorStatus": { "page": "https://status.mailchimp.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-09T07:58:08.512261949Z" }, "updatedAt": "2026-10-09T10:42:48.242583118Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Braze, Inc.", "b": "Intuit Mailchimp", "name": "Vendor" }, { "a": "https://mcp.braze.com/mcp", "b": "https://api.mailchimp.com/3.0", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Braze's Main Subscription Agreement. The deprecated local MCP server on PyPI is MIT", "b": "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", "name": "Licence" }, { "a": "71", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-17", "b": "2026-10-05", "name": "Last release" }, { "a": "2025-10-13", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-06-23", "b": "2026-03-09", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "yes", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "278k npm/wk, 111k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Braze scores 61.2 (C) on agent readiness against Mailchimp Marketing API's 57.4 (C), and leads in 4 of 7 scored categories. Mailchimp Marketing API leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing.", "question": "Which is better for AI agents, Braze or Mailchimp Marketing API?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Braze and Mailchimp Marketing API need an API key?" }, { "answer": "Yes. Braze has a hosted endpoint at https://mcp.braze.com/mcp and Mailchimp Marketing API at https://api.mailchimp.com/3.0.", "question": "Can an agent call Braze and Mailchimp Marketing API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 70 against 60", "Security \u0026 auth, 77 against 46", "Maintenance \u0026 community, 69 against 63", "Transparency \u0026 trust, 83 against 74" ], "also": null, "goodFor": "A company already on Braze that wants an agent to read campaign and Canvas results, manage catalogues and templates through MCP, or write profiles and trigger sends through REST.", "slug": "braze", "watchFor": "No public prices. Editions, monthly active users and Action Credits are sold by contract, and the pricing page says there is no free plan" }, { "aheadOn": [ "Schema \u0026 documentation, 76 against 68", "Agent ergonomics, 73 against 50", "Payments \u0026 pricing, 25 against 10" ], "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" } ], "job": { "capability": "marketing.profiles", "name": "Marketing profiles" }, "others": [ { "json": "https://www.anchorterminal.com/compare/activecampaign-vs-braze.json", "title": "ActiveCampaign vs Braze", "url": "https://www.anchorterminal.com/compare/activecampaign-vs-braze" }, { "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/braze-vs-customer-io.json", "title": "Braze vs Customer.io", "url": "https://www.anchorterminal.com/compare/braze-vs-customer-io" }, { "json": "https://www.anchorterminal.com/compare/braze-vs-iterable.json", "title": "Braze vs Iterable", "url": "https://www.anchorterminal.com/compare/braze-vs-iterable" }, { "json": "https://www.anchorterminal.com/compare/braze-vs-klaviyo.json", "title": "Braze vs Klaviyo API + MCP", "url": "https://www.anchorterminal.com/compare/braze-vs-klaviyo" }, { "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/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/klaviyo-vs-mailchimp-marketing.json", "title": "Klaviyo API + MCP vs Mailchimp Marketing API", "url": "https://www.anchorterminal.com/compare/klaviyo-vs-mailchimp-marketing" } ], "scores": [ { "braze": 70, "by": 10, "edge": "braze", "key": "reliability", "mailchimp-marketing": 60, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "braze": 68, "by": 8, "edge": "mailchimp-marketing", "key": "schema", "mailchimp-marketing": 76, "name": "Schema \u0026 documentation", "weight": 13 }, { "braze": 50, "by": 23, "edge": "mailchimp-marketing", "key": "ergonomics", "mailchimp-marketing": 73, "name": "Agent ergonomics", "weight": 13 }, { "braze": 77, "by": 31, "edge": "braze", "key": "security", "mailchimp-marketing": 46, "name": "Security \u0026 auth", "weight": 14 }, { "braze": 10, "by": 15, "edge": "mailchimp-marketing", "key": "payments", "mailchimp-marketing": 25, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "braze": 69, "by": 6, "edge": "braze", "key": "maintenance", "mailchimp-marketing": 63, "name": "Maintenance \u0026 community", "weight": 7 }, { "braze": 83, "by": 9, "edge": "braze", "key": "transparency", "mailchimp-marketing": 74, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Braze scores 61.2 (C) on agent readiness against Mailchimp Marketing API's 57.4 (C), and leads in 4 of 7 scored categories. Mailchimp Marketing API leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing. Both do marketing profiles.", "verdicts": { "braze": "The REST API covers profiles, events, sends and exports with keys limited to named endpoints, and the remote MCP server adds 71 tools under OAuth with PKCE that return no user-level personal data. No OpenAPI document, idempotency keys, published price or SLA were found, and MCP writes run without a confirmation step.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/braze-vs-mailchimp-marketing", "json": "https://www.anchorterminal.com/compare/braze-vs-mailchimp-marketing.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/braze-vs-mailchimp-marketing.md", "slim": "https://www.anchorterminal.com/compare/braze-vs-mailchimp-marketing.min.md" }, "markdown": "Braze scores 61.2 (C) on agent readiness against Mailchimp Marketing API's 57.4 (C), and leads in 4 of 7 scored categories. Mailchimp Marketing API leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing. Both do marketing profiles.\n\n- Braze: grade C, 61.2/100, rank #431 of 842. Markdown https://www.anchorterminal.com/tools/braze.md · JSON https://www.anchorterminal.com/api/v1/tools/braze.json\n- Mailchimp Marketing API: grade C, 57.4/100, rank #549 of 842. Markdown https://www.anchorterminal.com/tools/mailchimp-marketing.md · JSON https://www.anchorterminal.com/api/v1/tools/mailchimp-marketing.json\n\n## Which one, for what\n\n### Braze (C)\n\nGood for: A company already on Braze that wants an agent to read campaign and Canvas results, manage catalogues and templates through MCP, or write profiles and trigger sends through REST.\n\nAhead on:\n- Reliability, 70 against 60\n- Security \u0026 auth, 77 against 46\n- Maintenance \u0026 community, 69 against 63\n- Transparency \u0026 trust, 83 against 74\n\nWatch for: No public prices. Editions, monthly active users and Action Credits are sold by contract, and the pricing page says there is no free plan\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- Schema \u0026 documentation, 76 against 68\n- Agent ergonomics, 73 against 50\n- Payments \u0026 pricing, 25 against 10\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\n## Score by category\n\n| Category | Weight | Braze | Mailchimp Marketing API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 60 | Braze +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 68 | 76 | Mailchimp Marketing API +8 |\n| Agent ergonomics | 13% (16.2 this run) | 50 | 73 | Mailchimp Marketing API +23 |\n| Security \u0026 auth | 14% (17.5 this run) | 77 | 46 | Braze +31 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 25 | Mailchimp Marketing API +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 69 | 63 | Braze +6 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 83 | 74 | Braze +9 |\n| Negative events | ≤15 | 0 | -2 | |\n| **Total** | | **61.2 · C** | **57.4 · C** | |\n\n## Facts side by side\n\n| Fact | Braze | Mailchimp Marketing API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Braze, Inc. | Intuit Mailchimp |\n| Hosted endpoint | `https://mcp.braze.com/mcp` | `https://api.mailchimp.com/3.0` |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under Braze's Main Subscription Agreement. The deprecated local MCP server on PyPI is MIT | 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 |\n| Tools exposed | 71 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-17 | 2026-10-05 |\n| Terms last updated | 2025-10-13 | no date given |\n| Privacy policy last updated | 2026-06-23 | 2026-03-09 |\n| Customer content may train models | not found in the text | yes |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | none | 278k npm/wk, 111k PyPI/wk |\n\n## Verdicts\n\n**Braze.** The REST API covers profiles, events, sends and exports with keys limited to named endpoints, and the remote MCP server adds 71 tools under OAuth with PKCE that return no user-level personal data. No OpenAPI document, idempotency keys, published price or SLA were found, and MCP writes run without a confirmation step.\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## Before you call either\n\n### Braze\n\n1. Use the REST host for the customer's instance, such as https://rest.iad-01.braze.com or https://rest.fra-01.braze.eu. A key sent to the wrong instance returns 401\n2. Create a REST key with only the permissions the task needs. Scope and IP allowlist can't be edited later, so a change means a new key\n3. Call `get_workspaces` first on MCP. Every other tool needs the returned workspace id as `app_group_id`, and the wrong workspace is a documented failure\n4. Use REST for profiles, events and sends. The MCP server has no user-level tools and can't trigger a message to a named user\n5. Treat `\"message\": \"success\"` as queued, not delivered. Add a `group_id` to `/users/track` and poll `/users/track/status`, and don't resend a trigger call blindly\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## Questions\n\n### Which is better for AI agents, Braze or Mailchimp Marketing API?\n\nBraze scores 61.2 (C) on agent readiness against Mailchimp Marketing API's 57.4 (C), and leads in 4 of 7 scored categories. Mailchimp Marketing API leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing.\n\n### Do Braze and Mailchimp Marketing API need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Braze and Mailchimp Marketing API without installing anything?\n\nYes. Braze has a hosted endpoint at https://mcp.braze.com/mcp and Mailchimp Marketing API at https://api.mailchimp.com/3.0.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/braze-vs-mailchimp-marketing.json, and with the fewest tokens: https://www.anchorterminal.com/compare/braze-vs-mailchimp-marketing.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"braze\", \"b\": \"mailchimp-marketing\"}`. From a terminal: `anchor compare braze mailchimp-marketing`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/braze.json and https://www.anchorterminal.com/api/v1/tools/mailchimp-marketing.json\n\n## Other comparisons with Braze or Mailchimp Marketing API\n\n- [ActiveCampaign vs Braze](https://www.anchorterminal.com/compare/activecampaign-vs-braze.md)\n- [ActiveCampaign vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/activecampaign-vs-mailchimp-marketing.md)\n- [Braze vs Customer.io](https://www.anchorterminal.com/compare/braze-vs-customer-io.md)\n- [Braze vs Iterable](https://www.anchorterminal.com/compare/braze-vs-iterable.md)\n- [Braze vs Klaviyo API + MCP](https://www.anchorterminal.com/compare/braze-vs-klaviyo.md)\n- [Customer.io vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/customer-io-vs-mailchimp-marketing.md)\n- [Iterable vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/iterable-vs-mailchimp-marketing.md)\n- [Klaviyo API + MCP vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/klaviyo-vs-mailchimp-marketing.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "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": "Braze vs Mailchimp Marketing API", "url": "" } ], "description": "Braze scores 61.2 (C) on agent readiness against Mailchimp Marketing API's 57.4 (C), and leads in 4 of 7 scored categories. Mailchimp Marketing API leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing. Both do marketing profiles. Category scores, facts…", "facts": [ "Braze C 61.2", "Mailchimp Marketing API C 57.4", "scores" ], "h1": "Braze vs Mailchimp Marketing API", "image": "https://www.anchorterminal.com/assets/og/compare-braze-vs-mailchimp-marketing.png", "path": "/compare/braze-vs-mailchimp-marketing", "published": "2026-10-01", "section": "tools", "title": "Braze vs Mailchimp Marketing API for AI agents, C 61.2 vs C 57.4", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/braze-vs-mailchimp-marketing" }, "tokens": { "markdown": 2200, "slim": 780 }, "version": 1 }