{ "data": { "a": { "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", "dns": "omnisend.grade.anchorterminal.com", "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-10-30", "graded": true, "anchor": { "graded": true, "score": 65.8, "grade": "B", "agentReady": false, "rank": 398, "ranked": true, "rankOf": 1486, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 79, "maintenance": 39, "payments": 30, "reliability": 81, "schema": 79, "security": 57, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": 0, "verdict": "The API documents 105 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 105 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 2 November 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": 4, "avgRating": 2.8, "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.8 } ], "editorialScores": { "ergonomics": 79, "maintenance": 39, "payments": 30, "reliability": 81, "schema": 79, "security": 57, "transparency": 58 }, "provenanceScore": 95, "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 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-11-07T18:20:43.348740728Z", "lastOk": true, "lastStatus": 404, "lastMs": 155, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 150, "p95ms24h": 241, "samples24h": 239, "samples30d": 7205, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "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": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.omnisend.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:21:36.122450143Z" }, "securityTxt": { "url": "https://omnisend.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T16:00:24.921506467Z" }, "llmsTxt": { "url": "https://api-docs.omnisend.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:21.598946593Z" }, "domain": { "domain": "omnisend.com", "registered": "2013-10-14", "source": "https://rdap.verisign.com/com/v1/domain/omnisend.com", "checkedAt": "2026-11-01T14:23:47.36701877Z" }, "pages": [ { "url": "https://www.omnisend.com/changelog/", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:32:17.570067313Z", "changedAt": "2026-11-06T13:52:49.268791301Z", "fingerprint": "db14a3ae4341" }, { "url": "https://www.omnisend.com/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:32:21.325793344Z", "changedAt": "2026-11-06T13:52:52.465409397Z", "fingerprint": "feca824fb943" }, { "url": "https://www.omnisend.com/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:32:22.659737725Z", "changedAt": "2026-11-06T13:52:54.483756105Z", "fingerprint": "885daa12d156" }, { "url": "https://www.omnisend.com/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:32:24.30342253Z", "changedAt": "2026-11-06T13:52:57.08796894Z", "fingerprint": "651859b89c36" } ], "mcpTools": { "url": "https://mcp.omnisend.com/mcp", "checkedAt": "2026-11-07T01:46:34.124454228Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:34.124454228Z" }, "updatedAt": "2026-11-07T18:21:36.122450143Z" } }, "answer": "Omnisend scores 65.8 (B) on agent readiness against Sequenzy's 63.7 (B), and leads in 3 of 7 scored categories. Sequenzy leads on schema \u0026 documentation, security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community.", "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": 504, "ranked": true, "rankOf": 1486, "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-07T18:20:53.811404585Z", "lastOk": true, "lastStatus": 401, "lastMs": 752, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 429, "p95ms24h": 963, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "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-07T18:20:53.811404585Z" } }, "edges": [ { "by": 43, "category": "reliability", "leads": "omnisend", "name": "Reliability", "reasons": { "a": "Graded on the REST API at api.omnisend.com, with the hosted MCP server where a line names MCP. Statuspage at status.omnisend.com with an API component and incident history (20). The history feed's newest incident is still 26 May 2026 on 2 November, so the 90 days from 4 August are clean (30). Rate limits published per endpoint, 400 requests a minute per brand by default and down to 10 a minute and 55 a day for analytics reports (15). A 429 returns a problem document, and some endpoints add `retryAfter` in seconds. No `Retry-After` header, backoff guidance or idempotency keys were found. `POST /contacts` upserts on the email identifier and only a draft campaign can be sent, so a repeated send returns 409 (8). No SLA found, and the terms say scheduled or unscheduled downtime may occur (0). Version 2026-03-15 is the current version, but the Campaigns API definition is labelled `2026-preview` and the changelog announced the Forms API as beta on 24 April 2026, so 8 of 10.", "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": 81, "b": 38 } }, { "by": 39, "category": "maintenance", "leads": "sequenzy", "name": "Maintenance \u0026 community", "reasons": { "a": "The newest dated change to the agent surface is the Content Translations API's `GET /content-translations/languages` operation page, stamped 30 October 2026 and not in the 104-operation index read on 9 October. The MCP reference pages carry 1 September 2026 stamps, and the newest product changelog entry that names the API or MCP is 10 July 2026 (30). The product changelog's newest entries are 1 and 24 September 2026, neither naming the API or MCP, and the docs revisions on 5 August, 26 August and 1 September (per the 9 October check) and the 30 October operation page give one dated API change, not three (0 of 20). A public changelog with a roadmap tab, a support address in the docs and live chat and email support on every plan per the pricing page. No developer forum was found and we saw no reply times (9 of 15). No official SDK was found, and a search of the official MCP registry for Omnisend returned no server on 2 November (0 of 15). No package to assess (0 of 10).", "b": "sequenzy 2.1.56, @sequenzy/mcp 0.0.246 and @sequenzy/cli 0.0.202 were all published on 6 November 2026 (30). 18 SDK, 105 MCP and 93 CLI releases in the 90 days from 8 August, and dated changelog entries on most days (20). A closed service with a public changelog and support answered by the cofounders per the about page. GitHub issues weren't read, as the GitHub API refused our requests for its rate limit (12 of 15). Listed in the official MCP registry as io.github.polnikale/sequenzy-mcp, but the entry is at 0.0.36 against npm's 0.0.246, and the TypeScript SDK is current (10 of 15). MIT packages released daily, the MCP server and CLI still at 0.0.x (6 of 10). Total 78." }, "scores": { "a": 39, "b": 78 } }, { "by": 16, "category": "schema", "leads": "sequenzy", "name": "Schema \u0026 documentation", "reasons": { "a": "Every operation page is served as Markdown with its OpenAPI 3.0.0 definition, security schemes and scopes. No single downloadable OpenAPI file was linked from the pages read, and a Postman collection is linked instead, so 22 of 25. api-docs.omnisend.com/llms.txt indexes the guides and all 105 operation pages as Markdown, one more than on 9 October (10). Descriptions state the purpose, scopes, rate limit and state rules, such as that only a draft campaign can be sent and a sent one must be copied. Few say when not to use an endpoint (15). The two definitions read in full use required fields, enums and typed parameters. The rest were read only as index lines (11). Each operation lists its own 400, 401, 402, 403, 404, 409, 410, 429 and 500 responses with schemas and examples (13). Dated versions in a header and migration guides from versions 3 and 5, but no API changelog. API changes appear only now and then in the product changelog (8).", "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": 79, "b": 95 } }, { "by": 10, "category": "ergonomics", "leads": "omnisend", "name": "Agent ergonomics", "reasons": { "a": "The MCP server lists four tools in front of the 105 operations its docs table names, with `search`, `tool_schema` and `tool_documentation` loaded on demand. We couldn't read the tool definitions without an account, and no field selection was found on the REST API (22 of 25). Cursor pagination with `limit` up to 250, `sort`, `direction` and filters on list endpoints (20). RFC 9457 errors with field-level codes, every validation failure returned at once and a trace ID (20). No idempotency keys. Contact creation upserts on email, a campaign can be sent only from draft, and the MCP docs mark 47 of 105 operations read-only in a table, while the v2 server splits read, create, update and delete into separate tools. Tool annotations were not read (10). List defaults are sensible and two headers are required on every call. No official SDK was found (7).", "b": "The MCP tool reference lists about 306 tools, the over-30 band, and no toolsets, tool search or dynamic loading was found (5 of 25). List endpoints paginate and filter, and contact timelines use cursors (20). Errors carry a code, a human message, a fix and a docs link, with `retryAfterSeconds` when the API sent Retry-After (20). Idempotency keys on sends and event imports; MCP readOnlyHint and destructiveHint annotations weren't found in the published reference (14 of 20). Sensible defaults with a selected workspace; one official SDK (TypeScript) plus a CLI (10 of 15). Total 69." }, "scores": { "a": 79, "b": 69 } }, { "by": 10, "category": "security", "leads": "sequenzy", "name": "Security \u0026 auth", "reasons": { "a": "API keys are named, shown once and sent in a header. OAuth uses the authorisation code grant with per-resource read and write scopes, but credentials need a request form, no PKCE is documented and the token in the docs never expires unless revoked. The MCP server uses OAuth with dynamic client registration. Whether an API key can be scoped or rotated was not found (22). The MCP consent screen sets an access level with a read-only preset, and scopes split read from write. No approval or confirmation step before a campaign send was found, and the terms put approval of each agent action on the customer (13). The MCP docs warn against enabling two brand connectors in one chat and advise read-only access. No guidance on untrusted content in contact or form data was found (4). The app records API errors under API Issues. No log of successful calls or audit log endpoint was found (6). security.txt names a contact and a bug bounty policy whose scope includes api.omnisend.com, and the DPA states annual third-party penetration tests. No SOC 2 or ISO 27001 statement was found on the pages read (12).", "b": "Workspace and account API keys with fine-grained permission scopes, presets and explicit `*:delete` rights, revocable in settings, plus an OAuth `service_auth` flow for agents with user confirmation (30). Read-only and drafts-only presets let an agent prepare mail without sending, and account keys keep the user's workspace role (20). The agent inbox and reply tracking give the agent inbound mail, and no prompt-injection guidance was found in the MCP, permissions or inbox docs (4 of 15). The DPA lists administrative audit logs and MCP events report replies and bounces; no per-call API log for the customer was found (8 of 15). A responsible disclosure address on the security page, no security.txt (404), bug bounty or certification (5 of 20). Total 67." }, "scores": { "a": 57, "b": 67 } }, { "by": 10, "category": "payments", "leads": "sequenzy", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 in the API documentation or the pricing page. The 402 on the send campaign endpoint is a plan payment error (0). Plan prices are public and scale with contacts through a slider, with Standard at 500 contacts and Pro at 2,500 contacts shown at a three-month discount. Nothing is priced per API call (10). The Free plan has 250 contacts and 500 emails a month, and the page says no credit card is required (20). A person has to sign up in a browser and create a key or approve OAuth (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": 30, "b": 40 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Omnisend, UAB", "b": "Nic Tech Solutions, LLC", "name": "Vendor" }, { "a": "https://api.omnisend.com/api", "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": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Omnisend's Terms of Use", "b": "none", "name": "Licence" }, { "a": "4", "b": "306", "name": "Tools exposed" }, { "a": "yes", "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-30", "b": "2026-11-06", "name": "Last release" }, { "a": "2026-04-30", "b": "2026-06-30", "name": "Terms last updated" }, { "a": "2026-06-18", "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": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "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.8/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Omnisend scores 65.8 (B) on agent readiness against Sequenzy's 63.7 (B), and leads in 3 of 7 scored categories. Sequenzy leads on schema \u0026 documentation, security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Omnisend or Sequenzy?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Omnisend and Sequenzy need an API key?" }, { "answer": "Yes. Omnisend has a hosted endpoint at https://api.omnisend.com/api and Sequenzy at https://api.sequenzy.com/v1/mcp.", "question": "Can an agent call Omnisend and Sequenzy without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 81 against 38", "Agent ergonomics, 79 against 69", "Transparency \u0026 trust, 77 against 67" ], "also": null, "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" }, { "aheadOn": [ "Schema \u0026 documentation, 95 against 79", "Security \u0026 auth, 67 against 57", "Payments \u0026 pricing, 40 against 30", "Maintenance \u0026 community, 78 against 39" ], "also": [ "Runs on your own machine" ], "goodFor": "SaaS and ecommerce lifecycle email run from code or an agent, with billing-event triggers from Stripe, Paddle and others.", "slug": "sequenzy", "watchFor": "About 306 MCP tools, with no toolsets or dynamic loading found" } ], "history": { "omnisend": [ { "causes": [ "product" ], "date": "2026-11-02", "delta": 0.9, "from": 64.9, "fromGrade": "B", "to": 65.8, "toGrade": "B" } ], "sequenzy": null }, "job": { "capability": "marketing.profiles", "name": "Marketing audiences" }, "others": [ { "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/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-omnisend.json", "title": "Braze vs Omnisend", "url": "https://www.anchorterminal.com/compare/braze-vs-omnisend" }, { "json": "https://www.anchorterminal.com/compare/braze-vs-sequenzy.json", "title": "Braze vs Sequenzy", "url": "https://www.anchorterminal.com/compare/braze-vs-sequenzy" }, { "json": "https://www.anchorterminal.com/compare/clevertap-vs-omnisend.json", "title": "CleverTap vs Omnisend", "url": "https://www.anchorterminal.com/compare/clevertap-vs-omnisend" }, { "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-omnisend.json", "title": "Customer.io vs Omnisend", "url": "https://www.anchorterminal.com/compare/customer-io-vs-omnisend" }, { "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-omnisend.json", "title": "Iterable vs Omnisend", "url": "https://www.anchorterminal.com/compare/iterable-vs-omnisend" }, { "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-omnisend.json", "title": "Klaviyo API + MCP vs Omnisend", "url": "https://www.anchorterminal.com/compare/klaviyo-vs-omnisend" }, { "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-omnisend.json", "title": "Mailchimp Marketing API vs Omnisend", "url": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-omnisend" }, { "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-omnisend.json", "title": "MoEngage vs Omnisend", "url": "https://www.anchorterminal.com/compare/moengage-vs-omnisend" }, { "json": "https://www.anchorterminal.com/compare/moengage-vs-sequenzy.json", "title": "MoEngage vs Sequenzy", "url": "https://www.anchorterminal.com/compare/moengage-vs-sequenzy" }, { "json": "https://www.anchorterminal.com/compare/nitrosend-vs-omnisend.json", "title": "Nitrosend vs Omnisend", "url": "https://www.anchorterminal.com/compare/nitrosend-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/dreamlit-vs-omnisend.json", "title": "Dreamlit vs Omnisend", "url": "https://www.anchorterminal.com/compare/dreamlit-vs-omnisend" }, { "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": 43, "edge": "omnisend", "key": "reliability", "name": "Reliability", "omnisend": 81, "sequenzy": 38, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 16, "edge": "sequenzy", "key": "schema", "name": "Schema \u0026 documentation", "omnisend": 79, "sequenzy": 95, "weight": 13 }, { "by": 10, "edge": "omnisend", "key": "ergonomics", "name": "Agent ergonomics", "omnisend": 79, "sequenzy": 69, "weight": 13 }, { "by": 10, "edge": "sequenzy", "key": "security", "name": "Security \u0026 auth", "omnisend": 57, "sequenzy": 67, "weight": 14 }, { "by": 10, "edge": "sequenzy", "key": "payments", "name": "Payments \u0026 pricing", "omnisend": 30, "sequenzy": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 39, "edge": "sequenzy", "key": "maintenance", "name": "Maintenance \u0026 community", "omnisend": 39, "sequenzy": 78, "weight": 7 }, { "by": 10, "edge": "omnisend", "key": "transparency", "name": "Transparency \u0026 trust", "omnisend": 77, "sequenzy": 67, "weight": 7 } ], "summary": "Omnisend scores 65.8 (B) on agent readiness against Sequenzy's 63.7 (B), and leads in 3 of 7 scored categories. Sequenzy leads on schema \u0026 documentation, security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community. Both do marketing audiences.", "tasks": null, "tutorials": [], "verdicts": { "omnisend": "The API documents 105 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.", "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/omnisend-vs-sequenzy", "json": "https://www.anchorterminal.com/compare/omnisend-vs-sequenzy.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/omnisend-vs-sequenzy.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/omnisend-vs-sequenzy.min.md" }, "markdown": "Omnisend scores 65.8 (B) on agent readiness against Sequenzy's 63.7 (B), and leads in 3 of 7 scored categories. Sequenzy leads on schema \u0026 documentation, security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community. Both do marketing audiences.\n\n- Omnisend: grade B, 65.8/100, rank #398 of 1486. Markdown https://www.anchorterminal.com/tools/omnisend.md · JSON https://www.anchorterminal.com/api/v1/tools/omnisend.json\n- Sequenzy: grade B, 63.7/100, rank #504 of 1486. 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### 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 38\n- Agent ergonomics, 79 against 69\n- Transparency \u0026 trust, 77 against 67\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### 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 79\n- Security \u0026 auth, 67 against 57\n- Payments \u0026 pricing, 40 against 30\n- Maintenance \u0026 community, 78 against 39\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: About 306 MCP tools, with no toolsets or dynamic loading found\n\n\n## Why the edge\n\n### Reliability: Omnisend +43\n\n- Omnisend (81): Graded on the REST API at api.omnisend.com, with the hosted MCP server where a line names MCP. Statuspage at status.omnisend.com with an API component and incident history (20). The history feed's newest incident is still 26 May 2026 on 2 November, so the 90 days from 4 August are clean (30). Rate limits published per endpoint, 400 requests a minute per brand by default and down to 10 a minute and 55 a day for analytics reports (15). A 429 returns a problem document, and some endpoints add `retryAfter` in seconds. No `Retry-After` header, backoff guidance or idempotency keys were found. `POST /contacts` upserts on the email identifier and only a draft campaign can be sent, so a repeated send returns 409 (8). No SLA found, and the terms say scheduled or unscheduled downtime may occur (0). Version 2026-03-15 is the current version, but the Campaigns API definition is labelled `2026-preview` and the changelog announced the Forms API as beta on 24 April 2026, so 8 of 10.\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### Maintenance \u0026 community: Sequenzy +39\n\n- Omnisend (39): The newest dated change to the agent surface is the Content Translations API's `GET /content-translations/languages` operation page, stamped 30 October 2026 and not in the 104-operation index read on 9 October. The MCP reference pages carry 1 September 2026 stamps, and the newest product changelog entry that names the API or MCP is 10 July 2026 (30). The product changelog's newest entries are 1 and 24 September 2026, neither naming the API or MCP, and the docs revisions on 5 August, 26 August and 1 September (per the 9 October check) and the 30 October operation page give one dated API change, not three (0 of 20). A public changelog with a roadmap tab, a support address in the docs and live chat and email support on every plan per the pricing page. No developer forum was found and we saw no reply times (9 of 15). No official SDK was found, and a search of the official MCP registry for Omnisend returned no server on 2 November (0 of 15). No package to assess (0 of 10).\n- Sequenzy (78): sequenzy 2.1.56, @sequenzy/mcp 0.0.246 and @sequenzy/cli 0.0.202 were all published on 6 November 2026 (30). 18 SDK, 105 MCP and 93 CLI releases in the 90 days from 8 August, and dated changelog entries on most days (20). A closed service with a public changelog and support answered by the cofounders per the about page. GitHub issues weren't read, as the GitHub API refused our requests for its rate limit (12 of 15). Listed in the official MCP registry as io.github.polnikale/sequenzy-mcp, but the entry is at 0.0.36 against npm's 0.0.246, and the TypeScript SDK is current (10 of 15). MIT packages released daily, the MCP server and CLI still at 0.0.x (6 of 10). Total 78.\n\n### Schema \u0026 documentation: Sequenzy +16\n\n- Omnisend (79): Every operation page is served as Markdown with its OpenAPI 3.0.0 definition, security schemes and scopes. No single downloadable OpenAPI file was linked from the pages read, and a Postman collection is linked instead, so 22 of 25. api-docs.omnisend.com/llms.txt indexes the guides and all 105 operation pages as Markdown, one more than on 9 October (10). Descriptions state the purpose, scopes, rate limit and state rules, such as that only a draft campaign can be sent and a sent one must be copied. Few say when not to use an endpoint (15). The two definitions read in full use required fields, enums and typed parameters. The rest were read only as index lines (11). Each operation lists its own 400, 401, 402, 403, 404, 409, 410, 429 and 500 responses with schemas and examples (13). Dated versions in a header and migration guides from versions 3 and 5, but no API changelog. API changes appear only now and then in the product changelog (8).\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### Agent ergonomics: Omnisend +10\n\n- Omnisend (79): The MCP server lists four tools in front of the 105 operations its docs table names, with `search`, `tool_schema` and `tool_documentation` loaded on demand. We couldn't read the tool definitions without an account, and no field selection was found on the REST API (22 of 25). Cursor pagination with `limit` up to 250, `sort`, `direction` and filters on list endpoints (20). RFC 9457 errors with field-level codes, every validation failure returned at once and a trace ID (20). No idempotency keys. Contact creation upserts on email, a campaign can be sent only from draft, and the MCP docs mark 47 of 105 operations read-only in a table, while the v2 server splits read, create, update and delete into separate tools. Tool annotations were not read (10). List defaults are sensible and two headers are required on every call. No official SDK was found (7).\n- Sequenzy (69): The MCP tool reference lists about 306 tools, the over-30 band, and no toolsets, tool search or dynamic loading was found (5 of 25). List endpoints paginate and filter, and contact timelines use cursors (20). Errors carry a code, a human message, a fix and a docs link, with `retryAfterSeconds` when the API sent Retry-After (20). Idempotency keys on sends and event imports; MCP readOnlyHint and destructiveHint annotations weren't found in the published reference (14 of 20). Sensible defaults with a selected workspace; one official SDK (TypeScript) plus a CLI (10 of 15). Total 69.\n\n### Security \u0026 auth: Sequenzy +10\n\n- Omnisend (57): API keys are named, shown once and sent in a header. OAuth uses the authorisation code grant with per-resource read and write scopes, but credentials need a request form, no PKCE is documented and the token in the docs never expires unless revoked. The MCP server uses OAuth with dynamic client registration. Whether an API key can be scoped or rotated was not found (22). The MCP consent screen sets an access level with a read-only preset, and scopes split read from write. No approval or confirmation step before a campaign send was found, and the terms put approval of each agent action on the customer (13). The MCP docs warn against enabling two brand connectors in one chat and advise read-only access. No guidance on untrusted content in contact or form data was found (4). The app records API errors under API Issues. No log of successful calls or audit log endpoint was found (6). security.txt names a contact and a bug bounty policy whose scope includes api.omnisend.com, and the DPA states annual third-party penetration tests. No SOC 2 or ISO 27001 statement was found on the pages read (12).\n- Sequenzy (67): Workspace and account API keys with fine-grained permission scopes, presets and explicit `*:delete` rights, revocable in settings, plus an OAuth `service_auth` flow for agents with user confirmation (30). Read-only and drafts-only presets let an agent prepare mail without sending, and account keys keep the user's workspace role (20). The agent inbox and reply tracking give the agent inbound mail, and no prompt-injection guidance was found in the MCP, permissions or inbox docs (4 of 15). The DPA lists administrative audit logs and MCP events report replies and bounces; no per-call API log for the customer was found (8 of 15). A responsible disclosure address on the security page, no security.txt (404), bug bounty or certification (5 of 20). Total 67.\n\n### Payments \u0026 pricing: Sequenzy +10\n\n- Omnisend (30): No x402, MPP or L402 in the API documentation or the pricing page. The 402 on the send campaign endpoint is a plan payment error (0). Plan prices are public and scale with contacts through a slider, with Standard at 500 contacts and Pro at 2,500 contacts shown at a three-month discount. Nothing is priced per API call (10). The Free plan has 250 contacts and 500 emails a month, and the page says no credit card is required (20). A person has to sign up in a browser and create a key or approve OAuth (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## Score by category\n\n| Category | Weight | Omnisend | Sequenzy | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 81 | 38 | Omnisend +43 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 79 | 95 | Sequenzy +16 |\n| Agent ergonomics | 13% (16.2 this run) | 79 | 69 | Omnisend +10 |\n| Security \u0026 auth | 14% (17.5 this run) | 57 | 67 | Sequenzy +10 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 40 | Sequenzy +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 39 | 78 | Sequenzy +39 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 67 | Omnisend +10 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **65.8 · B** | **63.7 · B** | |\n\n## Facts side by side\n\n| Fact | Omnisend | Sequenzy |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Omnisend, UAB | Nic Tech Solutions, LLC |\n| Hosted endpoint | `https://api.omnisend.com/api` | `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 | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under Omnisend's Terms of Use | none |\n| Tools exposed | 4 | 306 |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.polnikale/sequenzy-mcp` |\n| Last release | 2026-10-30 | 2026-11-06 |\n| Terms last updated | 2026-04-30 | 2026-06-30 |\n| Privacy policy last updated | 2026-06-18 | 2026-09-16 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | 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.8/5 (4) | none |\n\n## How the scores have moved\n\n### Omnisend\n\n- +0.9 on 2 November 2026: product\n\n### Sequenzy\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Omnisend.** The API documents 105 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**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### 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### 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, Omnisend or Sequenzy?\n\nOmnisend scores 65.8 (B) on agent readiness against Sequenzy's 63.7 (B), and leads in 3 of 7 scored categories. Sequenzy leads on schema \u0026 documentation, security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community.\n\n### Do Omnisend and Sequenzy need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Omnisend and Sequenzy without installing anything?\n\nYes. Omnisend has a hosted endpoint at https://api.omnisend.com/api 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/omnisend-vs-sequenzy.json, and with the fewest tokens: https://www.anchorterminal.com/compare/omnisend-vs-sequenzy.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"omnisend\", \"b\": \"sequenzy\"}`. From a terminal: `anchor compare omnisend sequenzy`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/omnisend.json and https://www.anchorterminal.com/api/v1/tools/sequenzy.json\n\n## Other comparisons with Omnisend or Sequenzy\n\n- [ActiveCampaign vs Omnisend](https://www.anchorterminal.com/compare/activecampaign-vs-omnisend.md)\n- [ActiveCampaign vs Sequenzy](https://www.anchorterminal.com/compare/activecampaign-vs-sequenzy.md)\n- [Braze vs Omnisend](https://www.anchorterminal.com/compare/braze-vs-omnisend.md)\n- [Braze vs Sequenzy](https://www.anchorterminal.com/compare/braze-vs-sequenzy.md)\n- [CleverTap vs Omnisend](https://www.anchorterminal.com/compare/clevertap-vs-omnisend.md)\n- [CleverTap vs Sequenzy](https://www.anchorterminal.com/compare/clevertap-vs-sequenzy.md)\n- [Customer.io vs Omnisend](https://www.anchorterminal.com/compare/customer-io-vs-omnisend.md)\n- [Customer.io vs Sequenzy](https://www.anchorterminal.com/compare/customer-io-vs-sequenzy.md)\n- [Iterable vs Omnisend](https://www.anchorterminal.com/compare/iterable-vs-omnisend.md)\n- [Iterable vs Sequenzy](https://www.anchorterminal.com/compare/iterable-vs-sequenzy.md)\n- [Klaviyo API + MCP vs Omnisend](https://www.anchorterminal.com/compare/klaviyo-vs-omnisend.md)\n- [Klaviyo API + MCP vs Sequenzy](https://www.anchorterminal.com/compare/klaviyo-vs-sequenzy.md)\n- [Mailchimp Marketing API vs Omnisend](https://www.anchorterminal.com/compare/mailchimp-marketing-vs-omnisend.md)\n- [Mailchimp Marketing API vs Sequenzy](https://www.anchorterminal.com/compare/mailchimp-marketing-vs-sequenzy.md)\n- [MoEngage vs Omnisend](https://www.anchorterminal.com/compare/moengage-vs-omnisend.md)\n- [MoEngage vs Sequenzy](https://www.anchorterminal.com/compare/moengage-vs-sequenzy.md)\n- [Nitrosend vs Omnisend](https://www.anchorterminal.com/compare/nitrosend-vs-omnisend.md)\n- [Nitrosend vs Sequenzy](https://www.anchorterminal.com/compare/nitrosend-vs-sequenzy.md)\n- [Dreamlit vs Omnisend](https://www.anchorterminal.com/compare/dreamlit-vs-omnisend.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": "Omnisend vs Sequenzy", "url": "" } ], "description": "Omnisend scores 65.8 (B) to Sequenzy's 63.7 (B) for marketing audiences. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Omnisend B 65.8", "Sequenzy B 63.7", "scores" ], "h1": "Omnisend vs Sequenzy", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/omnisend-vs-sequenzy", "published": "2026-10-01", "section": "tools", "title": "Omnisend vs Sequenzy for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/omnisend-vs-sequenzy" }, "tokens": { "markdown": 4950, "slim": 3080 }, "version": 1 }