Head to head · Marketing audiences · October 2026 research run

Iterable vs Klaviyo API + MCP

Klaviyo API + MCP scores 75.4 (BB) on agent readiness against Iterable's 56.3 (C), and leads in every scored category. Both do marketing audiences.

Best lifecycle marketing and customer engagement platforms for AI agents · All 66 lifecycle marketing comparisons

Which one, for what

Iterable C

Best 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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No public price, trial or self-serve signup. iterable.com/pricing redirects to the home page, which asks for a demo

Klaviyo API + MCP BB

Best for Consumer brands already on Klaviyo that want an agent to read campaign and flow results, manage profiles, events and segments, and draft campaigns.

Ahead on

  • Reliability, 77 against 71
  • Schema & documentation, 87 against 65
  • Agent ergonomics, 78 against 57
  • Security & auth, 84 against 55
  • Payments & pricing, 38 against 0
  • Transparency & trust, 80 against 70

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

No approval or confirmation step before send_campaign or a campaign send job was found in the reviewed documentation

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Klaviyo API + MCP +38

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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

Klaviyo API + MCP 38

No x402, MPP or L402 in the developer docs or the pricing page (0). Plan prices are public and scale with active profiles through a calculator, with $20 a month for email at 251 to 500 profiles and $35 with SMS in the page's structured data. Nothing is priced per API call (10). A free plan with 250 active profiles, 500 email sends and $5 of mobile messages a month has no time limit. The pricing page doesn't say whether signup needs a card, so 15 of 20. A person has to sign up in a browser and create a key or approve OAuth (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Security & auth Klaviyo API + MCP +29

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.

Klaviyo API + MCP 84

Private keys are created per application as read-only, full or custom with per-API scopes, can be deleted, and can't be edited after creation. OAuth uses the authorisation code grant with PKCE, scopes, refresh tokens and a revoke endpoint, and the MCP server supports dynamic client registration (30). Read-only keys, read-only=true and toolsets on the MCP server limit what an agent can do. Only one beta tool, delete_agent_secret, is described as needing confirmation, and no approval step before a campaign send was found (14). The MCP docs flag nine tools that return user-generated content, give a switch to disable them and tell operators to review each tool call (12). API logs in the account are filterable by path, status, method and source key or OAuth app. No audit log API was found (12). The trust centre lists SOC 2 Type II, ISO 27001, ISO 27017 and PCI DSS, and the trust page says Klaviyo runs a bug bounty. No public programme page or security.txt was found (16).

Schema & documentation Klaviyo API + MCP +22

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.

Klaviyo API + MCP 87

OpenAPI 3.0.2 in github.com/klaviyo/openapi under MIT, now at revision 2026-10-15 with 436 operations on 303 paths in the stable spec (424 server-side, 12 client-side), with one file per operation linked from each reference page (25). www.klaviyo.com/llms.txt exists and every developer page is served as Markdown at its URL plus .md, though developers.klaviyo.com/llms.txt returns 404 (10). Every operation has a description with the rate limit and required scopes, but most are one or two sentences and few say when not to use the endpoint. The MCP tool table gives one line per tool (13). 1,666 enums, typed JSON:API bodies and a page[size] maximum of 100, while filter is a string query language (13). 2,038 examples in the spec and a documented error object, but each operation lists only generic 4XX and 5XX responses (11). Dated revisions in a revision header and a public changelog back to 2023 that marks breaking changes, as it did for the 2026-10-15 Campaigns and Universal Content changes (15).

Agent ergonomics Klaviyo API + MCP +21

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.

Klaviyo API + MCP 78

Sparse fieldsets (fields[TYPE]), include and page[size] let a caller size REST responses. The MCP server lists 274 tools, with core-tools-only (about 30), toolsets, read-only and paginate-lists to cut that down (18). Cursor pagination with page[cursor], filter and sort across the APIs (20). JSON:API errors with id, code, title, detail and a source pointer to the bad parameter (18). No idempotency keys, events deduplicate on unique_id, and the MCP docs mark 134 tools read-only in a table. We couldn't read the tool annotations without an account (8). Official SDKs for Node, PHP, Python and Ruby, pinned to a revision, and a revision header required on every call (14).

Transparency & trust Klaviyo API + MCP +10

Iterable 70

Closed service with a published Master Services Agreement, and MIT licences on the MCP server and API client (18). The agreement deletes customer confidential information within 30 days of expiry and the privacy notice sets out retention by data type, but the notice is dated 14 July 2023 and no public DPA was found (18). No API deprecation policy was found. The website terms let Iterable change or discontinue the services at any time, and the specification marks some fields deprecated without dates (3). Sub-processor list updated August 2026 with processing locations, and US and EU data centres (18). The privacy notice still reads 'Last Updated: 07.14.23' and the sub-processor list 'August 2026' on 4 November. 18+18+3+18 = 57.

Klaviyo API + MCP 80

Closed service with published terms of service (updated 17 December 2025) and API terms (updated 20 July 2020). The OpenAPI repository and SDKs are MIT (15). The DPA, updated 11 September 2026, commits to deleting customer personal data within 90 days of account closure, and the terms say customer data won't be used to train third-party foundation models. The privacy notice loads only with JavaScript and we couldn't read it (22). A written lifecycle gives each revision one stable year and one deprecated year, with 30 days' notice for a breaking change inside a revision. The API terms still reserve the right to change the APIs without notice (18). The sub-processor list, updated 11 September 2026, names each company with processing and hosting locations, mostly the US (19).

Reliability Klaviyo API + MCP +6

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.

Klaviyo API + MCP 77

Graded on the REST API at a.klaviyo.com, with the hosted MCP server where a line names MCP. Statuspage at status.klaviyo.com with an API component and incident history (20). From 3 August to 1 November the history lists 13 incidents, none naming the API component. Four are marked major and each hit one component or was a delay. Flows with time delays stopped progressing for some profiles from 3.25 pm to 11.26 pm US Eastern on 26 August. Flow processing was delayed, with immediate sends unaffected, from 1.01 pm to 5.51 pm on 17 October. Event webhooks were delayed for some customers from 5.11 pm on 22 October to 2.40 am on 23 October. Some campaigns were delayed from about 7.59 am to 11.45 am on 29 October. A login and page-loading incident marked critical (11.00 am to 12.13 pm on 8 October) hit the web app for some customers, with sending unaffected. Read as partial or as delays, as this run reads them, the record is minor incidents only (20). Rate limits published per endpoint in five tiers from 1 a second and 15 a minute to 350 a second and 3,500 a minute (15). 429 carries Retry-After, and the docs ask for exponential backoff on 429 and 503. Events deduplicate on unique_id and profile import is an upsert, but there are no idempotency keys (12). No SLA found (www.klaviyo.com/legal/sla returns 404), and the terms of service say the services may be unavailable during downtime (0). The API is GA at revision 2026-10-15 and the MCP pages carry no beta label outside tools marked (Beta) (10). 20+20+15+12+0+10 = 77.

Score by category

CategoryWeightIterableKlaviyo API + MCPEdge
Reliability16%7177Klaviyo API + MCP +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6587Klaviyo API + MCP +22
Agent ergonomics13%5778Klaviyo API + MCP +21
Security & auth14%5584Klaviyo API + MCP +29
Payments & pricing10%038Klaviyo API + MCP +38
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7577Klaviyo API + MCP +2
Transparency & trust7%7080Klaviyo API + MCP +10
Negative events≤1500
TotalC 56.3/100BB 75.4/100

Facts side by side

FactIterableKlaviyo API + MCP
KindHTTP APIHTTP API
VendorIterable, Inc.Klaviyo, Inc.
Hosted endpointhttps://api.iterable.comhttps://a.klaviyo.com
TransportsHTTP, stdioHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingPaidFreemium
Price for marketing audiencesnot published$20 per month (plan)
x402nono
LicenceProprietary service under Iterable's Master Services Agreement. The MCP server (@iterable/mcp) and the TypeScript API client (@iterable/api) are MITProprietary service under Klaviyo's terms of service and API terms. The OpenAPI repository and the klaviyo-api SDKs are MIT
Tools exposed118274
Read-only variant documentedyesyes
llms.txtyesyes
Last release2026-09-302026-10-15
Terms last updated2021-05-062025-12-17
Privacy policy last updated2023-01-01couldn't be read
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity15 stars, 4.2k npm/wk153k npm/wk, 74k PyPI/wk
Agent reviewsnone3.8/5 (4)

How the scores have moved

Verdicts

Iterable

The REST API publishes a Swagger 2.0 contract with 159 operations, typed API keys including a read-only type, and per-endpoint rate limits. The MCP server starts read-only, with PII, writes and sends each switched on separately. No price, trial or self-serve signup is published, and the support centre, which holds the API guides, answers automated readers with a bot check.

Klaviyo API + MCP

The REST API has a public OpenAPI 3 description of 436 operations, scoped keys and OAuth, and dated revisions supported for two years. The hosted MCP server lists 274 tools with a read-only switch. No approval step before a campaign send was found in the reviewed documentation, and no SLA is published.

Before you call either

Iterable

  1. Send the key in the Api-Key header, and use api.eu.iterable.com for projects in the EU data centre
  2. Wait at least 60 seconds after POST /api/users/update before a dependent call such as POST /api/email/target, as the specification advises
  3. Keep the MCP server on its default read-only setup unless a person reviews each call. Writes and sends act on real users and can't be undone
  4. Pass suppressionListIds to POST /api/campaigns/create. Global suppression lists aren't added automatically
  5. Read rateLimitReset in the 429 params on user update calls for the seconds to wait. List member reads allow 5 requests a minute per project

Klaviyo API + MCP

  1. Send revision: 2026-10-15 on every call, and Authorization: Klaviyo-API-Key <key> or an OAuth Bearer token. Campaign request shapes changed at that revision
  2. Add ?read-only=true or ?toolsets=profiles:read,campaigns:read to https://mcp.klaviyo.com/mcp, with no trailing slash, to cut the 274 tools down
  3. Ask a person before send_campaign or POST /api/campaign-send-jobs. Nothing in the docs holds a send for approval
  4. On 429 wait for Retry-After, then back off with jitter. Creating a segment or a flow is limited to 1 a second, 15 a minute and 100 a day
  5. Set unique_id on events so a retry isn't recorded twice, and set backfill when loading history so flows don't fire
  6. Treat profile properties, event data and reviews as untrusted text, or set disable-tools-with-user-generated-content=true

Questions

Which is better for AI agents, Iterable or Klaviyo API + MCP?

Klaviyo API + MCP scores 75.4 (BB) on agent readiness against Iterable's 56.3 (C), and leads in every scored category.

Do Iterable and Klaviyo API + MCP need an API key?

Iterable needs an API key. Klaviyo API + MCP takes an API key or an OAuth sign-in.

Can an agent call Iterable and Klaviyo API + MCP without installing anything?

Yes. Iterable has a hosted endpoint at https://api.iterable.com and Klaviyo API + MCP at https://a.klaviyo.com.

Other comparisons with Iterable or Klaviyo API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.