# Nitrosend vs Sequenzy (slim)

> Nitrosend scores 69.4 (B) to Sequenzy's 63.7 (B) for marketing audiences. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/nitrosend-vs-sequenzy.md (~4,050 tokens) · this version ~2,280 tokens · JSON https://www.anchorterminal.com/compare/nitrosend-vs-sequenzy.json · canonical https://www.anchorterminal.com/compare/nitrosend-vs-sequenzy
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Nitrosend scores 69.4 (B) on agent readiness against Sequenzy's 63.7 (B), and leads in 5 of 7 scored categories. Sequenzy leads on security & auth. Both do marketing audiences.

- Nitrosend: B 69.4, rank #249 of 1510 · https://www.anchorterminal.com/tools/nitrosend.min.md
- Sequenzy: B 63.7, rank #506 of 1510 · https://www.anchorterminal.com/tools/sequenzy.min.md
- Nitrosend, good for Agent-run email marketing for small teams and agencies, with campaigns, flows and segments through MCP and app sends over REST. Ahead on Reliability, 48 against 38; Agent ergonomics, 83 against 69; Payments & pricing, 55 against 40; Transparency & trust, 73 against 67.
- Sequenzy, good for SaaS and ecommerce lifecycle email run from code or an agent, with billing-event triggers from Stripe, Paddle and others. Ahead on Security & auth, 67 against 62.

| Category | Nitrosend | Sequenzy |
| --- | --- | --- |
| Reliability (16%) | 48 | 38 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 93 | 95 |
| Agent ergonomics (13%) | 83 | 69 |
| Security & auth (14%) | 62 | 67 |
| Payments & pricing (10%) | 55 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 81 | 78 |
| Transparency & trust (7%) | 73 | 67 |

| Fact (where they differ) | Nitrosend | Sequenzy |
| --- | --- | --- |
| Vendor | Nitrosend Pty Ltd | Nic Tech Solutions, LLC |
| Hosted endpoint | `https://api.nitrosend.com/mcp` | `https://api.sequenzy.com/v1/mcp` |
| Tools exposed | 25 | 306 |
| Read-only variant documented | no | yes |
| MCP registry | `com.nitrosend/nitrosend` | `io.github.polnikale/sequenzy-mcp` |
| Terms last updated | 2026-11-04 | 2026-06-30 |
| Privacy policy last updated | 2026-10-14 | 2026-09-16 |
| Terms restrict automated access | yes | not found in the text |
| Popularity | 1k npm/wk | 2.4k npm/wk |

Why the edge:
- Payments & pricing, Nitrosend +15: 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.); 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.)
- Agent ergonomics, Nitrosend +14: Nitrosend 83 (25 MCP tools is the 11 to 30 band; nitro_query reads every entity with filters, but no read-only subset or dynamic loading was found (15 of 25). Page and limit up to 100 with total and next-page headers, and keyset cursors on timelines (20). Errors return `error`, a `code`, validation details and next actions, and signup returns `next_action` (18 of 20). Required idempotency keys on sends, events, checkout and validation, and declared readOnlyHint and destructiveHint on the tools (20). Defaults such as the active brand and a recommended first call, but the only official SDK is Node, with a CLI beside it (10 of 15). Total 83.); 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.)
- Reliability, Nitrosend +10: 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.); 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.)
- Transparency & trust, Nitrosend +6: Nitrosend 73 (A closed service under terms that name Nitrosend Pty Ltd and Victorian law. The SDK, CLI and stdio MCP bridge are MIT on npm (18 of 30). Privacy policy of 14 October 2026 with account data kept while the account is open, export within 30 days of closure and deletion within 90 days, no-training terms for OpenAI and Anthropic, and a DPA by request rather than published (20 of 30). Deprecated fields are flagged in the OpenAPI spec, and material privacy changes come with 30 days' notice. No API deprecation policy found (8 of 20). Ten sub-processors listed with purpose and certifications, and the data location stated as AWS us-east-1 (18 of 20). Total 64.); Sequenzy 67 (A closed service. The SDK, MCP server and CLI are MIT on npm. The terms (30 June 2026) don't name the contracting entity in their text or a governing jurisdiction; the footer names Nic Tech Solutions, LLC (15 of 30). Privacy policy of 16 September 2026 and a public DPA agree on processing, and the terms say data is deleted within 30 days of termination (24 of 30). Deprecated endpoints are marked and kept as compatibility aliases; no written deprecation policy with notice periods (10 of 20). The DPA names its core sub-processors with their purpose; data locations aren't stated (15 of 20). Total 64.)
- Security & auth, Sequenzy +5: 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.); 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.)