{ "data": { "a": { "slug": "activecampaign", "name": "ActiveCampaign", "vendor": "ActiveCampaign, LLC", "vendorUrl": "https://www.activecampaign.com", "kind": "http-api", "category": "lifecycle-marketing", "summary": "ActiveCampaign is a hosted marketing automation platform for email, SMS and WhatsApp with a built-in CRM. Its v3 REST API and an official remote MCP server cover contacts, lists, tags, segments, campaigns, automations and deals.", "url": "https://www.anchorterminal.com/tools/activecampaign", "markdownUrl": "https://www.anchorterminal.com/tools/activecampaign.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/activecampaign.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/activecampaign.json", "dns": "activecampaign.grade.anchorterminal.com", "license": "Proprietary service under ActiveCampaign's terms of service and API licence agreement", "transports": [ "http", "streamable-http" ], "packages": [], "auth": "mixed", "authNotes": "Self-serve. The REST API takes an `Api-Token` header, and each user has one key, shown under Settings, Developer with the account's base URL. No scopes, read-only keys or OAuth for the REST API were found in the reviewed documentation. The remote MCP server uses an account-specific URL from the same page, and the user signs in to ActiveCampaign and approves the connection. Event tracking posts an event key and account ID in the request body.", "pricing": "paid", "pricingNotes": "14-day trial with no card, and a free developer sandbox on request by form (1,000 contacts, 100 email sends, 5 users, two years), per the 8 October check. No free plan. Plans are priced by contact count. The 8 October prices came from a data file the pricing page loads, which this benchmark no longer reads, and the page wasn't re-read on 4 November 2026 because the terms bar automated access.", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs or on the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 50, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developers.activecampaign.com/reference/overview", "llmsTxt": "https://developers.activecampaign.com/llms.txt", "capabilities": [ "marketing.profiles", "marketing.events", "marketing.segments", "marketing.campaigns", "marketing.journeys", "crm.records", "crm.pipeline", "crm.webhooks", "messaging.sms", "messaging.whatsapp" ], "tags": [ "official", "hosted", "closed-source", "mcp", "api-key", "llms-txt", "openapi", "webhooks", "no-card", "trial", "sandbox", "status-page", "sla", "sms", "whatsapp" ], "lastRelease": "2026-09-02", "graded": true, "anchor": { "graded": true, "score": 43.9, "grade": "E", "agentReady": false, "rank": 1240, "ranked": true, "rankOf": 1510, "categoryRank": 12, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 52, "maintenance": 5, "payments": 20, "reliability": 52, "schema": 68, "security": 33, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-04" }, "negative": 0, "verdict": "The v3 REST API covers contacts, segments, campaign scheduling and bulk import, with OpenAPI 3.1 definitions inside public Markdown reference pages and documented Retry-After on 429s. Each user has one unscoped API key, the limit is 5 requests a second, no changelog was found, and the official PHP and Node.js clients date from 2017 and 2018.", "bestFor": "Small and mid-sized teams already on ActiveCampaign that want an agent to maintain contacts, segments and campaign drafts and enrol contacts in automations.", "strengths": [ "Every reference page is served as Markdown with an OpenAPI 3.1 definition for its operation, indexed by llms.txt", "429 responses carry Retry-After, RateLimit-Limit and RateLimit-Remaining headers per the rate limit page", "Contact upsert by email and bulk import of 250 contacts a request make contact writes safe to repeat", "Official remote MCP server with 50 listed tools and no delete tool, included on all four plans per the pricing page", "A 99.5 per cent availability SLA is published for enterprise subscriptions, and the sub-processor list of 25 September 2026 names locations" ], "weaknesses": [ "No readable incident history. The status page sits on ActiveCampaign's own domain, whose terms bar robots, and its earlier reading came from a data feed", "One API key per user with no scopes or read-only keys in the reviewed documentation", "The limit is 5 requests a second per account on every plan", "No public API changelog or deprecation policy was found, and developers.activecampaign.com/changelog returns 404", "The official PHP and Node.js clients wrap the v1 API and last changed in December 2017 and March 2018" ], "agentNotes": [ "Take the base URL from Settings, Developer in the account. Do not build it from the account name, because non-US accounts may not sit on api-us1.com", "Use POST /contact/sync to upsert by email, and POST /import/bulk_import for up to 250 contacts, then read each row's outcome from GET /import/info", "Page large contact sets with `orders[id]=ASC` and `id_greater`, not `offset`. Unsupported filter and order keys are silently ignored", "Check `succeeded` in the body after scheduling, pausing or stopping a campaign. Business-rule failures return 200 with `succeeded` set to 0", "Stay under 5 requests a second per account and wait for the Retry-After value on a 429" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 43.9 } ], "editorialScores": { "ergonomics": 52, "maintenance": 5, "payments": 20, "reliability": 52, "schema": 68, "security": 33, "transparency": 55 }, "provenanceScore": 64, "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 -H \"Api-Token: $ACTIVECAMPAIGN_API_TOKEN\" https://\u003caccount\u003e.api-us1.com/api/3/users/me" }, "letme": { "capability": "https://letme.dev/marketing.profiles", "tool": "https://letme.dev/activecampaign" }, "area": "communication", "provenance": { "legalEntity": "ActiveCampaign, LLC", "domain": "activecampaign.com", "domainRegistered": "2003-01-10", "endpointOnVendorDomain": false, "terms": "https://www.activecampaign.com/legal/terms-of-service", "privacy": "https://www.activecampaign.com/legal/privacy-policy", "statusPage": "https://status.activecampaign.com", "changelog": "", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "The terms of service (last updated 19 October 2026) name ActiveCampaign, LLC and cover its websites, applications and other services. Section 8 excludes data mining, robots and similar data-gathering methods from the licence.", "The API answers at https://\u003caccount\u003e.api-us1.com/api/3 and event tracking at https://trackcmp.net/event, neither on activecampaign.com. The docs name both hosts (per the 8 October check).", "www.activecampaign.com/.well-known/security.txt and /security.txt returned 404 on 8 October 2026, not re-read.", "developers.activecampaign.com/changelog returned 404 on 8 October 2026 and no other API changelog was found.", "The registration date is carried from the 8 October check, which took it from RDAP, a data service this run doesn't use; it has no first-hand source today.", "robots.txt sets a Crawl-delay of 1 and Content-Signal ai-train=yes, search=yes, ai-input=yes." ], "score": 64 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/activecampaign.json", "live": { "slug": "activecampaign", "vendorStatus": { "page": "https://status.activecampaign.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T22:56:23.560480568Z" }, "securityTxt": { "url": "https://activecampaign.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:38.558209584Z" }, "llmsTxt": { "url": "https://developers.activecampaign.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:04.74227875Z" }, "domain": { "domain": "activecampaign.com", "registered": "2003-01-10", "source": "https://rdap.verisign.com/com/v1/domain/activecampaign.com", "checkedAt": "2026-11-01T14:25:42.85662222Z" }, "pages": [ { "url": "https://www.activecampaign.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-04T08:36:32.186298524Z", "changedAt": "2026-11-04T08:36:32.186298524Z", "fingerprint": "e568c5258ccf" }, { "url": "https://www.activecampaign.com/legal/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:24:09.993770715Z", "changedAt": "2026-11-04T08:36:27.042116758Z", "fingerprint": "79f5bf1d075d" }, { "url": "https://www.activecampaign.com/legal/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:24:12.401839002Z", "changedAt": "2026-11-04T08:36:29.878885766Z", "fingerprint": "82c150302ae7" } ], "updatedAt": "2026-11-07T22:56:23.560480568Z" } }, "answer": "Sequenzy scores 63.7 (B) on agent readiness against ActiveCampaign's 43.9 (E), and leads in 6 of 7 scored categories. ActiveCampaign leads on reliability.", "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-07T22:56:20.58112772Z", "lastOk": true, "lastStatus": 401, "lastMs": 3440, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 432, "p95ms24h": 1072, "samples24h": 244, "samples30d": 246, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 233, "ok": 233 } ] }, "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-07T22:56:20.58112772Z" } }, "edges": [ { "by": 73, "category": "maintenance", "leads": "sequenzy", "name": "Maintenance \u0026 community", "reasons": { "a": "There is no changelog. On 8 October the `updatedAt` stamps on 46 of the 185 reference pages fell on 12, 13, 17 and 31 August and 2 September 2026 (per the 8 October check, not re-read on 4 November). The 8 October check recorded them as page revisions, not changelog entries, and no API change was recorded on those pages. Page dates that record no change don't set recency (as wrike, coinbase-mcp and agentweb), and the clients are years old, so no dated API change is readable (0). Page stamps aren't releases, so the 90-day line is 0. No public changelog. A community site and a developer relations email address are published, and we did not see reply times (5). The official PHP and Node.js clients are v1 wrappers last changed in December 2017 and March 2018 (0). No current package to assess (0). 0 + 0 + 5 + 0 + 0 = 5.", "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": 5, "b": 78 } }, { "by": 34, "category": "security", "leads": "sequenzy", "name": "Security \u0026 auth", "reasons": { "a": "One API key per user in an `Api-Token` header, with no scopes. The MCP server is authorised by signing in and approving, with no scopes documented. Key rotation was not found in the reviewed documentation (15 of 30). No read-only key or mode. The listed MCP tools include no delete tool and none that schedules a campaign, though `add_contact_to_automation` can start messages, and the definitions name a permission resource for each operation (8 of 20). The API returns contact data, notes and message content written by outsiders, and no prompt-injection guidance was found (0 of 15). No audit log or per-call visibility was found in the developer docs. The help centre refused our reader, so this is unchecked (0 of 15). The security page states SOC 2, HIPAA and GDPR compliance, a red team and a trust centre with the SOC 2 report. No security.txt, bug bounty or disclosure policy was found (10 of 20). All per the 8 October check, not re-read on 4 November. robots.txt disallows `/security/bounty`, so whether a bounty page exists wasn't read.", "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": 33, "b": 67 } }, { "by": 27, "category": "schema", "leads": "sequenzy", "name": "Schema \u0026 documentation", "reasons": { "a": "Each reference page is public Markdown with an OpenAPI 3.1 definition for its operation. No single downloadable specification was found (20 of 25). llms.txt and Markdown pages (10). Pages revised in August 2026, such as contact upsert and contact search, say when to use each endpoint and when not to. Older pages are short, and the MCP page gives one line a tool with no input schemas (14 of 20). Query parameters are typed with enums on status and sort order, but the segment body is described as flexible JSON to be checked against the segment builder (10 of 15). Request examples on most pages. The errors page lists five status codes and one 422 body, and 400 responses in the definitions are empty objects (9 of 15). The version is in the path (v3, Segments 2.0.0). No changelog was found, and developers.activecampaign.com/changelog returns 404 (5 of 15). All per the 8 October check, not re-read on 4 November, since the terms bar automated access to the developer site.", "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": 68, "b": 95 } }, { "by": 20, "category": "payments", "leads": "sequenzy", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). The 8 October plan prices were read from a data file the pricing page loads, which this run doesn't use, and the pricing page wasn't re-read on 4 November because the terms bar automated access, so no published price is counted (0). A 14-day trial with no card, and a free developer sandbox on request (per the 8 October check, not re-read on 4 November) (20). A person signs up in a browser and copies the key from account settings (0). 0 + 0 + 20 + 0 = 20.", "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": 20, "b": 40 } }, { "by": 17, "category": "ergonomics", "leads": "sequenzy", "name": "Agent ergonomics", "reasons": { "a": "List endpoints take `limit` up to 100 and contacts take `meta=only` for a count, but there is no field selection. The MCP server lists 50 tools with no documented toolsets (12 of 25). `limit`, `offset`, `orders`, `filters` and `id_greater` on contacts, less 4 because unsupported filter and order keys are silently ignored (16 of 20). Five documented status codes and a 422 `errors` array of titles without codes. Campaign state changes report failures as 200 with `succeeded` 0 and a localised message (10 of 20). No idempotency keys. Upsert by email and bulk import with per-row status give safe retries for contacts, and no MCP tool annotations are documented (8 of 20). Few required parameters. The official PHP and Node.js clients wrap the v1 API and last changed in 2017 and 2018, so no current official SDK was found (6 of 15). Docs per the 8 October check, not re-read on 4 November; the PHP client's last commit (7 December 2017) was confirmed from a clone.", "b": "The MCP tool reference lists about 306 tools, the over-30 band, and no toolsets, tool search or dynamic loading was found (5 of 25). List endpoints paginate and filter, and contact timelines use cursors (20). Errors carry a code, a human message, a fix and a docs link, with `retryAfterSeconds` when the API sent Retry-After (20). Idempotency keys on sends and event imports; MCP readOnlyHint and destructiveHint annotations weren't found in the published reference (14 of 20). Sensible defaults with a selected workspace; one official SDK (TypeScript) plus a CLI (10 of 15). Total 69." }, "scores": { "a": 52, "b": 69 } }, { "by": 14, "category": "reliability", "leads": "activecampaign", "name": "Reliability", "reasons": { "a": "Graded on the v3 REST API with the hosted lines. ActiveCampaign's terms (updated 19 October 2026) bar robots and data-gathering methods on its websites, so its pages, its own-domain status page included, weren't re-read on 4 November. The 8 October component and incident readings came from the status page's JSON endpoints, which this run doesn't use, and no readable record remains, so the status-page line is 0 and the incident line 5 (unread). 5 requests a second per account (15). 429 with Retry-After and RateLimit headers; no idempotency keys, though upsert by email makes contact writes repeatable (12). SLA of 99.5 per cent for enterprise subscriptions (10). The v3 API is generally available and the MCP pages carry no beta label (10). The last four lines are per the 8 October check, not re-read on 4 November. 0 + 5 + 15 + 12 + 10 + 10 = 52.", "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": 52, "b": 38 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "ActiveCampaign, LLC", "b": "Nic Tech Solutions, LLC", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.sequenzy.com/v1/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP, stdio", "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 ActiveCampaign's terms of service and API licence agreement", "b": "none", "name": "Licence" }, { "a": "50", "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-09-02", "b": "2026-11-06", "name": "Last release" }, { "a": "2025-12-23", "b": "2026-06-30", "name": "Terms last updated" }, { "a": "2026-10-01", "b": "2026-09-16", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "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": "none", "b": "2.4k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Sequenzy scores 63.7 (B) on agent readiness against ActiveCampaign's 43.9 (E), and leads in 6 of 7 scored categories. ActiveCampaign leads on reliability.", "question": "Which is better for AI agents, ActiveCampaign or Sequenzy?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do ActiveCampaign and Sequenzy need an API key?" }, { "answer": "No hosted endpoint is listed for ActiveCampaign. Sequenzy has a hosted endpoint at https://api.sequenzy.com/v1/mcp.", "question": "Can an agent call ActiveCampaign and Sequenzy without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 52 against 38" ], "also": null, "goodFor": "Small and mid-sized teams already on ActiveCampaign that want an agent to maintain contacts, segments and campaign drafts and enrol contacts in automations.", "slug": "activecampaign", "watchFor": "No readable incident history. The status page sits on ActiveCampaign's own domain, whose terms bar robots, and its earlier reading came from a data feed" }, { "aheadOn": [ "Schema \u0026 documentation, 95 against 68", "Agent ergonomics, 69 against 52", "Security \u0026 auth, 67 against 33", "Payments \u0026 pricing, 40 against 20", "Maintenance \u0026 community, 78 against 5", "Transparency \u0026 trust, 67 against 60" ], "also": [ "A hosted endpoint, with nothing to install", "Runs on your own machine" ], "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": { "activecampaign": [ { "causes": [ "correction", "method" ], "date": "2026-11-04", "delta": -6.8, "from": 50.7, "fromGrade": "D", "to": 43.9, "toGrade": "E" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 50.5, "fromGrade": "D", "to": 50.7, "toGrade": "D" } ], "sequenzy": null }, "job": { "capability": "marketing.profiles", "name": "Marketing audiences" }, "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-clevertap.json", "title": "ActiveCampaign vs CleverTap", "url": "https://www.anchorterminal.com/compare/activecampaign-vs-clevertap" }, { "json": "https://www.anchorterminal.com/compare/activecampaign-vs-customer-io.json", "title": "ActiveCampaign vs Customer.io", "url": "https://www.anchorterminal.com/compare/activecampaign-vs-customer-io" }, { "json": "https://www.anchorterminal.com/compare/activecampaign-vs-iterable.json", "title": "ActiveCampaign vs Iterable", "url": "https://www.anchorterminal.com/compare/activecampaign-vs-iterable" }, { "json": "https://www.anchorterminal.com/compare/activecampaign-vs-klaviyo.json", "title": "ActiveCampaign vs Klaviyo API + MCP", "url": "https://www.anchorterminal.com/compare/activecampaign-vs-klaviyo" }, { "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/activecampaign-vs-nitrosend.json", "title": "ActiveCampaign vs Nitrosend", "url": "https://www.anchorterminal.com/compare/activecampaign-vs-nitrosend" }, { "json": "https://www.anchorterminal.com/compare/activecampaign-vs-omnisend.json", "title": "ActiveCampaign vs Omnisend", "url": "https://www.anchorterminal.com/compare/activecampaign-vs-omnisend" }, { "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-sequenzy.json", "title": "CleverTap vs Sequenzy", "url": "https://www.anchorterminal.com/compare/clevertap-vs-sequenzy" }, { "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-sequenzy.json", "title": "Iterable vs Sequenzy", "url": "https://www.anchorterminal.com/compare/iterable-vs-sequenzy" }, { "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-sequenzy.json", "title": "Mailchimp Marketing API vs Sequenzy", "url": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-sequenzy" }, { "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/activecampaign-vs-dreamlit.json", "title": "ActiveCampaign vs Dreamlit", "url": "https://www.anchorterminal.com/compare/activecampaign-vs-dreamlit" }, { "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": [ { "activecampaign": 52, "by": 14, "edge": "activecampaign", "key": "reliability", "name": "Reliability", "sequenzy": 38, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "activecampaign": 68, "by": 27, "edge": "sequenzy", "key": "schema", "name": "Schema \u0026 documentation", "sequenzy": 95, "weight": 13 }, { "activecampaign": 52, "by": 17, "edge": "sequenzy", "key": "ergonomics", "name": "Agent ergonomics", "sequenzy": 69, "weight": 13 }, { "activecampaign": 33, "by": 34, "edge": "sequenzy", "key": "security", "name": "Security \u0026 auth", "sequenzy": 67, "weight": 14 }, { "activecampaign": 20, "by": 20, "edge": "sequenzy", "key": "payments", "name": "Payments \u0026 pricing", "sequenzy": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "activecampaign": 5, "by": 73, "edge": "sequenzy", "key": "maintenance", "name": "Maintenance \u0026 community", "sequenzy": 78, "weight": 7 }, { "activecampaign": 60, "by": 7, "edge": "sequenzy", "key": "transparency", "name": "Transparency \u0026 trust", "sequenzy": 67, "weight": 7 } ], "summary": "Sequenzy scores 63.7 (B) on agent readiness against ActiveCampaign's 43.9 (E), and leads in 6 of 7 scored categories. ActiveCampaign leads on reliability. Both do marketing audiences.", "tasks": null, "tutorials": [], "verdicts": { "activecampaign": "The v3 REST API covers contacts, segments, campaign scheduling and bulk import, with OpenAPI 3.1 definitions inside public Markdown reference pages and documented Retry-After on 429s. Each user has one unscoped API key, the limit is 5 requests a second, no changelog was found, and the official PHP and Node.js clients date from 2017 and 2018.", "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/activecampaign-vs-sequenzy", "json": "https://www.anchorterminal.com/compare/activecampaign-vs-sequenzy.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/activecampaign-vs-sequenzy.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/activecampaign-vs-sequenzy.min.md" }, "markdown": "Sequenzy scores 63.7 (B) on agent readiness against ActiveCampaign's 43.9 (E), and leads in 6 of 7 scored categories. ActiveCampaign leads on reliability. Both do marketing audiences.\n\n- ActiveCampaign: grade E, 43.9/100, rank #1240 of 1510. Markdown https://www.anchorterminal.com/tools/activecampaign.md · JSON https://www.anchorterminal.com/api/v1/tools/activecampaign.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### ActiveCampaign (E)\n\nGood for: Small and mid-sized teams already on ActiveCampaign that want an agent to maintain contacts, segments and campaign drafts and enrol contacts in automations.\n\nAhead on:\n- Reliability, 52 against 38\n\nWatch for: No readable incident history. The status page sits on ActiveCampaign's own domain, whose terms bar robots, and its earlier reading came from a data feed\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 68\n- Agent ergonomics, 69 against 52\n- Security \u0026 auth, 67 against 33\n- Payments \u0026 pricing, 40 against 20\n- Maintenance \u0026 community, 78 against 5\n- Transparency \u0026 trust, 67 against 60\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n\nWatch for: About 306 MCP tools, with no toolsets or dynamic loading found\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Sequenzy +73\n\n- ActiveCampaign (5): There is no changelog. On 8 October the `updatedAt` stamps on 46 of the 185 reference pages fell on 12, 13, 17 and 31 August and 2 September 2026 (per the 8 October check, not re-read on 4 November). The 8 October check recorded them as page revisions, not changelog entries, and no API change was recorded on those pages. Page dates that record no change don't set recency (as wrike, coinbase-mcp and agentweb), and the clients are years old, so no dated API change is readable (0). Page stamps aren't releases, so the 90-day line is 0. No public changelog. A community site and a developer relations email address are published, and we did not see reply times (5). The official PHP and Node.js clients are v1 wrappers last changed in December 2017 and March 2018 (0). No current package to assess (0). 0 + 0 + 5 + 0 + 0 = 5.\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### Security \u0026 auth: Sequenzy +34\n\n- ActiveCampaign (33): One API key per user in an `Api-Token` header, with no scopes. The MCP server is authorised by signing in and approving, with no scopes documented. Key rotation was not found in the reviewed documentation (15 of 30). No read-only key or mode. The listed MCP tools include no delete tool and none that schedules a campaign, though `add_contact_to_automation` can start messages, and the definitions name a permission resource for each operation (8 of 20). The API returns contact data, notes and message content written by outsiders, and no prompt-injection guidance was found (0 of 15). No audit log or per-call visibility was found in the developer docs. The help centre refused our reader, so this is unchecked (0 of 15). The security page states SOC 2, HIPAA and GDPR compliance, a red team and a trust centre with the SOC 2 report. No security.txt, bug bounty or disclosure policy was found (10 of 20). All per the 8 October check, not re-read on 4 November. robots.txt disallows `/security/bounty`, so whether a bounty page exists wasn't read.\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 +27\n\n- ActiveCampaign (68): Each reference page is public Markdown with an OpenAPI 3.1 definition for its operation. No single downloadable specification was found (20 of 25). llms.txt and Markdown pages (10). Pages revised in August 2026, such as contact upsert and contact search, say when to use each endpoint and when not to. Older pages are short, and the MCP page gives one line a tool with no input schemas (14 of 20). Query parameters are typed with enums on status and sort order, but the segment body is described as flexible JSON to be checked against the segment builder (10 of 15). Request examples on most pages. The errors page lists five status codes and one 422 body, and 400 responses in the definitions are empty objects (9 of 15). The version is in the path (v3, Segments 2.0.0). No changelog was found, and developers.activecampaign.com/changelog returns 404 (5 of 15). All per the 8 October check, not re-read on 4 November, since the terms bar automated access to the developer site.\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 +20\n\n- ActiveCampaign (20): No x402, MPP or L402 (0). The 8 October plan prices were read from a data file the pricing page loads, which this run doesn't use, and the pricing page wasn't re-read on 4 November because the terms bar automated access, so no published price is counted (0). A 14-day trial with no card, and a free developer sandbox on request (per the 8 October check, not re-read on 4 November) (20). A person signs up in a browser and copies the key from account settings (0). 0 + 0 + 20 + 0 = 20.\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### Agent ergonomics: Sequenzy +17\n\n- ActiveCampaign (52): List endpoints take `limit` up to 100 and contacts take `meta=only` for a count, but there is no field selection. The MCP server lists 50 tools with no documented toolsets (12 of 25). `limit`, `offset`, `orders`, `filters` and `id_greater` on contacts, less 4 because unsupported filter and order keys are silently ignored (16 of 20). Five documented status codes and a 422 `errors` array of titles without codes. Campaign state changes report failures as 200 with `succeeded` 0 and a localised message (10 of 20). No idempotency keys. Upsert by email and bulk import with per-row status give safe retries for contacts, and no MCP tool annotations are documented (8 of 20). Few required parameters. The official PHP and Node.js clients wrap the v1 API and last changed in 2017 and 2018, so no current official SDK was found (6 of 15). Docs per the 8 October check, not re-read on 4 November; the PHP client's last commit (7 December 2017) was confirmed from a clone.\n- Sequenzy (69): The MCP tool reference lists about 306 tools, the over-30 band, and no toolsets, tool search or dynamic loading was found (5 of 25). List endpoints paginate and filter, and contact timelines use cursors (20). Errors carry a code, a human message, a fix and a docs link, with `retryAfterSeconds` when the API sent Retry-After (20). Idempotency keys on sends and event imports; MCP readOnlyHint and destructiveHint annotations weren't found in the published reference (14 of 20). Sensible defaults with a selected workspace; one official SDK (TypeScript) plus a CLI (10 of 15). Total 69.\n\n### Reliability: ActiveCampaign +14\n\n- ActiveCampaign (52): Graded on the v3 REST API with the hosted lines. ActiveCampaign's terms (updated 19 October 2026) bar robots and data-gathering methods on its websites, so its pages, its own-domain status page included, weren't re-read on 4 November. The 8 October component and incident readings came from the status page's JSON endpoints, which this run doesn't use, and no readable record remains, so the status-page line is 0 and the incident line 5 (unread). 5 requests a second per account (15). 429 with Retry-After and RateLimit headers; no idempotency keys, though upsert by email makes contact writes repeatable (12). SLA of 99.5 per cent for enterprise subscriptions (10). The v3 API is generally available and the MCP pages carry no beta label (10). The last four lines are per the 8 October check, not re-read on 4 November. 0 + 5 + 15 + 12 + 10 + 10 = 52.\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## Score by category\n\n| Category | Weight | ActiveCampaign | Sequenzy | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 52 | 38 | ActiveCampaign +14 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 68 | 95 | Sequenzy +27 |\n| Agent ergonomics | 13% (16.2 this run) | 52 | 69 | Sequenzy +17 |\n| Security \u0026 auth | 14% (17.5 this run) | 33 | 67 | Sequenzy +34 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 40 | Sequenzy +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 5 | 78 | Sequenzy +73 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 60 | 67 | Sequenzy +7 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **43.9 · E** | **63.7 · B** | |\n\n## Facts side by side\n\n| Fact | ActiveCampaign | Sequenzy |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | ActiveCampaign, LLC | Nic Tech Solutions, LLC |\n| Hosted endpoint | no (local only) | `https://api.sequenzy.com/v1/mcp` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under ActiveCampaign's terms of service and API licence agreement | none |\n| Tools exposed | 50 | 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-09-02 | 2026-11-06 |\n| Terms last updated | 2025-12-23 | 2026-06-30 |\n| Privacy policy last updated | 2026-10-01 | 2026-09-16 |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | yes | 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 | none | 2.4k npm/wk |\n\n## How the scores have moved\n\n### ActiveCampaign\n\n- -6.8 on 4 November 2026 (D to E): correction, checklist\n- +0.2 on 27 October 2026: checklist\n\n### Sequenzy\n\nNo score change since it was listed.\n\n## Verdicts\n\n**ActiveCampaign.** The v3 REST API covers contacts, segments, campaign scheduling and bulk import, with OpenAPI 3.1 definitions inside public Markdown reference pages and documented Retry-After on 429s. Each user has one unscoped API key, the limit is 5 requests a second, no changelog was found, and the official PHP and Node.js clients date from 2017 and 2018.\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### ActiveCampaign\n\n1. Take the base URL from Settings, Developer in the account. Do not build it from the account name, because non-US accounts may not sit on api-us1.com\n2. Use POST /contact/sync to upsert by email, and POST /import/bulk_import for up to 250 contacts, then read each row's outcome from GET /import/info\n3. Page large contact sets with `orders[id]=ASC` and `id_greater`, not `offset`. Unsupported filter and order keys are silently ignored\n4. Check `succeeded` in the body after scheduling, pausing or stopping a campaign. Business-rule failures return 200 with `succeeded` set to 0\n5. Stay under 5 requests a second per account and wait for the Retry-After value on a 429\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, ActiveCampaign or Sequenzy?\n\nSequenzy scores 63.7 (B) on agent readiness against ActiveCampaign's 43.9 (E), and leads in 6 of 7 scored categories. ActiveCampaign leads on reliability.\n\n### Do ActiveCampaign and Sequenzy need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call ActiveCampaign and Sequenzy without installing anything?\n\nNo hosted endpoint is listed for ActiveCampaign. Sequenzy has a hosted endpoint at https://api.sequenzy.com/v1/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/activecampaign-vs-sequenzy.json, and with the fewest tokens: https://www.anchorterminal.com/compare/activecampaign-vs-sequenzy.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"activecampaign\", \"b\": \"sequenzy\"}`. From a terminal: `anchor compare activecampaign sequenzy`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/activecampaign.json and https://www.anchorterminal.com/api/v1/tools/sequenzy.json\n\n## Other comparisons with ActiveCampaign or Sequenzy\n\n- [ActiveCampaign vs Braze](https://www.anchorterminal.com/compare/activecampaign-vs-braze.md)\n- [ActiveCampaign vs CleverTap](https://www.anchorterminal.com/compare/activecampaign-vs-clevertap.md)\n- [ActiveCampaign vs Customer.io](https://www.anchorterminal.com/compare/activecampaign-vs-customer-io.md)\n- [ActiveCampaign vs Iterable](https://www.anchorterminal.com/compare/activecampaign-vs-iterable.md)\n- [ActiveCampaign vs Klaviyo API + MCP](https://www.anchorterminal.com/compare/activecampaign-vs-klaviyo.md)\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- [ActiveCampaign vs Nitrosend](https://www.anchorterminal.com/compare/activecampaign-vs-nitrosend.md)\n- [ActiveCampaign vs Omnisend](https://www.anchorterminal.com/compare/activecampaign-vs-omnisend.md)\n- [Braze vs Sequenzy](https://www.anchorterminal.com/compare/braze-vs-sequenzy.md)\n- [CleverTap vs Sequenzy](https://www.anchorterminal.com/compare/clevertap-vs-sequenzy.md)\n- [Customer.io vs Sequenzy](https://www.anchorterminal.com/compare/customer-io-vs-sequenzy.md)\n- [Iterable vs Sequenzy](https://www.anchorterminal.com/compare/iterable-vs-sequenzy.md)\n- [Klaviyo API + MCP vs Sequenzy](https://www.anchorterminal.com/compare/klaviyo-vs-sequenzy.md)\n- [Mailchimp Marketing API vs Sequenzy](https://www.anchorterminal.com/compare/mailchimp-marketing-vs-sequenzy.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- [ActiveCampaign vs Dreamlit](https://www.anchorterminal.com/compare/activecampaign-vs-dreamlit.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": "ActiveCampaign vs Sequenzy", "url": "" } ], "description": "Sequenzy scores 63.7 (B) to ActiveCampaign's 43.9 (E) for marketing audiences. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "ActiveCampaign E 43.9", "Sequenzy B 63.7", "scores" ], "h1": "ActiveCampaign vs Sequenzy", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/activecampaign-vs-sequenzy", "published": "2026-10-01", "section": "tools", "title": "ActiveCampaign vs Sequenzy for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/activecampaign-vs-sequenzy" }, "tokens": { "markdown": 4850, "slim": 3080 }, "version": 1 }