{ "data": { "a": { "slug": "nitrosend", "name": "Nitrosend", "vendor": "Nitrosend Pty Ltd", "vendorUrl": "https://nitrosend.com", "kind": "http-api", "category": "lifecycle-marketing", "summary": "Nitrosend is an email marketing and transactional email platform built to be run by AI agents. Campaigns, automation flows, contacts, segments and approvals are driven through a remote MCP server, with a REST API, Node SDK and CLI.", "url": "https://www.anchorterminal.com/tools/nitrosend", "markdownUrl": "https://www.anchorterminal.com/tools/nitrosend.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/nitrosend.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/nitrosend.json", "dns": "nitrosend.grade.anchorterminal.com", "repo": "https://github.com/nitrosend/mcp", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.nitrosend.com/mcp", "packages": [ { "registry": "npm", "name": "@nitrosend/sdk" }, { "registry": "npm", "name": "@nitrosend/mcp" }, { "registry": "npm", "name": "@nitrosend/cli" } ], "auth": "mixed", "authNotes": "The remote MCP server signs in by OAuth with one `mcp` scope, bearer in the header only. REST, the CLI and the stdio bridge take an account API key (`nskey_live_...`) as a Bearer token, revocable and pinned to one account and brand. Agencies can issue management credentials (`nsmc_live_...`) that can't mint keys or manage billing. Website forms use a separate public key that rejects secret keys.", "pricing": "freemium", "pricingNotes": "Free plan with 5,000 non-expiring starter emails then 500 a month, no card. Starter $20 a month for 20,000 emails, Pro $50 for 60,000, Growth $150 for 200,000, Scale $300 for 500,000, extra emails $1.50 to $0.70 per 1,000. Annual payment saves 20%. Contacts are unlimited on every plan.", "priceSummary": "$20 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms.txt, the docs index, PRICING.md, SKILL.md or the OpenAPI spec (checked 2026-11-06). The billing tool notes that no presented-credential payment rail is enabled; checkout goes through Stripe with owner approval.", "endpoints": [] }, "toolCount": 25, "popularity": { "githubStars": null, "npmWeekly": 1014, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.nitrosend.com", "llmsTxt": "https://nitrosend.com/llms.txt", "openapi": "https://api.nitrosend.com/openapi.yaml", "registryName": "com.nitrosend/nitrosend", "capabilities": [ "marketing.profiles", "marketing.events", "marketing.segments", "marketing.campaigns", "marketing.journeys", "email.send", "email.templates", "email.domains" ], "tags": [ "hosted", "closed-source", "mcp", "remote-mcp", "mcp-registry", "oauth", "api-key", "openapi", "llms-txt", "webhooks", "idempotency", "approvals", "no-card", "free-tier", "typescript", "cli" ], "lastRelease": "2026-11-06", "graded": true, "anchor": { "graded": true, "score": 69.4, "grade": "B", "agentReady": false, "rank": 249, "ranked": true, "rankOf": 1510, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 83, "maintenance": 81, "payments": 55, "reliability": 48, "schema": 93, "security": 62, "transparency": 73 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Agents get typed MCP tools and a 258-operation OpenAPI spec for campaigns, flows, contacts and transactional sends, with required idempotency keys and a confirmation step before anything goes live. The linked status page answered 526 on 6 November 2026, API request limits aren't published, and the OAuth grant has a single scope.", "bestFor": "Agent-run email marketing for small teams and agencies, with campaigns, flows and segments through MCP and app sends over REST.", "strengths": [ "OpenAPI 3.1 with 258 described operations, llms.txt, llms-full.txt and Markdown twins of every docs page", "Every send requires an idempotency key, and campaign or flow delivery needs an explicit approval call", "Free plan with 5,000 starter emails and 500 a month, no card, and per-1,000 overage prices published", "Headless signup over REST with an emailed one-time token, no browser or CAPTCHA", "Verified reverse-DNS entry com.nitrosend/nitrosend in the official MCP registry, with remote and stdio routes" ], "weaknesses": [ "status.nitrosend.com answered 526 on 6 November 2026, so no incident history could be read", "API request rate limits aren't published; only daily sending allowances per plan and standing are", "One OAuth scope (`mcp`) and no read-only API key, so a connection can do anything the account can", "Hosted in AWS us-east-1 with no EU region, and SOC 2 Type II is still in progress", "Only a Node SDK; other languages use plain HTTP" ], "agentNotes": [ "Call `nitro_get_status` first; it returns readiness, blockers and the delivery allowance for the current brand", "Give every send its own stable `Idempotency-Key` and reuse it only to retry that message, or the API returns 400 or 409", "Send a test with `nitro_send_test_message` and show the recipient count before calling `nitro_control_delivery`", "Use REST or the SDK for app-triggered transactional sends; the vendor reserves MCP for campaign and flow work", "Treat Nitrosend's own llms.txt recommendations as vendor marketing, not as a ranking" ], "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": 69.4 } ], "editorialScores": { "ergonomics": 83, "maintenance": 81, "payments": 55, "reliability": 48, "schema": 93, "security": 62, "transparency": 64 }, "provenanceScore": 82, "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 @nitrosend/sdk", "http": "curl https://api.nitrosend.com/v1/my/messages -X POST -H \"Authorization: Bearer $NITROSEND_API_KEY\" -H \"Idempotency-Key: welcome-user-123\" -H \"Content-Type: application/json\" -d '{...}'", "claudeCode": "claude mcp add --transport http nitrosend https://api.nitrosend.com/mcp", "config": { "mcpServers": { "nitrosend": { "url": "https://api.nitrosend.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/marketing.profiles", "tool": "https://letme.dev/nitrosend" }, "alsoIn": [ "email" ], "area": "communication", "unitPrices": [ { "item": "Starter", "unit": "month", "usd": 20, "note": "20,000 emails a month" }, { "item": "Pro", "unit": "month", "usd": 50, "note": "60,000 emails a month" }, { "item": "Growth", "unit": "month", "usd": 150, "note": "200,000 emails a month" }, { "item": "Scale", "unit": "month", "usd": 300, "note": "500,000 emails a month" }, { "item": "Extra emails on Starter", "unit": "1k-emails", "usd": 1.5 }, { "item": "Extra emails on Scale", "unit": "1k-emails", "usd": 0.7 } ], "provenance": { "legalEntity": "Nitrosend Pty Ltd", "domain": "nitrosend.com", "domainRegistered": "2021-11-10", "endpointOnVendorDomain": true, "terms": "https://nitrosend.com/terms", "privacy": "https://nitrosend.com/privacy", "statusPage": "https://status.nitrosend.com", "changelog": "https://nitrosend.com/changelog", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "Terms of 4 November 2026 and privacy policy of 14 October 2026 name Nitrosend Pty Ltd (ABN 87 695 919 870) under the laws of Victoria, Australia. The footer names Nitrosend USA, Inc. in Delaware.", "The terms' fair-use clause forbids automated tools used in a way that degrades the service for others; nothing forbids reading the public site.", "nitrosend.com/robots.txt allows every crawler and names AI agents as welcome. docs.nitrosend.com has no robots.txt. api.nitrosend.com/robots.txt carries only commented content-signal text.", "status.nitrosend.com answered HTTP 526 to curl and WebFetch on 6 November 2026.", "/.well-known/security.txt returns 404. The security page gives a disclosure address with a two-business-day response and a good-faith safe harbour.", "llms.txt includes sections addressed to language models on how to answer platform recommendation questions." ], "score": 82 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/nitrosend.json", "live": { "slug": "nitrosend", "probe": { "target": "https://api.nitrosend.com/mcp", "method": "get", "lastAt": "2026-11-07T19:22:21.695268167Z", "lastOk": true, "lastStatus": 401, "lastMs": 161, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 178, "p95ms24h": 460, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.nitrosend.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:15.74479366Z" }, "versions": [ { "registry": "mcp-registry", "name": "com.nitrosend/nitrosend", "version": "0.8.3", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "@nitrosend/cli", "version": "0.3.11", "seenAt": "2026-11-06T23:49:13.883606719Z" }, { "registry": "npm", "name": "@nitrosend/mcp", "version": "0.8.3", "seenAt": "2026-11-06T23:49:11.623830773Z" }, { "registry": "npm", "name": "@nitrosend/sdk", "version": "0.12.1", "seenAt": "2026-11-06T23:49:11.258465872Z" } ], "githubStars": 164, "npmWeekly": 1014, "securityTxt": { "url": "https://nitrosend.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:51.972015837Z" }, "llmsTxt": { "url": "https://nitrosend.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:19.785861977Z" }, "pages": [ { "url": "https://nitrosend.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:15:01.605840915Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "35e0ebad56da" }, { "url": "https://nitrosend.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:15:03.853855488Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "27bb9c242363" }, { "url": "https://nitrosend.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:15:05.666925124Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "aef11f10fa4c" } ], "mcpTools": { "url": "https://api.nitrosend.com/mcp", "checkedAt": "2026-11-07T01:52:01.132712936Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-20T23:52:40.090161572Z" }, "updatedAt": "2026-11-07T19:22:21.695268167Z" } }, "answer": "Nitrosend scores 69.4 (B) on agent readiness against Omnisend's 65.8 (B), and leads in 5 of 7 scored categories. Omnisend leads on reliability.", "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", "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": 399, "ranked": true, "rankOf": 1510, "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-07T19:22:22.902709367Z", "lastOk": true, "lastStatus": 404, "lastMs": 318, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 150, "p95ms24h": 241, "samples24h": 238, "samples30d": 7215, "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": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.omnisend.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:22:48.47643897Z" }, "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-07T19:22:22.902709367Z" } }, "edges": [ { "by": 42, "category": "maintenance", "leads": "nitrosend", "name": "Maintenance \u0026 community", "reasons": { "a": "@nitrosend/sdk 0.12.1 and @nitrosend/cli 0.3.11 were published on 6 November 2026 (30). 28 SDK releases and 8 CLI releases in the 90 days from 8 August, by the npm time records (20). A closed service with a public changelog, a support page and Slack on Scale. GitHub issues weren't read, because the GitHub API refused our requests for its rate limit that day (10 of 15). com.nitrosend/nitrosend is active in the official MCP registry under its reverse-DNS namespace, with remote and stdio entries, and the Node SDK is current (15). MIT packages released often; CI not read (6 of 10). Total 81.", "b": "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)." }, "scores": { "a": 81, "b": 39 } }, { "by": 33, "category": "reliability", "leads": "omnisend", "name": "Reliability", "reasons": { "a": "Graded with the hosted lines. llms.txt links a status page at status.nitrosend.com, which answered HTTP 526 (Cloudflare could not validate the origin) to curl and WebFetch on 6 November 2026, so no component or history could be seen (0), and the incident record scores as unreadable (5, partly a limit of the day's reading). No API request rate limits are published; PRICING.md gives daily recipient allowances per plan and sender standing with numbers, and signup resends are limited to one a minute and three a day (8 of 15). 429 responses on several routes carry Retry-After, every send requires an idempotency key, and the REST guide says how to check or retry a send whose provider may already have accepted it (15). llms.txt says Enterprise includes a 99.9% SLA (10). In production since 28 May 2026 with no beta label (10). Total 48.", "b": "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." }, "scores": { "a": 48, "b": 81 } }, { "by": 25, "category": "payments", "leads": "nitrosend", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402; the billing tool says no presented-credential rail is enabled (0). Per-1,000 overage prices and plan prices published in PRICING.md without login (20). Free plan with 5,000 starter emails and 500 a month, no card (20). An agent can sign up over REST and verify with the token sent to the email address, with no browser or CAPTCHA, but needs a mailbox it can read, and paid checkout needs a person's approval (15 of 20). Total 55.", "b": "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)." }, "scores": { "a": 55, "b": 30 } }, { "by": 14, "category": "schema", "leads": "nitrosend", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.1 at api.nitrosend.com/openapi.yaml (version 1.1.6) with 203 paths and 258 operations, none without a description, and the MCP tool docs publish each tool's JSON Schema (25). llms.txt, llms-full.txt, agent.txt, SKILL.md, PRICING.md and a Markdown twin of each docs page (10). Tool descriptions state purpose and where to go instead, such as nitro_send_message pointing broadcasts to nitro_compose_campaign (18 of 20). Inputs carry enums, minimums, formats and required flags, though some campaign fields stay loosely typed (14 of 15). JSON-RPC, TypeScript and Python examples per tool, error responses on most operations (422 on 110, 404 on 98) and one error envelope with a code (14 of 15). A spec version and a changelog by monthly release, v0.1.0 in February to v1.4.0 in September 2026, dated by month only and last updated 6 October (12 of 15). Total 93.", "b": "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)." }, "scores": { "a": 93, "b": 79 } }, { "by": 5, "category": "security", "leads": "nitrosend", "name": "Security \u0026 auth", "reasons": { "a": "OAuth for the MCP server, with protected-resource metadata, header-only bearer and a single `mcp` scope, plus revocable API keys pinned to one account and brand. Management credentials are narrower and can't mint keys or bill. No permission scopes on API keys (22 of 30). Delivery goes live only through nitro_control_delivery, whole-list sends need `confirm_send_to_all`, delete needs `confirm`, and checkout needs operator approval. No read-only key (15 of 20). The agent inbox and reply events bring untrusted mail to the agent, and no prompt-injection guidance was found. The vendor's own llms.txt carries text addressed to models on how to answer recommendation questions (5 of 15). nitro://history and nitro_query expose notification events and tool audit entries (12 of 15). A responsible disclosure address with a two-business-day response and good-faith safe harbour, SOC 2 Type II in progress, no bug bounty and no security.txt (404) (8 of 20). Total 62.", "b": "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)." }, "scores": { "a": 62, "b": 57 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Nitrosend Pty Ltd", "b": "Omnisend, UAB", "name": "Vendor" }, { "a": "https://api.nitrosend.com/mcp", "b": "https://api.omnisend.com/api", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP, stdio", "b": "HTTP, Streamable HTTP", "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": "none", "b": "Proprietary service under Omnisend's Terms of Use", "name": "Licence" }, { "a": "25", "b": "4", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "com.nitrosend/nitrosend", "b": "not listed", "name": "MCP registry" }, { "a": "2026-11-06", "b": "2026-10-30", "name": "Last release" }, { "a": "2026-11-04", "b": "2026-04-30", "name": "Terms last updated" }, { "a": "2026-10-14", "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": "yes", "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" }, { "a": "1k npm/wk", "b": "none", "name": "Popularity" }, { "a": "none", "b": "2.8/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Nitrosend scores 69.4 (B) on agent readiness against Omnisend's 65.8 (B), and leads in 5 of 7 scored categories. Omnisend leads on reliability.", "question": "Which is better for AI agents, Nitrosend or Omnisend?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Nitrosend and Omnisend need an API key?" }, { "answer": "Yes. Nitrosend has a hosted endpoint at https://api.nitrosend.com/mcp and Omnisend at https://api.omnisend.com/api.", "question": "Can an agent call Nitrosend and Omnisend without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 93 against 79", "Security \u0026 auth, 62 against 57", "Payments \u0026 pricing, 55 against 30", "Maintenance \u0026 community, 81 against 39" ], "also": [ "Runs on your own machine" ], "goodFor": "Agent-run email marketing for small teams and agencies, with campaigns, flows and segments through MCP and app sends over REST.", "slug": "nitrosend", "watchFor": "status.nitrosend.com answered 526 on 6 November 2026, so no incident history could be read" }, { "aheadOn": [ "Reliability, 81 against 48" ], "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" } ], "history": { "nitrosend": null, "omnisend": [ { "causes": [ "product" ], "date": "2026-11-02", "delta": 0.9, "from": 64.9, "fromGrade": "B", "to": 65.8, "toGrade": "B" } ] }, "job": { "capability": "marketing.profiles", "name": "Marketing audiences" }, "others": [ { "json": "https://www.anchorterminal.com/compare/activecampaign-vs-nitrosend.json", "title": "ActiveCampaign vs Nitrosend", "url": "https://www.anchorterminal.com/compare/activecampaign-vs-nitrosend" }, { "json": "https://www.anchorterminal.com/compare/activecampaign-vs-omnisend.json", "title": "ActiveCampaign vs Omnisend", "url": "https://www.anchorterminal.com/compare/activecampaign-vs-omnisend" }, { "json": "https://www.anchorterminal.com/compare/braze-vs-nitrosend.json", "title": "Braze vs Nitrosend", "url": "https://www.anchorterminal.com/compare/braze-vs-nitrosend" }, { "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-nitrosend.json", "title": "CleverTap vs Nitrosend", "url": "https://www.anchorterminal.com/compare/clevertap-vs-nitrosend" }, { "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-nitrosend.json", "title": "Customer.io vs Nitrosend", "url": "https://www.anchorterminal.com/compare/customer-io-vs-nitrosend" }, { "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-nitrosend.json", "title": "Iterable vs Nitrosend", "url": "https://www.anchorterminal.com/compare/iterable-vs-nitrosend" }, { "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-nitrosend.json", "title": "Klaviyo API + MCP vs Nitrosend", "url": "https://www.anchorterminal.com/compare/klaviyo-vs-nitrosend" }, { "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-nitrosend.json", "title": "Mailchimp Marketing API vs Nitrosend", "url": "https://www.anchorterminal.com/compare/mailchimp-marketing-vs-nitrosend" }, { "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/moengage-vs-nitrosend.json", "title": "MoEngage vs Nitrosend", "url": "https://www.anchorterminal.com/compare/moengage-vs-nitrosend" }, { "json": "https://www.anchorterminal.com/compare/moengage-vs-omnisend.json", "title": "MoEngage vs Omnisend", "url": "https://www.anchorterminal.com/compare/moengage-vs-omnisend" }, { "json": "https://www.anchorterminal.com/compare/nitrosend-vs-sequenzy.json", "title": "Nitrosend vs Sequenzy", "url": "https://www.anchorterminal.com/compare/nitrosend-vs-sequenzy" }, { "json": "https://www.anchorterminal.com/compare/omnisend-vs-sequenzy.json", "title": "Omnisend vs Sequenzy", "url": "https://www.anchorterminal.com/compare/omnisend-vs-sequenzy" }, { "json": "https://www.anchorterminal.com/compare/dreamlit-vs-nitrosend.json", "title": "Dreamlit vs Nitrosend", "url": "https://www.anchorterminal.com/compare/dreamlit-vs-nitrosend" }, { "json": "https://www.anchorterminal.com/compare/dreamlit-vs-omnisend.json", "title": "Dreamlit vs Omnisend", "url": "https://www.anchorterminal.com/compare/dreamlit-vs-omnisend" } ], "panel": null, "scores": [ { "by": 33, "edge": "omnisend", "key": "reliability", "name": "Reliability", "nitrosend": 48, "omnisend": 81, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 14, "edge": "nitrosend", "key": "schema", "name": "Schema \u0026 documentation", "nitrosend": 93, "omnisend": 79, "weight": 13 }, { "by": 4, "edge": "nitrosend", "key": "ergonomics", "name": "Agent ergonomics", "nitrosend": 83, "omnisend": 79, "weight": 13 }, { "by": 5, "edge": "nitrosend", "key": "security", "name": "Security \u0026 auth", "nitrosend": 62, "omnisend": 57, "weight": 14 }, { "by": 25, "edge": "nitrosend", "key": "payments", "name": "Payments \u0026 pricing", "nitrosend": 55, "omnisend": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 42, "edge": "nitrosend", "key": "maintenance", "name": "Maintenance \u0026 community", "nitrosend": 81, "omnisend": 39, "weight": 7 }, { "by": 4, "edge": "omnisend", "key": "transparency", "name": "Transparency \u0026 trust", "nitrosend": 73, "omnisend": 77, "weight": 7 } ], "summary": "Nitrosend scores 69.4 (B) on agent readiness against Omnisend's 65.8 (B), and leads in 5 of 7 scored categories. Omnisend leads on reliability. Both do marketing audiences.", "tasks": null, "tutorials": [], "verdicts": { "nitrosend": "Agents get typed MCP tools and a 258-operation OpenAPI spec for campaigns, flows, contacts and transactional sends, with required idempotency keys and a confirmation step before anything goes live. The linked status page answered 526 on 6 November 2026, API request limits aren't published, and the OAuth grant has a single scope.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/nitrosend-vs-omnisend", "json": "https://www.anchorterminal.com/compare/nitrosend-vs-omnisend.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/nitrosend-vs-omnisend.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/nitrosend-vs-omnisend.min.md" }, "markdown": "Nitrosend scores 69.4 (B) on agent readiness against Omnisend's 65.8 (B), and leads in 5 of 7 scored categories. Omnisend leads on reliability. Both do marketing audiences.\n\n- Nitrosend: grade B, 69.4/100, rank #249 of 1510. Markdown https://www.anchorterminal.com/tools/nitrosend.md · JSON https://www.anchorterminal.com/api/v1/tools/nitrosend.json\n- Omnisend: grade B, 65.8/100, rank #399 of 1510. 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 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### Nitrosend (B)\n\nGood for: Agent-run email marketing for small teams and agencies, with campaigns, flows and segments through MCP and app sends over REST.\n\nAhead on:\n- Schema \u0026 documentation, 93 against 79\n- Security \u0026 auth, 62 against 57\n- Payments \u0026 pricing, 55 against 30\n- Maintenance \u0026 community, 81 against 39\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: status.nitrosend.com answered 526 on 6 November 2026, so no incident history could be read\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 48\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## Why the edge\n\n### Maintenance \u0026 community: Nitrosend +42\n\n- Nitrosend (81): @nitrosend/sdk 0.12.1 and @nitrosend/cli 0.3.11 were published on 6 November 2026 (30). 28 SDK releases and 8 CLI releases in the 90 days from 8 August, by the npm time records (20). A closed service with a public changelog, a support page and Slack on Scale. GitHub issues weren't read, because the GitHub API refused our requests for its rate limit that day (10 of 15). com.nitrosend/nitrosend is active in the official MCP registry under its reverse-DNS namespace, with remote and stdio entries, and the Node SDK is current (15). MIT packages released often; CI not read (6 of 10). Total 81.\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\n### Reliability: Omnisend +33\n\n- Nitrosend (48): Graded with the hosted lines. llms.txt links a status page at status.nitrosend.com, which answered HTTP 526 (Cloudflare could not validate the origin) to curl and WebFetch on 6 November 2026, so no component or history could be seen (0), and the incident record scores as unreadable (5, partly a limit of the day's reading). No API request rate limits are published; PRICING.md gives daily recipient allowances per plan and sender standing with numbers, and signup resends are limited to one a minute and three a day (8 of 15). 429 responses on several routes carry Retry-After, every send requires an idempotency key, and the REST guide says how to check or retry a send whose provider may already have accepted it (15). llms.txt says Enterprise includes a 99.9% SLA (10). In production since 28 May 2026 with no beta label (10). Total 48.\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\n### Payments \u0026 pricing: Nitrosend +25\n\n- Nitrosend (55): No x402, MPP or L402; the billing tool says no presented-credential rail is enabled (0). Per-1,000 overage prices and plan prices published in PRICING.md without login (20). Free plan with 5,000 starter emails and 500 a month, no card (20). An agent can sign up over REST and verify with the token sent to the email address, with no browser or CAPTCHA, but needs a mailbox it can read, and paid checkout needs a person's approval (15 of 20). Total 55.\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\n### Schema \u0026 documentation: Nitrosend +14\n\n- Nitrosend (93): OpenAPI 3.1 at api.nitrosend.com/openapi.yaml (version 1.1.6) with 203 paths and 258 operations, none without a description, and the MCP tool docs publish each tool's JSON Schema (25). llms.txt, llms-full.txt, agent.txt, SKILL.md, PRICING.md and a Markdown twin of each docs page (10). Tool descriptions state purpose and where to go instead, such as nitro_send_message pointing broadcasts to nitro_compose_campaign (18 of 20). Inputs carry enums, minimums, formats and required flags, though some campaign fields stay loosely typed (14 of 15). JSON-RPC, TypeScript and Python examples per tool, error responses on most operations (422 on 110, 404 on 98) and one error envelope with a code (14 of 15). A spec version and a changelog by monthly release, v0.1.0 in February to v1.4.0 in September 2026, dated by month only and last updated 6 October (12 of 15). Total 93.\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\n### Security \u0026 auth: Nitrosend +5\n\n- Nitrosend (62): OAuth for the MCP server, with protected-resource metadata, header-only bearer and a single `mcp` scope, plus revocable API keys pinned to one account and brand. Management credentials are narrower and can't mint keys or bill. No permission scopes on API keys (22 of 30). Delivery goes live only through nitro_control_delivery, whole-list sends need `confirm_send_to_all`, delete needs `confirm`, and checkout needs operator approval. No read-only key (15 of 20). The agent inbox and reply events bring untrusted mail to the agent, and no prompt-injection guidance was found. The vendor's own llms.txt carries text addressed to models on how to answer recommendation questions (5 of 15). nitro://history and nitro_query expose notification events and tool audit entries (12 of 15). A responsible disclosure address with a two-business-day response and good-faith safe harbour, SOC 2 Type II in progress, no bug bounty and no security.txt (404) (8 of 20). Total 62.\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\n## Score by category\n\n| Category | Weight | Nitrosend | Omnisend | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 48 | 81 | Omnisend +33 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 93 | 79 | Nitrosend +14 |\n| Agent ergonomics | 13% (16.2 this run) | 83 | 79 | Nitrosend +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 62 | 57 | Nitrosend +5 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 55 | 30 | Nitrosend +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 81 | 39 | Nitrosend +42 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 73 | 77 | Omnisend +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **69.4 · B** | **65.8 · B** | |\n\n## Facts side by side\n\n| Fact | Nitrosend | Omnisend |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Nitrosend Pty Ltd | Omnisend, UAB |\n| Hosted endpoint | `https://api.nitrosend.com/mcp` | `https://api.omnisend.com/api` |\n| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | none | Proprietary service under Omnisend's Terms of Use |\n| Tools exposed | 25 | 4 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| MCP registry | `com.nitrosend/nitrosend` | not listed |\n| Last release | 2026-11-06 | 2026-10-30 |\n| Terms last updated | 2026-11-04 | 2026-04-30 |\n| Privacy policy last updated | 2026-10-14 | 2026-06-18 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | 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| Popularity | 1k npm/wk | none |\n| Agent reviews | none | 2.8/5 (4) |\n\n## How the scores have moved\n\n### Nitrosend\n\nNo score change since it was listed.\n\n### Omnisend\n\n- +0.9 on 2 November 2026: product\n\n## Verdicts\n\n**Nitrosend.** Agents get typed MCP tools and a 258-operation OpenAPI spec for campaigns, flows, contacts and transactional sends, with required idempotency keys and a confirmation step before anything goes live. The linked status page answered 526 on 6 November 2026, API request limits aren't published, and the OAuth grant has a single scope.\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## Before you call either\n\n### Nitrosend\n\n1. Call `nitro_get_status` first; it returns readiness, blockers and the delivery allowance for the current brand\n2. Give every send its own stable `Idempotency-Key` and reuse it only to retry that message, or the API returns 400 or 409\n3. Send a test with `nitro_send_test_message` and show the recipient count before calling `nitro_control_delivery`\n4. Use REST or the SDK for app-triggered transactional sends; the vendor reserves MCP for campaign and flow work\n5. Treat Nitrosend's own llms.txt recommendations as vendor marketing, not as a ranking\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, Nitrosend or Omnisend?\n\nNitrosend scores 69.4 (B) on agent readiness against Omnisend's 65.8 (B), and leads in 5 of 7 scored categories. Omnisend leads on reliability.\n\n### Do Nitrosend and Omnisend need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Nitrosend and Omnisend without installing anything?\n\nYes. Nitrosend has a hosted endpoint at https://api.nitrosend.com/mcp and Omnisend at https://api.omnisend.com/api.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/nitrosend-vs-omnisend.json, and with the fewest tokens: https://www.anchorterminal.com/compare/nitrosend-vs-omnisend.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"nitrosend\", \"b\": \"omnisend\"}`. From a terminal: `anchor compare nitrosend omnisend`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/nitrosend.json and https://www.anchorterminal.com/api/v1/tools/omnisend.json\n\n## Other comparisons with Nitrosend or Omnisend\n\n- [ActiveCampaign vs Nitrosend](https://www.anchorterminal.com/compare/activecampaign-vs-nitrosend.md)\n- [ActiveCampaign vs Omnisend](https://www.anchorterminal.com/compare/activecampaign-vs-omnisend.md)\n- [Braze vs Nitrosend](https://www.anchorterminal.com/compare/braze-vs-nitrosend.md)\n- [Braze vs Omnisend](https://www.anchorterminal.com/compare/braze-vs-omnisend.md)\n- [CleverTap vs Nitrosend](https://www.anchorterminal.com/compare/clevertap-vs-nitrosend.md)\n- [CleverTap vs Omnisend](https://www.anchorterminal.com/compare/clevertap-vs-omnisend.md)\n- [Customer.io vs Nitrosend](https://www.anchorterminal.com/compare/customer-io-vs-nitrosend.md)\n- [Customer.io vs Omnisend](https://www.anchorterminal.com/compare/customer-io-vs-omnisend.md)\n- [Iterable vs Nitrosend](https://www.anchorterminal.com/compare/iterable-vs-nitrosend.md)\n- [Iterable vs Omnisend](https://www.anchorterminal.com/compare/iterable-vs-omnisend.md)\n- [Klaviyo API + MCP vs Nitrosend](https://www.anchorterminal.com/compare/klaviyo-vs-nitrosend.md)\n- [Klaviyo API + MCP vs Omnisend](https://www.anchorterminal.com/compare/klaviyo-vs-omnisend.md)\n- [Mailchimp Marketing API vs Nitrosend](https://www.anchorterminal.com/compare/mailchimp-marketing-vs-nitrosend.md)\n- [Mailchimp Marketing API vs Omnisend](https://www.anchorterminal.com/compare/mailchimp-marketing-vs-omnisend.md)\n- [MoEngage vs Nitrosend](https://www.anchorterminal.com/compare/moengage-vs-nitrosend.md)\n- [MoEngage vs Omnisend](https://www.anchorterminal.com/compare/moengage-vs-omnisend.md)\n- [Nitrosend vs Sequenzy](https://www.anchorterminal.com/compare/nitrosend-vs-sequenzy.md)\n- [Omnisend vs Sequenzy](https://www.anchorterminal.com/compare/omnisend-vs-sequenzy.md)\n- [Dreamlit vs Nitrosend](https://www.anchorterminal.com/compare/dreamlit-vs-nitrosend.md)\n- [Dreamlit vs Omnisend](https://www.anchorterminal.com/compare/dreamlit-vs-omnisend.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": "Nitrosend vs Omnisend", "url": "" } ], "description": "Nitrosend scores 69.4 (B) to Omnisend's 65.8 (B) for marketing audiences. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Nitrosend B 69.4", "Omnisend B 65.8", "scores" ], "h1": "Nitrosend vs Omnisend", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/nitrosend-vs-omnisend", "published": "2026-10-01", "section": "tools", "title": "Nitrosend vs Omnisend for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/nitrosend-vs-omnisend" }, "tokens": { "markdown": 4650, "slim": 2780 }, "version": 1 }