{ "data": { "a": { "slug": "moengage", "name": "MoEngage", "vendor": "MoEngage, Inc.", "vendorUrl": "https://www.moengage.com", "kind": "http-api", "category": "lifecycle-marketing", "summary": "MoEngage is a hosted customer engagement platform that stores user profiles and events, builds segments and sends campaigns and flows by push, email, SMS and WhatsApp. Agents reach it through REST APIs and a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/moengage", "markdownUrl": "https://www.anchorterminal.com/tools/moengage.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/moengage.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/moengage.json", "dns": "moengage.grade.anchorterminal.com", "license": "Proprietary service under MoEngage's Terms of Use and a customer agreement", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://mcp.moengage.com", "packages": [], "auth": "mixed", "authNotes": "Access needs a MoEngage customer workspace, which is sold through sales. A dashboard user creates API keys under Settings, Account, APIs. The default is HTTP Basic with the Workspace ID as username and the API key as password, with separate keys for Data, Push, Inform, Campaigns and Personalise. An API key dashboard, in early access and enabled on request, adds named keys scoped to chosen API groups, OAuth 2.0 client credentials (access tokens of 5 to 60 minutes, refresh tokens of 30 days, issued at `https://oauth2-{dc}.moengage.com`) and AWS STS role ARNs. Segmentation and Inform accept Basic only. The MCP server uses OAuth with the user's own MoEngage login and role, a second factor, and a 30-day session with a 7-day idle timeout. No app review or partner approval was found.", "pricing": "paid", "pricingNotes": "No public prices. https://www.moengage.com/plans-and-pricing/ lists Growth and Enterprise plans, counted in monthly tracked users, with a sales contact and a one-year minimum commitment. No free tier, trial or self-serve signup was found. Each workspace has Live and Test environments and Inform has a sandbox host, but both sit inside a customer account, so an agent can't start without a contract. API and MCP calls aren't priced per call in any page read (checked 2026-10-09).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API documentation, the OpenAPI files, the pricing page or the legal pages (checked 2026-10-09).", "endpoints": [] }, "toolCount": 52, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://www.moengage.com/docs/api/introduction", "llmsTxt": "https://www.moengage.com/docs/llms.txt", "openapi": "https://www.moengage.com/docs/api/data/data.yaml", "capabilities": [ "marketing.profiles", "marketing.events", "marketing.segments", "marketing.campaigns", "marketing.journeys", "email.templates", "notify.push" ], "tags": [ "official", "hosted", "mcp", "oauth", "api-key", "openapi", "llms-txt", "closed-source", "sales-led", "enterprise", "eu-region", "status-page", "soc2", "sla" ], "lastRelease": "2026-10-14", "graded": true, "anchor": { "graded": true, "score": 65.7, "grade": "B", "agentReady": false, "rank": 405, "ranked": true, "rankOf": 1510, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 68, "maintenance": 75, "payments": 0, "reliability": 76, "schema": 87, "security": 69, "transparency": 76 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": 0, "verdict": "MoEngage publishes 37 OpenAPI files, a per-endpoint rate limit table, Markdown docs and a hosted MCP server that builds drafts and leaves publishing to a person. No price, trial or self-serve signup is published, and on 27 October 2026 the Push API was down across its data centres for about 11 hours.", "bestFor": "A team already on MoEngage that wants an agent to update profiles, track events, build filter segments, draft Push and Email campaigns and read campaign, flow and analytics results.", "strengths": [ "37 public OpenAPI files linked from the docs index; the 36 read on 9 October held 140 operations, each with a summary and description", "A rate limit table with numbers for every endpoint group, plus `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset` response headers", "The hosted MCP server at mcp.moengage.com uses OAuth tied to the user's role, masks PII attributes and cannot publish a campaign", "API keys can be scoped to chosen API groups, use OAuth 2.0 tokens of 5 to 60 minutes or AWS STS roles, and be limited by IP address", "A published SLA of 99.9 per cent monthly availability, a public DPA and a sub-processor list with locations dated 1 September 2026" ], "weaknesses": [ "No public price, free tier or trial. The pricing page lists Growth and Enterprise plans with a one-year minimum and a sales contact only", "On 27 October 2026 the Push API was down across data centres for about 11 hours, and on 17 August the DC-03 Inform API returned HTTP 200 for 16 hours without sending some messages", "Scoped keys, OAuth 2.0 and AWS STS keys sit in an API key dashboard that is in early access and enabled on request", "Segmentation and Inform accept Basic authentication only, and new Push API keys can't be created", "No API deprecation policy was found, and no official server-side API client library was found in the documentation" ], "agentNotes": [ "Take the data centre number from the dashboard URL and call `https://api-{dc}.moengage.com`. Data can't be moved between data centres", "Send an `Idempotency-Key` header (UUID v4) on V5 campaign writes and test sends, and a `transaction_id` on Inform alerts, which deduplicates for 5 minutes", "Use internal event and attribute names in segment filters, and run `deep_validate_segment_filters` first. A wrong event name is accepted and the count later fails with no reason", "Use `in` with a list for text equality in segment filters. `equals` returns a 400 that names no field", "Reuse an OAuth access token until it nears expiry. The token endpoint allows 5 requests a minute and 30 per 10 minutes for each key" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 65.7 } ], "editorialScores": { "ergonomics": 68, "maintenance": 75, "payments": 0, "reliability": 76, "schema": 87, "security": 69, "transparency": 60 }, "provenanceScore": 91, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-11-02", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl --request POST \\\n --url https://api-{dc}.moengage.com/v1/customer/YOUR_WORKSPACE_ID \\\n --header 'Authorization: Bearer YOUR_ACCESS_TOKEN' \\\n --header 'Content-Type: application/json' \\\n --data '{ \"type\": \"customer\", \"customer_id\": \"user_12345\" }'", "config": { "mcpServers": { "moengage": { "url": "https://mcp.moengage.com" } } } }, "letme": { "capability": "https://letme.dev/marketing.profiles", "tool": "https://letme.dev/moengage" }, "area": "communication", "provenance": { "legalEntity": "MoEngage, Inc.", "domain": "moengage.com", "domainRegistered": "2014-04-19", "endpointOnVendorDomain": true, "terms": "https://www.moengage.com/terms-of-use/", "privacy": "https://www.moengage.com/privacy-policy/", "statusPage": "https://status.moengage.com", "changelog": "https://www.moengage.com/docs/release-notes/product/2026/september-2026", "securityTxt": "none", "checked": "2026-11-02", "notes": [ "The Terms of Use name MoEngage, Inc., a Delaware corporation, and say they govern the website and related software and services. They carry no date. The DPA and sub-processor list name MoEngage Global Inc.", "The acceptable use policy (last updated 14 May 2026) refers to a Master Service Agreement between MoEngage and its customers. That agreement isn't published.", "The privacy policy was last updated on 26 August 2026 and covers MoEngage as processor for its customers' end users.", "The API answers at api-{dc}.moengage.com and the MCP server at mcp.moengage.com, both on the vendor's domain.", "https://www.moengage.com/.well-known/security.txt returns 404 (re-read 2 November 2026). Reports go to the address in the responsible disclosure policy.", "Release notes are one page a month under /docs/release-notes/product/, with separate dated changelogs for each SDK.", "RDAP for moengage.com gives a registration date of 2014-04-19." ], "score": 91 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/moengage.json", "live": { "slug": "moengage", "probe": { "target": "https://mcp.moengage.com", "method": "get", "lastAt": "2026-11-07T19:22:20.569598976Z", "lastOk": true, "lastStatus": 401, "lastMs": 81, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.99, "p50ms24h": 35, "p95ms24h": 123, "samples24h": 238, "samples30d": 7215, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 247, "ok": 246 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.moengage.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:22:42.897791739Z" }, "securityTxt": { "url": "https://moengage.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:17.164091584Z" }, "llmsTxt": { "url": "https://www.moengage.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:13.621481424Z" }, "domain": { "domain": "moengage.com", "registered": "2014-04-19", "source": "https://rdap.verisign.com/com/v1/domain/moengage.com", "checkedAt": "2026-11-01T14:21:21.091325535Z" }, "pages": [ { "url": "https://www.moengage.com/docs/release-notes/product/2026/september-2026", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:31:44.906126765Z", "changedAt": "2026-11-06T13:52:21.289294153Z", "fingerprint": "e0a462c3a13f" }, { "url": "https://www.moengage.com/plans-and-pricing/", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:31:47.25902456Z", "changedAt": "2026-10-31T06:29:58.721060509Z", "fingerprint": "e799bed9be85" }, { "url": "https://www.moengage.com/privacy-policy/", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:31:50.470962503Z", "changedAt": "2026-11-04T08:42:47.835112355Z", "fingerprint": "4de27c3abe59" }, { "url": "https://www.moengage.com/terms-of-use/", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:31:51.428269323Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3a3cf18334cc" } ], "mcpTools": { "url": "https://mcp.moengage.com", "checkedAt": "2026-11-07T01:46:16.238795444Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:16.238795444Z" }, "updatedAt": "2026-11-07T19:22:20.569598976Z" } }, "answer": "MoEngage scores 65.7 (B) on agent readiness against Sequenzy's 63.7 (B), and leads in 3 of 7 scored categories. Sequenzy leads on schema \u0026 documentation and payments \u0026 pricing.", "b": { "slug": "sequenzy", "name": "Sequenzy", "vendor": "Nic Tech Solutions, LLC", "vendorUrl": "https://www.sequenzy.com", "kind": "http-api", "category": "lifecycle-marketing", "summary": "Sequenzy is an email marketing and lifecycle automation platform for SaaS and ecommerce teams, with sequences, campaigns, transactional email, an agent inbox, push and SMS. It has a REST API, an MCP server, a CLI and a TypeScript SDK.", "url": "https://www.anchorterminal.com/tools/sequenzy", "markdownUrl": "https://www.anchorterminal.com/tools/sequenzy.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sequenzy.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sequenzy.json", "dns": "sequenzy.grade.anchorterminal.com", "repo": "https://github.com/Sequenzy/mcp", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.sequenzy.com/v1/mcp", "packages": [ { "registry": "npm", "name": "sequenzy" }, { "registry": "npm", "name": "@sequenzy/mcp" }, { "registry": "npm", "name": "@sequenzy/cli" } ], "auth": "mixed", "authNotes": "Workspace API keys (`seq_live_`) and account keys (`seq_user_`) sent as Bearer tokens, each with permission scopes such as `transactional:send`, `subscribers:tag` and explicit `*:delete`, and presets including read-only and drafts-only. Account keys keep the user's workspace role. Agents can also register through the `service_auth` OAuth flow, where the user confirms a code in a Sequenzy browser page.", "pricing": "freemium", "pricingNotes": "Free plan of 2,500 emails a month with unlimited contacts and API, MCP and CLI access, no card, with a Sequenzy footer. Paid plans by monthly email volume, $19 for 15,000, $29 for 30,000, $49 for 60,000, $99 for 120,000, up to $2,999 for 5 million. SMS add-on $16 a month with 1,000 credits.", "priceSummary": "$19 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms.txt, auth.md, the pricing page or the OpenAPI spec (checked 2026-11-06).", "endpoints": [] }, "toolCount": 306, "popularity": { "githubStars": null, "npmWeekly": 2363, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.sequenzy.com", "llmsTxt": "https://www.sequenzy.com/llms.txt", "openapi": "https://docs.sequenzy.com/openapi.yaml", "registryName": "io.github.polnikale/sequenzy-mcp", "capabilities": [ "marketing.profiles", "marketing.events", "marketing.segments", "marketing.campaigns", "marketing.journeys", "email.send", "email.templates", "email.inbound" ], "tags": [ "hosted", "closed-source", "mcp", "remote-mcp", "mcp-registry", "oauth", "api-key", "openapi", "llms-txt", "webhooks", "idempotency", "smtp", "sms", "no-card", "free-tier", "typescript", "cli", "no-status-page" ], "lastRelease": "2026-11-06", "graded": true, "anchor": { "graded": true, "score": 63.7, "grade": "B", "agentReady": false, "rank": 506, "ranked": true, "rankOf": 1510, "categoryRank": 6, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 78, "payments": 40, "reliability": 38, "schema": 95, "security": 67, "transparency": 67 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Scoped keys with read-only and drafts-only presets, a 475-operation OpenAPI spec, idempotent sends and near-daily dated releases make it workable for an agent. The MCP server lists about 306 tools, which is heavy on context, and there is no status page, SLA or published request limit table.", "bestFor": "SaaS and ecommerce lifecycle email run from code or an agent, with billing-event triggers from Stripe, Paddle and others.", "strengths": [ "Every key and MCP grant carries permission scopes, with read-only and drafts-only presets and explicit delete permissions", "OpenAPI 3.1 with 475 described operations, llms.txt and Markdown twins of the docs", "Tool and API errors return a code, a fix and a docs link, and sends take an `Idempotency-Key`", "Free plan of 2,500 emails a month with no card and full API, MCP and CLI access", "Dated changelog entries almost every day, 353 since December 2025" ], "weaknesses": [ "About 306 MCP tools, with no toolsets or dynamic loading found", "No status page, incident history or SLA found", "Request rate limits appear only as response headers and a few per-route notes, with no published table", "The registry entry io.github.polnikale/sequenzy-mcp is at 0.0.36 while npm is at 0.0.246", "The terms' governing-law clause doesn't name a jurisdiction" ], "agentNotes": [ "Connect with a drafts-only or read-only key unless the task must send, and widen permissions only when an error names the missing scope", "Send an `Idempotency-Key` with each transactional send and reuse it unchanged after an uncertain result", "Read `structuredContent.error.code` and `howToFix` on a failed tool call before retrying; the client doesn't retry", "Call `get_account` and `select_company` first when the key can reach more than one workspace", "On 429 wait for Retry-After and read the RateLimit-Remaining header" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.7 } ], "editorialScores": { "ergonomics": 69, "maintenance": 78, "payments": 40, "reliability": 38, "schema": 95, "security": 67, "transparency": 64 }, "provenanceScore": 70, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install sequenzy", "claudeCode": "claude mcp add --scope user --env=SEQUENZY_API_KEY=seq_user_your_key_here sequenzy -- npx -y @sequenzy/mcp", "config": { "mcpServers": { "sequenzy": { "args": [ "-y", "@sequenzy/mcp" ], "command": "npx", "env": { "SEQUENZY_API_KEY": "seq_user_your_key_here" } } } } }, "letme": { "capability": "https://letme.dev/marketing.profiles", "tool": "https://letme.dev/sequenzy" }, "alsoIn": [ "email" ], "area": "communication", "unitPrices": [ { "item": "15,000 emails", "unit": "month", "usd": 19 }, { "item": "60,000 emails", "unit": "month", "usd": 49 }, { "item": "120,000 emails", "unit": "month", "usd": 99 }, { "item": "300,000 emails", "unit": "month", "usd": 199 }, { "item": "SMS add-on", "unit": "month", "usd": 16, "note": "1,000 credits a month" } ], "provenance": { "legalEntity": "Nic Tech Solutions, LLC", "domain": "sequenzy.com", "domainRegistered": "2025-11-25", "endpointOnVendorDomain": true, "terms": "https://www.sequenzy.com/terms", "privacy": "https://www.sequenzy.com/privacy", "statusPage": "", "changelog": "https://docs.sequenzy.com/changelog", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The site footer and contact page name Nic Tech Solutions, LLC in Delaware. The terms (30 June 2026) say they're governed by the laws of the jurisdiction in which Sequenzy operates, without naming it.", "Privacy policy last updated 16 September 2026, security page 3 July 2026, and a public DPA with a named sub-processor list.", "www.sequenzy.com/robots.txt disallows /api/, /dashboard/ and app paths only; docs.sequenzy.com disallows /_next/ and /cdn-cgi/. Both carry Content-Signal ai-input=yes.", "RDAP gives sequenzy.com a registration date of 25 November 2025.", "/.well-known/security.txt returns 404; the security page gives security@sequenzy.com for disclosure. No status page found." ], "score": 70 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/sequenzy.json", "live": { "slug": "sequenzy", "probe": { "target": "https://api.sequenzy.com/v1/mcp", "method": "get", "lastAt": "2026-11-07T19:22:32.315745023Z", "lastOk": true, "lastStatus": 401, "lastMs": 513, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 430, "p95ms24h": 963, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "versions": [ { "registry": "mcp-registry", "name": "io.github.polnikale/sequenzy-mcp", "version": "0.0.80", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "@sequenzy/cli", "version": "0.0.202", "seenAt": "2026-11-07T00:04:47.709534287Z" }, { "registry": "npm", "name": "@sequenzy/mcp", "version": "0.0.246", "seenAt": "2026-11-07T00:04:46.382384788Z" }, { "registry": "npm", "name": "sequenzy", "version": "2.1.56", "seenAt": "2026-11-07T00:04:45.470371029Z" } ], "githubStars": 3, "npmWeekly": 2363, "securityTxt": { "url": "https://sequenzy.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:21.983534364Z" }, "llmsTxt": { "url": "https://www.sequenzy.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:54.221757235Z" }, "pages": [ { "url": "https://docs.sequenzy.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:07:55.051332773Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c2d75327efad" }, { "url": "https://www.sequenzy.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:34:21.090752788Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "03a493105931" }, { "url": "https://www.sequenzy.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:34:23.45384067Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "a816dc038eb6" } ], "updatedAt": "2026-11-07T19:22:32.315745023Z" } }, "edges": [ { "by": 40, "category": "payments", "leads": "sequenzy", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). No prices are published. The pricing page lists Growth and Enterprise plans with a sales contact (0). No free tier or trial was found (0). A person has to buy through sales and create keys in the dashboard (0). Total 0.", "b": "No x402, MPP or L402 (0). Prices are public as volume tiers from $19 for 15,000 emails to $2,999 for 5 million, without a per-email overage rate (10 of 20). Free plan of 2,500 emails a month with no card (20). Agents can register through `service_auth`, but the user has to confirm a code in a Sequenzy browser page, and plan payment is through Stripe (10 of 20). Total 40." }, "scores": { "a": 0, "b": 40 } }, { "by": 38, "category": "reliability", "leads": "moengage", "name": "Reliability", "reasons": { "a": "Graded on the REST API, with the hosted lines. Statuspage site at status.moengage.com with components for each data centre, among them Data APIs, Push APIs, Custom Segment API and Inform (20). In the 90 days from 4 August 2026 the history feed holds two incidents touching the APIs. On 27 October the Push API had \"downtime across our data centers\" from 02:20 UTC, restored for single-user sends at 12:39 and for all-user and segment sends at 13:23, and the Campaigns v1 API failed campaign creation from 03:13 to 14:14 UTC. That is about 11 hours of a core API down in every data centre, read as a major as nylas-email's all-region webhooks outage was. On 17 August the Inform API in DC-03 returned HTTP 200 for about 16 hours while a subset of messages was never sent, which is one region and a subset of requests, so partial and minor. The 20 October docs outage, the 24 September and 28 October dashboard incidents and two maintenance windows didn't touch the APIs. One major outage (10 of 30; the 9 October 8 isn't a checklist value, and its July incidents have left the window). Numeric limits are published for every endpoint group (15). 429 responses carry `x-ratelimit` headers, the OAuth and some V5 endpoints add `Retry-After`, and V5 campaigns and flow status changes take an `Idempotency-Key`. The Data APIs have no idempotency key (12). The published SLA commits to 99.9 per cent monthly availability with service credits (10). The REST API is generally available, with the Flows endpoints and the API key dashboard in early access (9). 20 + 10 + 15 + 12 + 10 + 9 = 76.", "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": 76, "b": 38 } }, { "by": 9, "category": "transparency", "leads": "moengage", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service. The published Terms of Use are short and undated, and the Master Service Agreement that the acceptable use policy refers to isn't public (13). A public DPA, a privacy policy dated 26 August 2026 that covers MoEngage as processor, an SLA that states backups every 12 hours kept for 3 months, and an AI policy that commits to no training of third-party models on customer data. Retention periods sit in a help centre article that wasn't read (22). No API deprecation policy was found. The docs say legacy API keys will be deprecated, with no date, and that the early access Flows endpoints won't receive breaking changes (5). The sub-processor list, last modified 1 September 2026, gives each processor's service and location, and the docs name the region of each data centre (20). Total 60.", "b": "A closed service. The SDK, MCP server and CLI are MIT on npm. The terms (30 June 2026) don't name the contracting entity in their text or a governing jurisdiction; the footer names Nic Tech Solutions, LLC (15 of 30). Privacy policy of 16 September 2026 and a public DPA agree on processing, and the terms say data is deleted within 30 days of termination (24 of 30). Deprecated endpoints are marked and kept as compatibility aliases; no written deprecation policy with notice periods (10 of 20). The DPA names its core sub-processors with their purpose; data locations aren't stated (15 of 20). Total 64." }, "scores": { "a": 76, "b": 67 } }, { "by": 8, "category": "schema", "leads": "sequenzy", "name": "Schema \u0026 documentation", "reasons": { "a": "37 OpenAPI 3 files are linked from the docs index on 2 November 2026 (36 on 9 October), with 140 operations on 119 paths and 535 schemas in the 36 read on 9 October; the files weren't recounted (25). The docs publish llms.txt, llms-full.txt, a Markdown twin of every page, a skill.md file and a docs MCP server (10). All 140 operations have a summary and a description, and the MCP page states what each tool can't do, but few descriptions say when not to use an endpoint (16). The files carry 503 enums and required lists, while 121 of 1,132 object schemas have no declared properties (12). There are 1,725 example entries, 400 or 401 on every operation and 429 on 103 (14). Versions are mixed (v1, v2, v2.1, v5 and a dated 2025-11-20 campaigns file). Monthly product release notes list new APIs and SDK changelogs are dated, but no API changelog was found (10). Total 87.", "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": 87, "b": 95 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "MoEngage, Inc.", "b": "Nic Tech Solutions, LLC", "name": "Vendor" }, { "a": "https://mcp.moengage.com", "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 MoEngage's Terms of Use and a customer agreement", "b": "none", "name": "Licence" }, { "a": "52", "b": "306", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.polnikale/sequenzy-mcp", "name": "MCP registry" }, { "a": "2026-10-14", "b": "2026-11-06", "name": "Last release" }, { "a": "no date given", "b": "2026-06-30", "name": "Terms last updated" }, { "a": "2026-08-26", "b": "2026-09-16", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "2.4k npm/wk", "name": "Popularity" }, { "a": "2.5/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "MoEngage scores 65.7 (B) on agent readiness against Sequenzy's 63.7 (B), and leads in 3 of 7 scored categories. Sequenzy leads on schema \u0026 documentation and payments \u0026 pricing.", "question": "Which is better for AI agents, MoEngage or Sequenzy?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do MoEngage and Sequenzy need an API key?" }, { "answer": "Yes. MoEngage has a hosted endpoint at https://mcp.moengage.com and Sequenzy at https://api.sequenzy.com/v1/mcp.", "question": "Can an agent call MoEngage and Sequenzy without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 76 against 38", "Transparency \u0026 trust, 76 against 67" ], "also": null, "goodFor": "A team already on MoEngage that wants an agent to update profiles, track events, build filter segments, draft Push and Email campaigns and read campaign, flow and analytics results.", "slug": "moengage", "watchFor": "No public price, free tier or trial. The pricing page lists Growth and Enterprise plans with a one-year minimum and a sales contact only" }, { "aheadOn": [ "Schema \u0026 documentation, 95 against 87", "Payments \u0026 pricing, 40 against 0" ], "also": [ "Runs on your own machine", "Free to start without a card" ], "goodFor": "SaaS and ecommerce lifecycle email run from code or an agent, with billing-event triggers from Stripe, Paddle and others.", "slug": "sequenzy", "watchFor": "About 306 MCP tools, with no toolsets or dynamic loading found" } ], "history": { "moengage": [ { "causes": [ "reliability" ], "date": "2026-11-02", "delta": 0.4, "from": 65.3, "fromGrade": "B", "to": 65.7, "toGrade": "B" }, { "causes": [ "evidence" ], "date": "2026-10-27", "delta": 0.1, "from": 65.2, "fromGrade": "B", "to": 65.3, "toGrade": "B" } ], "sequenzy": null }, "job": { "capability": "marketing.profiles", "name": "Marketing audiences" }, "others": [ { "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-sequenzy.json", "title": "ActiveCampaign vs Sequenzy", "url": "https://www.anchorterminal.com/compare/activecampaign-vs-sequenzy" }, { "json": "https://www.anchorterminal.com/compare/braze-vs-moengage.json", "title": "Braze vs MoEngage", "url": "https://www.anchorterminal.com/compare/braze-vs-moengage" }, { "json": "https://www.anchorterminal.com/compare/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-moengage.json", "title": "CleverTap vs MoEngage", "url": "https://www.anchorterminal.com/compare/clevertap-vs-moengage" }, { "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-moengage.json", "title": "Customer.io vs MoEngage", "url": "https://www.anchorterminal.com/compare/customer-io-vs-moengage" }, { "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-moengage.json", "title": "Iterable vs MoEngage", "url": "https://www.anchorterminal.com/compare/iterable-vs-moengage" }, { "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-moengage.json", "title": "Klaviyo API + MCP vs MoEngage", "url": "https://www.anchorterminal.com/compare/klaviyo-vs-moengage" }, { "json": "https://www.anchorterminal.com/compare/klaviyo-vs-sequenzy.json", "title": "Klaviyo API + MCP vs Sequenzy", "url": "https://www.anchorterminal.com/compare/klaviyo-vs-sequenzy" }, { "json": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-moengage.json", "title": "Mailchimp Marketing API vs MoEngage", "url": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-moengage" }, { "json": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-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-nitrosend.json", "title": "MoEngage vs Nitrosend", "url": "https://www.anchorterminal.com/compare/moengage-vs-nitrosend" }, { "json": "https://www.anchorterminal.com/compare/moengage-vs-omnisend.json", "title": "MoEngage vs Omnisend", "url": "https://www.anchorterminal.com/compare/moengage-vs-omnisend" }, { "json": "https://www.anchorterminal.com/compare/nitrosend-vs-sequenzy.json", "title": "Nitrosend vs Sequenzy", "url": "https://www.anchorterminal.com/compare/nitrosend-vs-sequenzy" }, { "json": "https://www.anchorterminal.com/compare/omnisend-vs-sequenzy.json", "title": "Omnisend vs Sequenzy", "url": "https://www.anchorterminal.com/compare/omnisend-vs-sequenzy" }, { "json": "https://www.anchorterminal.com/compare/dreamlit-vs-moengage.json", "title": "Dreamlit vs MoEngage", "url": "https://www.anchorterminal.com/compare/dreamlit-vs-moengage" }, { "json": "https://www.anchorterminal.com/compare/dreamlit-vs-sequenzy.json", "title": "Dreamlit vs Sequenzy", "url": "https://www.anchorterminal.com/compare/dreamlit-vs-sequenzy" } ], "panel": null, "scores": [ { "by": 38, "edge": "moengage", "key": "reliability", "moengage": 76, "name": "Reliability", "sequenzy": 38, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 8, "edge": "sequenzy", "key": "schema", "moengage": 87, "name": "Schema \u0026 documentation", "sequenzy": 95, "weight": 13 }, { "by": 1, "edge": "sequenzy", "key": "ergonomics", "moengage": 68, "name": "Agent ergonomics", "sequenzy": 69, "weight": 13 }, { "by": 2, "edge": "moengage", "key": "security", "moengage": 69, "name": "Security \u0026 auth", "sequenzy": 67, "weight": 14 }, { "by": 40, "edge": "sequenzy", "key": "payments", "moengage": 0, "name": "Payments \u0026 pricing", "sequenzy": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 3, "edge": "sequenzy", "key": "maintenance", "moengage": 75, "name": "Maintenance \u0026 community", "sequenzy": 78, "weight": 7 }, { "by": 9, "edge": "moengage", "key": "transparency", "moengage": 76, "name": "Transparency \u0026 trust", "sequenzy": 67, "weight": 7 } ], "summary": "MoEngage scores 65.7 (B) on agent readiness against Sequenzy's 63.7 (B), and leads in 3 of 7 scored categories. Sequenzy leads on schema \u0026 documentation and payments \u0026 pricing. Both do marketing audiences.", "tasks": null, "tutorials": [], "verdicts": { "moengage": "MoEngage publishes 37 OpenAPI files, a per-endpoint rate limit table, Markdown docs and a hosted MCP server that builds drafts and leaves publishing to a person. No price, trial or self-serve signup is published, and on 27 October 2026 the Push API was down across its data centres for about 11 hours.", "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/moengage-vs-sequenzy", "json": "https://www.anchorterminal.com/compare/moengage-vs-sequenzy.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/moengage-vs-sequenzy.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/moengage-vs-sequenzy.min.md" }, "markdown": "MoEngage scores 65.7 (B) on agent readiness against Sequenzy's 63.7 (B), and leads in 3 of 7 scored categories. Sequenzy leads on schema \u0026 documentation and payments \u0026 pricing. Both do marketing audiences.\n\n- MoEngage: grade B, 65.7/100, rank #405 of 1510. Markdown https://www.anchorterminal.com/tools/moengage.md · JSON https://www.anchorterminal.com/api/v1/tools/moengage.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### MoEngage (B)\n\nGood for: A team already on MoEngage that wants an agent to update profiles, track events, build filter segments, draft Push and Email campaigns and read campaign, flow and analytics results.\n\nAhead on:\n- Reliability, 76 against 38\n- Transparency \u0026 trust, 76 against 67\n\nWatch for: No public price, free tier or trial. The pricing page lists Growth and Enterprise plans with a one-year minimum and a sales contact only\n\n### 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 87\n- Payments \u0026 pricing, 40 against 0\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: About 306 MCP tools, with no toolsets or dynamic loading found\n\n\n## Why the edge\n\n### Payments \u0026 pricing: Sequenzy +40\n\n- MoEngage (0): No x402, MPP or L402 (0). No prices are published. The pricing page lists Growth and Enterprise plans with a sales contact (0). No free tier or trial was found (0). A person has to buy through sales and create keys in the dashboard (0). Total 0.\n- Sequenzy (40): No x402, MPP or L402 (0). Prices are public as volume tiers from $19 for 15,000 emails to $2,999 for 5 million, without a per-email overage rate (10 of 20). Free plan of 2,500 emails a month with no card (20). Agents can register through `service_auth`, but the user has to confirm a code in a Sequenzy browser page, and plan payment is through Stripe (10 of 20). Total 40.\n\n### Reliability: MoEngage +38\n\n- MoEngage (76): Graded on the REST API, with the hosted lines. Statuspage site at status.moengage.com with components for each data centre, among them Data APIs, Push APIs, Custom Segment API and Inform (20). In the 90 days from 4 August 2026 the history feed holds two incidents touching the APIs. On 27 October the Push API had \"downtime across our data centers\" from 02:20 UTC, restored for single-user sends at 12:39 and for all-user and segment sends at 13:23, and the Campaigns v1 API failed campaign creation from 03:13 to 14:14 UTC. That is about 11 hours of a core API down in every data centre, read as a major as nylas-email's all-region webhooks outage was. On 17 August the Inform API in DC-03 returned HTTP 200 for about 16 hours while a subset of messages was never sent, which is one region and a subset of requests, so partial and minor. The 20 October docs outage, the 24 September and 28 October dashboard incidents and two maintenance windows didn't touch the APIs. One major outage (10 of 30; the 9 October 8 isn't a checklist value, and its July incidents have left the window). Numeric limits are published for every endpoint group (15). 429 responses carry `x-ratelimit` headers, the OAuth and some V5 endpoints add `Retry-After`, and V5 campaigns and flow status changes take an `Idempotency-Key`. The Data APIs have no idempotency key (12). The published SLA commits to 99.9 per cent monthly availability with service credits (10). The REST API is generally available, with the Flows endpoints and the API key dashboard in early access (9). 20 + 10 + 15 + 12 + 10 + 9 = 76.\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### Transparency \u0026 trust: MoEngage +9\n\n- MoEngage (76): Closed service. The published Terms of Use are short and undated, and the Master Service Agreement that the acceptable use policy refers to isn't public (13). A public DPA, a privacy policy dated 26 August 2026 that covers MoEngage as processor, an SLA that states backups every 12 hours kept for 3 months, and an AI policy that commits to no training of third-party models on customer data. Retention periods sit in a help centre article that wasn't read (22). No API deprecation policy was found. The docs say legacy API keys will be deprecated, with no date, and that the early access Flows endpoints won't receive breaking changes (5). The sub-processor list, last modified 1 September 2026, gives each processor's service and location, and the docs name the region of each data centre (20). Total 60.\n- Sequenzy (67): A closed service. The SDK, MCP server and CLI are MIT on npm. The terms (30 June 2026) don't name the contracting entity in their text or a governing jurisdiction; the footer names Nic Tech Solutions, LLC (15 of 30). Privacy policy of 16 September 2026 and a public DPA agree on processing, and the terms say data is deleted within 30 days of termination (24 of 30). Deprecated endpoints are marked and kept as compatibility aliases; no written deprecation policy with notice periods (10 of 20). The DPA names its core sub-processors with their purpose; data locations aren't stated (15 of 20). Total 64.\n\n### Schema \u0026 documentation: Sequenzy +8\n\n- MoEngage (87): 37 OpenAPI 3 files are linked from the docs index on 2 November 2026 (36 on 9 October), with 140 operations on 119 paths and 535 schemas in the 36 read on 9 October; the files weren't recounted (25). The docs publish llms.txt, llms-full.txt, a Markdown twin of every page, a skill.md file and a docs MCP server (10). All 140 operations have a summary and a description, and the MCP page states what each tool can't do, but few descriptions say when not to use an endpoint (16). The files carry 503 enums and required lists, while 121 of 1,132 object schemas have no declared properties (12). There are 1,725 example entries, 400 or 401 on every operation and 429 on 103 (14). Versions are mixed (v1, v2, v2.1, v5 and a dated 2025-11-20 campaigns file). Monthly product release notes list new APIs and SDK changelogs are dated, but no API changelog was found (10). Total 87.\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## Score by category\n\n| Category | Weight | MoEngage | Sequenzy | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 76 | 38 | MoEngage +38 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 95 | Sequenzy +8 |\n| Agent ergonomics | 13% (16.2 this run) | 68 | 69 | Sequenzy +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 69 | 67 | MoEngage +2 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 40 | Sequenzy +40 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 78 | Sequenzy +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 76 | 67 | MoEngage +9 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **65.7 · B** | **63.7 · B** | |\n\n## Facts side by side\n\n| Fact | MoEngage | Sequenzy |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | MoEngage, Inc. | Nic Tech Solutions, LLC |\n| Hosted endpoint | `https://mcp.moengage.com` | `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 MoEngage's Terms of Use and a customer agreement | none |\n| Tools exposed | 52 | 306 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.polnikale/sequenzy-mcp` |\n| Last release | 2026-10-14 | 2026-11-06 |\n| Terms last updated | no date given | 2026-06-30 |\n| Privacy policy last updated | 2026-08-26 | 2026-09-16 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | none | 2.4k npm/wk |\n| Agent reviews | 2.5/5 (4) | none |\n\n## How the scores have moved\n\n### MoEngage\n\n- +0.4 on 2 November 2026: reliability\n- +0.1 on 27 October 2026: new evidence\n\n### Sequenzy\n\nNo score change since it was listed.\n\n## Verdicts\n\n**MoEngage.** MoEngage publishes 37 OpenAPI files, a per-endpoint rate limit table, Markdown docs and a hosted MCP server that builds drafts and leaves publishing to a person. No price, trial or self-serve signup is published, and on 27 October 2026 the Push API was down across its data centres for about 11 hours.\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### MoEngage\n\n1. Take the data centre number from the dashboard URL and call `https://api-{dc}.moengage.com`. Data can't be moved between data centres\n2. Send an `Idempotency-Key` header (UUID v4) on V5 campaign writes and test sends, and a `transaction_id` on Inform alerts, which deduplicates for 5 minutes\n3. Use internal event and attribute names in segment filters, and run `deep_validate_segment_filters` first. A wrong event name is accepted and the count later fails with no reason\n4. Use `in` with a list for text equality in segment filters. `equals` returns a 400 that names no field\n5. Reuse an OAuth access token until it nears expiry. The token endpoint allows 5 requests a minute and 30 per 10 minutes for each key\n\n### 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, MoEngage or Sequenzy?\n\nMoEngage scores 65.7 (B) on agent readiness against Sequenzy's 63.7 (B), and leads in 3 of 7 scored categories. Sequenzy leads on schema \u0026 documentation and payments \u0026 pricing.\n\n### Do MoEngage and Sequenzy need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call MoEngage and Sequenzy without installing anything?\n\nYes. MoEngage has a hosted endpoint at https://mcp.moengage.com and Sequenzy at https://api.sequenzy.com/v1/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/moengage-vs-sequenzy.json, and with the fewest tokens: https://www.anchorterminal.com/compare/moengage-vs-sequenzy.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"moengage\", \"b\": \"sequenzy\"}`. From a terminal: `anchor compare moengage sequenzy`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/moengage.json and https://www.anchorterminal.com/api/v1/tools/sequenzy.json\n\n## Other comparisons with MoEngage or Sequenzy\n\n- [ActiveCampaign vs MoEngage](https://www.anchorterminal.com/compare/activecampaign-vs-moengage.md)\n- [ActiveCampaign vs Sequenzy](https://www.anchorterminal.com/compare/activecampaign-vs-sequenzy.md)\n- [Braze vs MoEngage](https://www.anchorterminal.com/compare/braze-vs-moengage.md)\n- [Braze vs Sequenzy](https://www.anchorterminal.com/compare/braze-vs-sequenzy.md)\n- [CleverTap vs MoEngage](https://www.anchorterminal.com/compare/clevertap-vs-moengage.md)\n- [CleverTap vs Sequenzy](https://www.anchorterminal.com/compare/clevertap-vs-sequenzy.md)\n- [Customer.io vs MoEngage](https://www.anchorterminal.com/compare/customer-io-vs-moengage.md)\n- [Customer.io vs Sequenzy](https://www.anchorterminal.com/compare/customer-io-vs-sequenzy.md)\n- [Iterable vs MoEngage](https://www.anchorterminal.com/compare/iterable-vs-moengage.md)\n- [Iterable vs Sequenzy](https://www.anchorterminal.com/compare/iterable-vs-sequenzy.md)\n- [Klaviyo API + MCP vs MoEngage](https://www.anchorterminal.com/compare/klaviyo-vs-moengage.md)\n- [Klaviyo API + MCP vs Sequenzy](https://www.anchorterminal.com/compare/klaviyo-vs-sequenzy.md)\n- [Mailchimp Marketing API vs MoEngage](https://www.anchorterminal.com/compare/mailchimp-marketing-vs-moengage.md)\n- [Mailchimp Marketing API vs Sequenzy](https://www.anchorterminal.com/compare/mailchimp-marketing-vs-sequenzy.md)\n- [MoEngage vs Nitrosend](https://www.anchorterminal.com/compare/moengage-vs-nitrosend.md)\n- [MoEngage vs Omnisend](https://www.anchorterminal.com/compare/moengage-vs-omnisend.md)\n- [Nitrosend vs Sequenzy](https://www.anchorterminal.com/compare/nitrosend-vs-sequenzy.md)\n- [Omnisend vs Sequenzy](https://www.anchorterminal.com/compare/omnisend-vs-sequenzy.md)\n- [Dreamlit vs MoEngage](https://www.anchorterminal.com/compare/dreamlit-vs-moengage.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": "MoEngage vs Sequenzy", "url": "" } ], "description": "MoEngage scores 65.7 (B) to Sequenzy's 63.7 (B) for marketing audiences. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "MoEngage B 65.7", "Sequenzy B 63.7", "scores" ], "h1": "MoEngage vs Sequenzy", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/moengage-vs-sequenzy", "published": "2026-10-01", "section": "tools", "title": "MoEngage vs Sequenzy for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/moengage-vs-sequenzy" }, "tokens": { "markdown": 4000, "slim": 2180 }, "version": 1 }