# Iterable vs Sequenzy (slim)

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

- Full: https://www.anchorterminal.com/compare/iterable-vs-sequenzy.md (~4,450 tokens) · this version ~2,630 tokens · JSON https://www.anchorterminal.com/compare/iterable-vs-sequenzy.json · canonical https://www.anchorterminal.com/compare/iterable-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)

Sequenzy scores 63.7 (B) on agent readiness against Iterable's 56.3 (C), and leads in 5 of 7 scored categories. Iterable leads on reliability. Both do marketing audiences.

- Iterable: C 56.3, rank #830 of 1486 · https://www.anchorterminal.com/tools/iterable.min.md
- Sequenzy: B 63.7, rank #504 of 1486 · https://www.anchorterminal.com/tools/sequenzy.min.md
- Iterable, good for A team already on Iterable that wants an agent to read campaigns, templates and metrics, or to update profiles, track events and trigger sends under review. Ahead on Reliability, 71 against 38.
- 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 Schema & documentation, 95 against 65; Agent ergonomics, 69 against 57; Security & auth, 67 against 55; Payments & pricing, 40 against 0. Also Free to start without a card.

| Category | Iterable | Sequenzy |
| --- | --- | --- |
| Reliability (16%) | 71 | 38 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 65 | 95 |
| Agent ergonomics (13%) | 57 | 69 |
| Security & auth (14%) | 55 | 67 |
| Payments & pricing (10%) | 0 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 78 |
| Transparency & trust (7%) | 70 | 67 |

| Fact (where they differ) | Iterable | Sequenzy |
| --- | --- | --- |
| Vendor | Iterable, Inc. | Nic Tech Solutions, LLC |
| Hosted endpoint | `https://api.iterable.com` | `https://api.sequenzy.com/v1/mcp` |
| Transports | HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| Licence | Proprietary service under Iterable's Master Services Agreement. The MCP server (@iterable/mcp) and the TypeScript API client (@iterable/api) are MIT | none |
| Tools exposed | 118 | 306 |
| MCP registry | not listed | `io.github.polnikale/sequenzy-mcp` |
| Last release | 2026-09-30 | 2026-11-06 |
| Terms last updated | 2021-05-06 | 2026-06-30 |
| Privacy policy last updated | 2023-01-01 | 2026-09-16 |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 15 stars, 4.2k npm/wk | 2.4k npm/wk |

Why the edge:
- Payments & pricing, Sequenzy +40: Iterable 0 (No x402, MPP or L402 (0). No public prices. iterable.com/pricing redirects to the home page, which asks for a demo (0). No free tier or trial was found (0). A person has to buy through sales and create a key in the app (0). 0+0+0+0 = 0.); 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.)
- Reliability, Iterable +33: Iterable 71 (Graded on the REST API, with the hosted lines. Statuspage site at status.iterable.com, whose page lists global components such as Global API Success and per-cluster components such as User Updates (20). The 8 October incident reading came from the page's JSON API, which its robots.txt closes, so it is struck and the window was re-read from /history.atom on 4 November. The 90 days from 6 August hold four incidents, each partial by its own text, Twilio SMS drops for a subset of customers on 1 September, EU platform slowness and gateway errors on 10 September (about 9:25 to 11:13 EDT), timeouts on the user update endpoints on 22 September, and delayed sends for some SparkPost US customers on 28 October. The 16 July critical incident has left the window. Minor only (20, from 15). 53 of 159 operations state a numeric limit in the specification re-read on 4 November (15). Only 7 operations document 429, two of them with `rateLimitReset` in the body. No Retry-After header or idempotency key was found in the specification, and backoff guidance on the support centre couldn't be read (6, an earlier partial kept). No SLA was found in the Master Services Agreement (last updated 8 June 2026) or the product-specific terms (0). The REST API is generally available. The MCP server is beta (10). 20+20+15+6+0+10 = 71.); 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.)
- Schema & documentation, Sequenzy +30: Iterable 65 (Public Swagger 2.0 specification at api.iterable.com/api-docs, which the API explorer page links as 'Raw API specification (JSON)', with 159 operations and 209 schemas on 4 November (25). iterable.com/llms.txt exists but describes the company and links the documentation without carrying it, and no Markdown docs were found (4). All 159 operations have a summary and 147 a description, several with cautions such as the 60-second wait after a user update and the suppression list rule on campaign creation (14). Required fields are marked and there are 35 enums, while `dataFields` and template content stay free-form objects (11). The specification has 21 examples. 400 and 401 appear on nearly every operation, and the error body has a 26-value `code` enum (8). The specification is labelled version 1.8 with no version in the path. Release notes sit on the support centre, which answered a Cloudflare check again on 4 November, so only 3 of 15 here (an earlier partial kept). The specification was re-read on 4 November, and the description, enum and example counts are per the 8 October check. 25+4+14+11+8+3 = 65.); 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.)
- Agent ergonomics, Sequenzy +12: Iterable 57 (API list calls take `page` and `pageSize`, and the MCP server shows 31 of its 118 tools by default, with three flags that add the rest (15). `nextPageUrl` paging on campaigns, catalogues, journeys and templates, state and sort filters on campaigns, and `limit` on events, but list member reads are capped at 5 requests a minute (14). Errors carry a `code` from a 26-value enum, a message and `params`, with reset seconds on some 429s (15). No idempotency keys. User updates merge and catalogue PUT replaces, so those retries are safe, but sends aren't. The MCP tools have no readOnlyHint or destructiveHint, and an issue asking for them has been open since 4 June 2026 (6). Most calls need few parameters. The one server-side SDK is the TypeScript client, which its README calls experimental (7). Per the 8 October check, and the MCP repository has no commit since 1.9.0 on 30 September. 15+14+15+6+7 = 57.); 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.)
- Security & auth, Sequenzy +12: Iterable 55 (API keys come in five types and each operation lists the types it accepts. A read-only type works on 30 operations, and the key travels only in a header. Rotation and expiry are unchecked because the key guide couldn't be read (22). The read-only key type, and an MCP server that starts with PII, writes and sends all off and stores those settings per key. Neither surface has a confirmation step, and the README leaves review of each call to the person (16). Profiles, events and templates hold customer-written text. The README warns about irreversible actions but gives no injection guidance (3). No audit log or per-call record for the operator was found in the pages we could read (0). The responsible disclosure policy, re-read on 4 November, says Iterable responds 'usually one to three business days' and that there is no public bug bounty. No security.txt, SOC 2 Type 2, ISO 27001 and HIPAA on the trust centre, and CodeQL on the open repositories (14). 22+16+3+0+14 = 55.); 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.)