{ "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", "license": "Proprietary service under MoEngage's Terms of Use and a customer agreement", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://mcp.moengage.com", "packages": [], "auth": "mixed", "authNotes": "Access needs a MoEngage customer workspace, which is sold through sales. A dashboard user creates API keys under Settings, Account, APIs. The default is HTTP Basic with the Workspace ID as username and the API key as password, with separate keys for Data, Push, Inform, Campaigns and Personalise. An API key dashboard, in early access and enabled on request, adds named keys scoped to chosen API groups, OAuth 2.0 client credentials (access tokens of 5 to 60 minutes, refresh tokens of 30 days, issued at `https://oauth2-{dc}.moengage.com`) and AWS STS role ARNs. Segmentation and Inform accept Basic only. The MCP server uses OAuth with the user's own MoEngage login and role, a second factor, and a 30-day session with a 7-day idle timeout. No app review or partner approval was found.", "pricing": "paid", "pricingNotes": "No public prices. https://www.moengage.com/plans-and-pricing/ lists Growth and Enterprise plans, counted in monthly tracked users, with a sales contact and a one-year minimum commitment. No free tier, trial or self-serve signup was found. Each workspace has Live and Test environments and Inform has a sandbox host, but both sit inside a customer account, so an agent can't start without a contract. API and MCP calls aren't priced per call in any page read (checked 2026-10-09).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API documentation, the OpenAPI files, the pricing page or the legal pages (checked 2026-10-09).", "endpoints": [] }, "toolCount": 52, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://www.moengage.com/docs/api/introduction", "llmsTxt": "https://www.moengage.com/docs/llms.txt", "openapi": "https://www.moengage.com/docs/api/data/data.yaml", "capabilities": [ "marketing.profiles", "marketing.events", "marketing.segments", "marketing.campaigns", "marketing.journeys", "email.templates", "notify.push" ], "tags": [ "official", "hosted", "mcp", "oauth", "api-key", "openapi", "llms-txt", "closed-source", "sales-led", "enterprise", "eu-region", "status-page", "soc2", "sla" ], "lastRelease": "2026-10-09", "graded": true, "anchor": { "graded": true, "score": 65.2, "grade": "B", "agentReady": false, "rank": 327, "ranked": true, "rankOf": 950, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 68, "maintenance": 75, "payments": 0, "reliability": 74, "schema": 87, "security": 69, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "MoEngage publishes 36 OpenAPI files covering 140 operations, a per-endpoint rate limit table, Markdown docs and a hosted MCP server that builds drafts and leaves publishing to a person. No price, trial or self-serve signup is published, and on 17 August 2026 the Inform API in one data centre accepted requests for about 16 hours without sending the messages.", "bestFor": "A team already on MoEngage that wants an agent to update profiles, track events, build filter segments, draft Push and Email campaigns and read campaign, flow and analytics results.", "strengths": [ "36 public OpenAPI files with 140 operations, every one with a summary and description, and a 429 response documented on 103", "A rate limit table with numbers for every endpoint group, plus `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset` response headers", "The hosted MCP server at mcp.moengage.com uses OAuth tied to the user's role, masks PII attributes and cannot publish a campaign", "API keys can be scoped to chosen API groups, use OAuth 2.0 tokens of 5 to 60 minutes or AWS STS roles, and be limited by IP address", "A published SLA of 99.9 per cent monthly availability, a public DPA and a sub-processor list with locations dated 1 September 2026" ], "weaknesses": [ "No public price, free tier or trial. The pricing page lists Growth and Enterprise plans with a one-year minimum and a sales contact only", "On 17 August 2026 the Inform API in DC-03 returned HTTP 200 for about 16 hours while some messages were never sent, per the status page", "Scoped keys, OAuth 2.0 and AWS STS keys sit in an API key dashboard that is in early access and enabled on request", "Segmentation and Inform accept Basic authentication only, and new Push API keys can't be created", "No API deprecation policy was found, and no official server-side API client library was found in the documentation" ], "agentNotes": [ "Take the data centre number from the dashboard URL and call `https://api-{dc}.moengage.com`. Data can't be moved between data centres", "Send an `Idempotency-Key` header (UUID v4) on V5 campaign writes and test sends, and a `transaction_id` on Inform alerts, which deduplicates for 5 minutes", "Use internal event and attribute names in segment filters, and run `deep_validate_segment_filters` first. A wrong event name is accepted and the count later fails with no reason", "Use `in` with a list for text equality in segment filters. `equals` returns a 400 that names no field", "Reuse an OAuth access token until it nears expiry. The token endpoint allows 5 requests a minute and 30 per 10 minutes for each key" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 65.2 } ], "editorialScores": { "ergonomics": 68, "maintenance": 75, "payments": 0, "reliability": 74, "schema": 87, "security": 69, "transparency": 60 }, "provenanceScore": 89 }, "connect": { "http": "curl --request POST \\\n --url https://api-{dc}.moengage.com/v1/customer/YOUR_WORKSPACE_ID \\\n --header 'Authorization: Bearer YOUR_ACCESS_TOKEN' \\\n --header 'Content-Type: application/json' \\\n --data '{ \"type\": \"customer\", \"customer_id\": \"user_12345\" }'", "config": { "mcpServers": { "moengage": { "url": "https://mcp.moengage.com" } } } }, "letme": { "capability": "https://letme.dev/marketing.profiles", "tool": "https://letme.dev/moengage" }, "area": "communication", "provenance": { "legalEntity": "MoEngage, Inc.", "domain": "moengage.com", "domainRegistered": "2014-04-19", "endpointOnVendorDomain": true, "terms": "https://www.moengage.com/terms-of-use/", "privacy": "https://www.moengage.com/privacy-policy/", "statusPage": "https://status.moengage.com", "changelog": "https://www.moengage.com/docs/release-notes/product/2026/september-2026", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Terms of Use name MoEngage, Inc., a Delaware corporation, and say they govern the website and related software and services. They carry no date. The DPA and sub-processor list name MoEngage Global Inc.", "The acceptable use policy (last updated 14 May 2026) refers to a Master Service Agreement between MoEngage and its customers. That agreement isn't published.", "The privacy policy was last updated on 26 August 2026 and covers MoEngage as processor for its customers' end users.", "The API answers at api-{dc}.moengage.com and the MCP server at mcp.moengage.com, both on the vendor's domain.", "https://www.moengage.com/.well-known/security.txt returns 404. Reports go to the address in the responsible disclosure policy.", "Release notes are one page a month under /docs/release-notes/product/, with separate dated changelogs for each SDK.", "RDAP for moengage.com gives a registration date of 2014-04-19." ], "score": 89 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/moengage.json", "live": { "slug": "moengage", "probe": { "target": "https://mcp.moengage.com", "method": "get", "lastAt": "2026-10-10T03:53:35.125620945Z", "lastOk": true, "lastStatus": 401, "lastMs": 31, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 99.2, "uptime30d": 99.2, "p50ms24h": 36, "p95ms24h": 134, "samples24h": 125, "samples30d": 125, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 40, "ok": 39 } ] }, "vendorStatus": { "page": "https://status.moengage.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T03:58:28.483064795Z" }, "pages": [ { "url": "https://www.moengage.com/docs/release-notes/product/2026/september-2026", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:52:19.636830436Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "01e807658b5c" }, { "url": "https://www.moengage.com/plans-and-pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:52:23.984233527Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "159b4036728b" }, { "url": "https://www.moengage.com/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:52:24.146105363Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "cf0f65af7274" }, { "url": "https://www.moengage.com/terms-of-use/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:52:26.055494253Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3a3cf18334cc" } ], "updatedAt": "2026-10-10T03:58:28.483064795Z" } }, "answer": "MoEngage and Omnisend score within a point of each other on agent readiness, 65.2 (B) and 64.9 (B). Omnisend leads on reliability, agent ergonomics and payments \u0026 pricing.", "b": { "slug": "omnisend", "name": "Omnisend", "vendor": "Omnisend, UAB", "vendorUrl": "https://www.omnisend.com", "kind": "http-api", "category": "lifecycle-marketing", "summary": "Omnisend is an email, SMS and push marketing platform for online shops. Agents reach contacts, events, segments, campaigns, automations and forms through a REST API with dated versions and an official hosted MCP server.", "url": "https://www.anchorterminal.com/tools/omnisend", "markdownUrl": "https://www.anchorterminal.com/tools/omnisend.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/omnisend.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/omnisend.json", "license": "Proprietary service under Omnisend's Terms of Use", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.omnisend.com/api", "packages": [], "auth": "mixed", "authNotes": "Access is self-serve with an API key. A user creates a named key in the app under API keys, copies it once, and sends it as `Authorization: Omnisend-API-Key \u003ckey\u003e` with `Omnisend-Version: 2026-03-15`. OAuth 2.0 with the authorisation code grant and per-resource scopes is for apps, and credentials are issued through a request form in one to three business days. The hosted MCP server takes OAuth with dynamic client registration, needs the Owner, Admin, Manager or Partner role, and asks for an access level on the consent screen. Whether an API key can be limited to scopes was not found in the pages read.", "pricing": "freemium", "pricingNotes": "Free plan with 250 contacts and 500 emails a month, no credit card required, so an agent's owner can start without a contract. Paid plans scale with contacts through a slider. At the page's defaults Standard (500 contacts, 6,000 emails a month) shows $11.20 a month for the first three months against a three-month total of $48.00, and Pro (2,500 contacts, unlimited emails) $41.30 against $177.00. SMS starts at $0.007 a message. API calls aren't metered, and the page lists Omnisend MCP under every plan (https://www.omnisend.com/pricing/, checked 2026-10-09).", "priceSummary": "$16 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API documentation or the pricing page. The 402 response on the send campaign endpoint is an ordinary plan payment error (checked 2026-10-09).", "endpoints": [] }, "toolCount": 4, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://api-docs.omnisend.com/", "llmsTxt": "https://api-docs.omnisend.com/llms.txt", "capabilities": [ "marketing.profiles", "marketing.events", "marketing.segments", "marketing.campaigns", "marketing.journeys", "email.templates", "forms.create" ], "tags": [ "official", "hosted", "mcp", "closed-source", "oauth", "llms-txt", "free-tier", "no-card", "status-page", "bug-bounty" ], "lastRelease": "2026-07-10", "graded": true, "anchor": { "graded": true, "score": 64.9, "grade": "B", "agentReady": false, "rank": 334, "ranked": true, "rankOf": 950, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 79, "maintenance": 29, "payments": 30, "reliability": 81, "schema": 79, "security": 57, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "The API documents 104 operations with per-operation OpenAPI definitions, cursor pagination, RFC 9457 errors and published rate limits, and the hosted MCP server fronts them with four tools and a read-only consent preset. No approval hold before a campaign send, no idempotency keys, no SLA and no official SDK were found in the reviewed documentation.", "bestFor": "Online shops already on Omnisend that want an agent to read campaign results, manage contacts and segments, and draft campaigns or automations.", "strengths": [ "Each of the 104 documented operations has a Markdown page with its OpenAPI 3.0 definition, required scopes and rate limit, indexed in `llms.txt`", "The hosted MCP server lists four tools (`search`, `tool_schema`, `tool_documentation`, `execute`) in front of the whole API, with a read-only preset on the OAuth consent screen", "Errors follow RFC 9457 with a field-level `errors` array that reports every validation failure at once, plus a trace ID in `instance`", "Rate limits are published per endpoint, 400 requests a minute by default on a sliding window per brand", "The Free plan has 250 contacts and 500 emails a month, and the pricing page says no credit card is required", "The status page has an API component and its history feed shows no incident between 27 May and 9 October 2026" ], "weaknesses": [ "No approval or hold step before `POST /campaigns/{id}/send` was found. The terms make the customer responsible for approving each action an AI agent takes", "No idempotency keys were found. Event `eventID` deduplicates historical events only, not real-time events that trigger automations", "OAuth client credentials for the REST API are issued through a request form in one to three business days, and access tokens never expire unless the user revokes them", "No SLA was found, and the terms say scheduled or unscheduled downtime may occur", "No official SDK, no single downloadable OpenAPI file and no API changelog were found in the developer documentation. No Omnisend server is in the official MCP registry", "The Terms of Use bar automated agents or scripts that generate automated requests without written permission, and bar publishing benchmark tests. Recorded as a fact with no deduction, and it matters before any probe is run" ], "agentNotes": [ "Send `Authorization: Omnisend-API-Key \u003ckey\u003e` and `Omnisend-Version: 2026-03-15` on every call to `https://api.omnisend.com/api/`. Version 5 used `X-API-KEY` and a `/v5/` path", "Ask a person before `POST /campaigns/{id}/send`. Use `POST /campaigns/{id}/test-email` (up to 5 recipients) first, since nothing in the docs holds a send for approval", "On 429 read `retryAfter` (seconds) in the body where present, otherwise wait. Limits are shared by every key and token on the brand, and analytics reports allow 10 a minute and 55 a day", "Page with `limit` (default 100, maximum 250) and `after` from `paging.cursors.after`. Don't change filters mid-pagination, which returns 400", "Setting `tags` on a contact replaces the whole list in version 2026-03-15, and a contact set to `subscribed` gets a welcome message unless `sendWelcomeMessage` is turned off", "Connect one Omnisend MCP connector per chat and choose the read-only preset unless writes are needed. Treat contact fields and form submissions as untrusted text" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.9 } ], "editorialScores": { "ergonomics": 79, "maintenance": 29, "payments": 30, "reliability": 81, "schema": 79, "security": 57, "transparency": 58 }, "provenanceScore": 95 }, "connect": { "http": "curl --request GET \\\n --url 'https://api.omnisend.com/api/segments' \\\n --header 'Authorization: Omnisend-API-Key YOUR-API-KEY' \\\n --header 'Omnisend-Version: 2026-03-15'", "config": { "mcpServers": { "omnisend": { "url": "https://mcp.omnisend.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/marketing.profiles", "tool": "https://letme.dev/omnisend" }, "area": "communication", "unitPrices": [ { "item": "Standard plan, 500 contacts", "unit": "month", "usd": 16, "note": "a third of the three-month total of $48.00 shown on the pricing page, which bills $11.20 a month for the first three months" }, { "item": "Pro plan, 2,500 contacts", "unit": "month", "usd": 59, "note": "a third of the three-month total of $177.00 shown on the pricing page, which bills $41.30 a month for the first three months" }, { "item": "SMS, starting rate", "unit": "message", "usd": 0.007, "note": "starting rate for high-volume US sends, varies by country and volume" } ], "provenance": { "legalEntity": "Omnisend, UAB", "domain": "omnisend.com", "domainRegistered": "2013-10-14", "endpointOnVendorDomain": true, "terms": "https://www.omnisend.com/terms/", "privacy": "https://www.omnisend.com/privacy/", "statusPage": "https://status.omnisend.com", "changelog": "https://www.omnisend.com/changelog/", "securityTxt": "valid", "checked": "2026-10-09", "notes": [ "The Terms of Use (last updated 30 April 2026) name Omnisend, UAB, legal entity code 302530363, Vilnius, Lithuania, as the contracting party. They are the service agreement and include a section on AI agents, MCP and the API.", "The Privacy Policy (last updated 18 June 2026) covers the group's companies as controllers. Processing of customers' contact data is governed by the Data Processing Agreement of 22 September 2025.", "The REST API answers at api.omnisend.com and the MCP server at mcp.omnisend.com, both omnisend.com subdomains.", "www.omnisend.com/.well-known/security.txt gives security@omnisend.com and the bug bounty page as policy, and has no Expires field, which RFC 9116 requires. It is recorded as valid.", "The changelog is the product changelog. No API changelog was found in the developer documentation.", "RDAP for omnisend.com gives a registration date of 2013-10-14." ], "score": 95 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/omnisend.json", "live": { "slug": "omnisend", "probe": { "target": "https://api.omnisend.com/api", "method": "get", "lastAt": "2026-10-10T03:53:36.417415425Z", "lastOk": true, "lastStatus": 404, "lastMs": 135, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 150, "p95ms24h": 223, "samples24h": 125, "samples30d": 125, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.omnisend.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T03:58:30.213877732Z" }, "pages": [ { "url": "https://www.omnisend.com/changelog/", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:52:40.626914195Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "4ee91ee1c9c0" }, { "url": "https://www.omnisend.com/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:52:43.649861328Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "a4f809f8a468" }, { "url": "https://www.omnisend.com/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:52:45.267503247Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "2fe5ad4e76ef" }, { "url": "https://www.omnisend.com/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:52:47.254298905Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "8732e799e365" } ], "updatedAt": "2026-10-10T03:58:30.213877732Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "MoEngage, Inc.", "b": "Omnisend, UAB", "name": "Vendor" }, { "a": "https://mcp.moengage.com", "b": "https://api.omnisend.com/api", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under MoEngage's Terms of Use and a customer agreement", "b": "Proprietary service under Omnisend's Terms of Use", "name": "Licence" }, { "a": "52", "b": "4", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-09", "b": "2026-07-10", "name": "Last release" }, { "a": "no date given", "b": "2026-04-30", "name": "Terms last updated" }, { "a": "2026-08-26", "b": "2026-06-18", "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": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "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" } ], "faq": [ { "answer": "MoEngage and Omnisend score within a point of each other on agent readiness, 65.2 (B) and 64.9 (B). Omnisend leads on reliability, agent ergonomics and payments \u0026 pricing.", "question": "Which is better for AI agents, MoEngage or Omnisend?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do MoEngage and Omnisend need an API key?" }, { "answer": "Yes. MoEngage has a hosted endpoint at https://mcp.moengage.com and Omnisend at https://api.omnisend.com/api.", "question": "Can an agent call MoEngage and Omnisend without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 87 against 79", "Security \u0026 auth, 69 against 57", "Maintenance \u0026 community, 75 against 29" ], "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": [ "Reliability, 81 against 74", "Agent ergonomics, 79 against 68", "Payments \u0026 pricing, 30 against 0" ], "also": [ "Free to start without a card" ], "goodFor": "Online shops already on Omnisend that want an agent to read campaign results, manage contacts and segments, and draft campaigns or automations.", "slug": "omnisend", "watchFor": "No approval or hold step before `POST /campaigns/{id}/send` was found. The terms make the customer responsible for approving each action an AI agent takes" } ], "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-omnisend.json", "title": "ActiveCampaign vs Omnisend", "url": "https://www.anchorterminal.com/compare/activecampaign-vs-omnisend" }, { "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-omnisend.json", "title": "Braze vs Omnisend", "url": "https://www.anchorterminal.com/compare/braze-vs-omnisend" }, { "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-omnisend.json", "title": "CleverTap vs Omnisend", "url": "https://www.anchorterminal.com/compare/clevertap-vs-omnisend" }, { "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-omnisend.json", "title": "Customer.io vs Omnisend", "url": "https://www.anchorterminal.com/compare/customer-io-vs-omnisend" }, { "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-omnisend.json", "title": "Iterable vs Omnisend", "url": "https://www.anchorterminal.com/compare/iterable-vs-omnisend" }, { "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-omnisend.json", "title": "Klaviyo API + MCP vs Omnisend", "url": "https://www.anchorterminal.com/compare/klaviyo-vs-omnisend" }, { "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-omnisend.json", "title": "Mailchimp Marketing API vs Omnisend", "url": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-omnisend" } ], "scores": [ { "by": 7, "edge": "omnisend", "key": "reliability", "moengage": 74, "name": "Reliability", "omnisend": 81, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 8, "edge": "moengage", "key": "schema", "moengage": 87, "name": "Schema \u0026 documentation", "omnisend": 79, "weight": 13 }, { "by": 11, "edge": "omnisend", "key": "ergonomics", "moengage": 68, "name": "Agent ergonomics", "omnisend": 79, "weight": 13 }, { "by": 12, "edge": "moengage", "key": "security", "moengage": 69, "name": "Security \u0026 auth", "omnisend": 57, "weight": 14 }, { "by": 30, "edge": "omnisend", "key": "payments", "moengage": 0, "name": "Payments \u0026 pricing", "omnisend": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 46, "edge": "moengage", "key": "maintenance", "moengage": 75, "name": "Maintenance \u0026 community", "omnisend": 29, "weight": 7 }, { "by": 2, "edge": "omnisend", "key": "transparency", "moengage": 75, "name": "Transparency \u0026 trust", "omnisend": 77, "weight": 7 } ], "summary": "MoEngage and Omnisend score within a point of each other on agent readiness, 65.2 (B) and 64.9 (B). Omnisend leads on reliability, agent ergonomics and payments \u0026 pricing. Both do marketing audiences.", "verdicts": { "moengage": "MoEngage publishes 36 OpenAPI files covering 140 operations, a per-endpoint rate limit table, Markdown docs and a hosted MCP server that builds drafts and leaves publishing to a person. No price, trial or self-serve signup is published, and on 17 August 2026 the Inform API in one data centre accepted requests for about 16 hours without sending the messages.", "omnisend": "The API documents 104 operations with per-operation OpenAPI definitions, cursor pagination, RFC 9457 errors and published rate limits, and the hosted MCP server fronts them with four tools and a read-only consent preset. No approval hold before a campaign send, no idempotency keys, no SLA and no official SDK were found in the reviewed documentation." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/moengage-vs-omnisend", "json": "https://www.anchorterminal.com/compare/moengage-vs-omnisend.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/moengage-vs-omnisend.md", "slim": "https://www.anchorterminal.com/compare/moengage-vs-omnisend.min.md" }, "markdown": "MoEngage and Omnisend score within a point of each other on agent readiness, 65.2 (B) and 64.9 (B). Omnisend leads on reliability, agent ergonomics and payments \u0026 pricing. Both do marketing audiences.\n\n- MoEngage: grade B, 65.2/100, rank #327 of 950. Markdown https://www.anchorterminal.com/tools/moengage.md · JSON https://www.anchorterminal.com/api/v1/tools/moengage.json\n- Omnisend: grade B, 64.9/100, rank #334 of 950. Markdown https://www.anchorterminal.com/tools/omnisend.md · JSON https://www.anchorterminal.com/api/v1/tools/omnisend.json\n- Best lifecycle marketing and customer engagement platforms for AI agents: https://www.anchorterminal.com/best/lifecycle-marketing/index.md\n- All 36 lifecycle marketing comparisons: https://www.anchorterminal.com/compare/lifecycle-marketing/index.md\n\n## Which one, for what\n\n### 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- Schema \u0026 documentation, 87 against 79\n- Security \u0026 auth, 69 against 57\n- Maintenance \u0026 community, 75 against 29\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### Omnisend (B)\n\nGood for: Online shops already on Omnisend that want an agent to read campaign results, manage contacts and segments, and draft campaigns or automations.\n\nAhead on:\n- Reliability, 81 against 74\n- Agent ergonomics, 79 against 68\n- Payments \u0026 pricing, 30 against 0\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No approval or hold step before `POST /campaigns/{id}/send` was found. The terms make the customer responsible for approving each action an AI agent takes\n\n\n## Score by category\n\n| Category | Weight | MoEngage | Omnisend | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 74 | 81 | Omnisend +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 79 | MoEngage +8 |\n| Agent ergonomics | 13% (16.2 this run) | 68 | 79 | Omnisend +11 |\n| Security \u0026 auth | 14% (17.5 this run) | 69 | 57 | MoEngage +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 30 | Omnisend +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 29 | MoEngage +46 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 75 | 77 | Omnisend +2 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **65.2 · B** | **64.9 · B** | |\n\n## Facts side by side\n\n| Fact | MoEngage | Omnisend |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | MoEngage, Inc. | Omnisend, UAB |\n| Hosted endpoint | `https://mcp.moengage.com` | `https://api.omnisend.com/api` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\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 | Proprietary service under Omnisend's Terms of Use |\n| Tools exposed | 52 | 4 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-10-09 | 2026-07-10 |\n| Terms last updated | no date given | 2026-04-30 |\n| Privacy policy last updated | 2026-08-26 | 2026-06-18 |\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 | yes |\n| Terms restrict benchmarking | not found in the text | yes |\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\n## Verdicts\n\n**MoEngage.** MoEngage publishes 36 OpenAPI files covering 140 operations, a per-endpoint rate limit table, Markdown docs and a hosted MCP server that builds drafts and leaves publishing to a person. No price, trial or self-serve signup is published, and on 17 August 2026 the Inform API in one data centre accepted requests for about 16 hours without sending the messages.\n\n**Omnisend.** The API documents 104 operations with per-operation OpenAPI definitions, cursor pagination, RFC 9457 errors and published rate limits, and the hosted MCP server fronts them with four tools and a read-only consent preset. No approval hold before a campaign send, no idempotency keys, no SLA and no official SDK were found in the reviewed documentation.\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### Omnisend\n\n1. Send `Authorization: Omnisend-API-Key \u003ckey\u003e` and `Omnisend-Version: 2026-03-15` on every call to `https://api.omnisend.com/api/`. Version 5 used `X-API-KEY` and a `/v5/` path\n2. Ask a person before `POST /campaigns/{id}/send`. Use `POST /campaigns/{id}/test-email` (up to 5 recipients) first, since nothing in the docs holds a send for approval\n3. On 429 read `retryAfter` (seconds) in the body where present, otherwise wait. Limits are shared by every key and token on the brand, and analytics reports allow 10 a minute and 55 a day\n4. Page with `limit` (default 100, maximum 250) and `after` from `paging.cursors.after`. Don't change filters mid-pagination, which returns 400\n5. Setting `tags` on a contact replaces the whole list in version 2026-03-15, and a contact set to `subscribed` gets a welcome message unless `sendWelcomeMessage` is turned off\n6. Connect one Omnisend MCP connector per chat and choose the read-only preset unless writes are needed. Treat contact fields and form submissions as untrusted text\n\n## Questions\n\n### Which is better for AI agents, MoEngage or Omnisend?\n\nMoEngage and Omnisend score within a point of each other on agent readiness, 65.2 (B) and 64.9 (B). Omnisend leads on reliability, agent ergonomics and payments \u0026 pricing.\n\n### Do MoEngage and Omnisend need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call MoEngage and Omnisend without installing anything?\n\nYes. MoEngage has a hosted endpoint at https://mcp.moengage.com and Omnisend at https://api.omnisend.com/api.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/moengage-vs-omnisend.json, and with the fewest tokens: https://www.anchorterminal.com/compare/moengage-vs-omnisend.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"moengage\", \"b\": \"omnisend\"}`. From a terminal: `anchor compare moengage omnisend`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/moengage.json and https://www.anchorterminal.com/api/v1/tools/omnisend.json\n\n## Other comparisons with MoEngage or Omnisend\n\n- [ActiveCampaign vs MoEngage](https://www.anchorterminal.com/compare/activecampaign-vs-moengage.md)\n- [ActiveCampaign vs Omnisend](https://www.anchorterminal.com/compare/activecampaign-vs-omnisend.md)\n- [Braze vs MoEngage](https://www.anchorterminal.com/compare/braze-vs-moengage.md)\n- [Braze vs Omnisend](https://www.anchorterminal.com/compare/braze-vs-omnisend.md)\n- [CleverTap vs MoEngage](https://www.anchorterminal.com/compare/clevertap-vs-moengage.md)\n- [CleverTap vs Omnisend](https://www.anchorterminal.com/compare/clevertap-vs-omnisend.md)\n- [Customer.io vs MoEngage](https://www.anchorterminal.com/compare/customer-io-vs-moengage.md)\n- [Customer.io vs Omnisend](https://www.anchorterminal.com/compare/customer-io-vs-omnisend.md)\n- [Iterable vs MoEngage](https://www.anchorterminal.com/compare/iterable-vs-moengage.md)\n- [Iterable vs Omnisend](https://www.anchorterminal.com/compare/iterable-vs-omnisend.md)\n- [Klaviyo API + MCP vs MoEngage](https://www.anchorterminal.com/compare/klaviyo-vs-moengage.md)\n- [Klaviyo API + MCP vs Omnisend](https://www.anchorterminal.com/compare/klaviyo-vs-omnisend.md)\n- [Mailchimp Marketing API vs MoEngage](https://www.anchorterminal.com/compare/mailchimp-marketing-vs-moengage.md)\n- [Mailchimp Marketing API vs Omnisend](https://www.anchorterminal.com/compare/mailchimp-marketing-vs-omnisend.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "MoEngage vs Omnisend", "url": "" } ], "description": "MoEngage and Omnisend score within a point of each other for marketing audiences, 65.2 and 64.9 out of 100. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "MoEngage B 65.2", "Omnisend B 64.9", "scores" ], "h1": "MoEngage vs Omnisend", "image": "https://www.anchorterminal.com/assets/og/compare-moengage-vs-omnisend.png", "path": "/compare/moengage-vs-omnisend", "published": "2026-10-01", "section": "tools", "title": "MoEngage vs Omnisend for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/moengage-vs-omnisend" }, "tokens": { "markdown": 2350, "slim": 630 }, "version": 1 }