Head to head · Marketing audiences · October 2026 research run
CleverTap vs Nitrosend
Nitrosend scores 69.4 (B) on agent readiness against CleverTap's 50.4 (D), 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
Best email delivery APIs for AI agents · All 174 email comparisons
Which one, for what
Best for A team already on CleverTap that wants an agent to load profiles and events, read them back, create or stop API campaigns and pull campaign reports.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No OpenAPI file was found. The contract is prose tables plus a Postman collection published as a zip on GitHub
Best 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 37
- Schema & documentation, 93 against 57
- Agent ergonomics, 83 against 53
- Security & auth, 62 against 56
- Payments & pricing, 55 against 25
- Maintenance & community, 81 against 73
- Transparency & trust, 73 against 66
Also in its favour
- A hosted endpoint, with nothing to install
- Runs on your own machine
- Free to start without a card
Watch for
status.nitrosend.com answered 526 on 6 November 2026, so no incident history could be read
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.
Schema & documentation Nitrosend +36
CleverTap 57
No OpenAPI file was found. A Postman collection is published as a zip on GitHub, which was not opened (6). Both docs hosts publish llms.txt and a Markdown twin of every page (10). Each endpoint page opens with an overview and use cases, and Stop Scheduled Campaign lists what happens in each campaign state. Few pages say when not to use an endpoint (13). Parameters sit in prose tables with type, required flag and sample value, with no schema and few enums (8). Request examples come in up to six languages with sample responses, and each API has an error table. The quick start recommends Python 2.7 (13). Paths carry /1/, /2/ and /v1/. SDK changelogs and product release notes are monthly, and no API changelog was found (7). Total 57.
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.
Agent ergonomics Nitrosend +30
CleverTap 53
Get User Profiles takes batch_size and app, events and profile flags, and reports take date ranges. No field selection was found (12). Profiles and events page by cursor with next_cursor, valid for 4 days. Get Campaigns filters only by date range and lists only API-created campaigns (14). Errors use status, error and code with per-API code lists and per-record results on uploads, but Get User Profiles returns some throttling errors with HTTP 200 (13). No idempotency key was found. dryRun=1 validates uploads, estimate_only and draft hold a campaign back, and stopping a stopped campaign returns success (8). One current server library, Node.js clevertap 1.3.1. The linked Python wrapper was last changed in 2017 (6). Total 53.
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.
Payments & pricing Nitrosend +30
CleverTap 25
No x402, MPP or L402 (0). The Core plan's entry price is public at 85 dollars a month, re-read on 4 November, for up to 5,000 monthly active users. The larger tiers were not readable and Pro and Ultimate need a demo, so this is plan-only pricing (10). Core has a 30-day free trial. The account docs say billing details are needed before the last seven days, so 5 of the 20 points come off (15). A person signs up in a browser and creates the passcode in the dashboard (0). Total 25.
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.
Reliability Nitrosend +11
CleverTap 37
Graded on the REST API, with the hosted lines. No status page is linked from the home page, the pricing, security, terms or privacy pages or either docs index, re-read on 4 November, and no address was guessed (0). With no page there is no readable incident history, which this run scores 5 (from 0). Concurrent request limits are published with numbers for 23 API groups (15 on uploads, 3 elsewhere) with 1,000 records a call, re-read on 4 November, but the Create Campaign page gives 3 requests a second, per the 9 October check, and the Get User Profiles page, re-read on 4 November, says limits are account-specific (13). HTTP 429 is in the errors table, re-read on 4 November, and the Get User Profiles page asks for exponential backoff of 1 to 16 seconds with at most 5 retries and says a cursor survives a timeout. That page, re-read on 4 November (updated 3 July 2026), still gives the backoff schedule for 429, 500 and 503. No Retry-After header and no idempotency key or safe-retry guidance for writes were found, so this run's value for backoff guidance alone applies (10, from 8). The terms, re-read on 4 November, leave service levels to each order, and no SLA is published (0). The API is generally available, with the External Trigger API in Public Beta, per the 9 October check (9). 0+5+13+10+0+9 = 37.
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.
Maintenance & community Nitrosend +8
CleverTap 73
The Web SDK tagged v3.1.2 on 2 November 2026, and the iOS SDK 7.9.1 on 30 October (30). Since 6 August the Web SDK has tagged v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.1.0, v3.1.1 and v3.1.2, the Android SDK core 8.4.1, push templates 2.6.0 and core 8.5.0 with templates 2.7.0, and the iOS SDK 7.8.1, 7.8.2, 7.9.0 and 7.9.1, read from clones on 4 November (20). Public monthly SDK changelogs (September 2026 is the newest page) and product release notes, with support through a dashboard ticket. GitHub issue handling was not read (9). Client SDKs are current. The Node.js server library's last release is still 1.3.1 (7 July 2026), and the Python wrapper dates from 2017 (10). The Node.js library ships a Travis CI file and depends on node-fetch 2. Its CI state was not read (4). 30+20+9+10+4 = 73.
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.
Transparency & trust Nitrosend +7
CleverTap 66
Closed service with public Terms of Service, last updated 30 April 2021 and re-read on 4 November, that name WizRocket Inc. and state the restrictions plainly (15). The privacy policy of 9 April 2026, unchanged on 4 November, covers CleverTap as processor, with deletion within 60 days of termination, and the docs give three years' default retention on Core and backup deletion within 60 days. The Data Processing Addendum the policy cites was not found in public (22). No API deprecation policy was found. The only dated notice read is the 2021 end of TLS 1.1 (3). Six hosting regions are documented and AWS is named as host. The sub-processor list sits on the trust portal, which answered 403 and was not read (10). Total 50.
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.
Score by category
| Category | Weight this run | CleverTap | Nitrosend | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 37 | 48 | Nitrosend +11 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 57 | 93 | Nitrosend +36 |
| Agent ergonomics | 13%16.2 | 53 | 83 | Nitrosend +30 |
| Security & auth | 14%17.5 | 56 | 62 | Nitrosend +6 |
| Payments & pricing | 10%12.5 | 25 | 55 | Nitrosend +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 73 | 81 | Nitrosend +8 |
| Transparency & trust | 7%8.8 | 66 | 73 | Nitrosend +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 50.4/100 | B 69.4/100 |
Facts side by side
| Fact | CleverTap | Nitrosend |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | WizRocket Inc. | Nitrosend Pty Ltd |
| Hosted endpoint | no (local only) | https://api.nitrosend.com/mcp |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary service under CleverTap's Terms of Service. The Node.js API library on GitHub is MIT | none |
| Tools exposed | none | 25 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | com.nitrosend/nitrosend |
| Last release | 2026-10-01 | 2026-11-06 |
| Terms last updated | 2021-04-30 | 2026-11-04 |
| Privacy policy last updated | 2026-04-09 | 2026-10-14 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 3k npm/wk | 1k npm/wk |
How the scores have moved
Nitrosend
No score change since it was listed.
Verdicts
CleverTap
CleverTap's REST API uploads and reads profiles and events, creates and stops campaigns and reports results, with Markdown docs, numeric concurrency limits and a 30-day Core trial. No OpenAPI file or public status page was found, passcodes carry no scopes, and the docs say campaigns created through the API are not restricted by role-based access control.
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.
Before you call either
CleverTap
- Call the host for the account's region, such as
in1.api.clevertap.comorus1.api.clevertap.com.api.clevertap.comis the Europe region - Send
X-CleverTap-Account-IdandX-CleverTap-Passcodeheaders on every call, and ask for a named passcode with an expiry date - Check
statusin the body as well as the HTTP code. Get User Profiles can answer 200 with"status":"fail"when throttled - Add
dryRun=1to an upload URL to validate up to 1,000 records without storing them - Set
estimate_onlyordraftto true on Create Campaign before a real send. API campaigns bypass dashboard role restrictions
Nitrosend
- Call
nitro_get_statusfirst; it returns readiness, blockers and the delivery allowance for the current brand - Give every send its own stable
Idempotency-Keyand reuse it only to retry that message, or the API returns 400 or 409 - Send a test with
nitro_send_test_messageand show the recipient count before callingnitro_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
Questions
Which is better for AI agents, CleverTap or Nitrosend?
Nitrosend scores 69.4 (B) on agent readiness against CleverTap's 50.4 (D), and leads in every scored category.
Do CleverTap and Nitrosend need an API key?
CleverTap needs an API key. Nitrosend takes an API key or an OAuth sign-in.
Can an agent call CleverTap and Nitrosend without installing anything?
No hosted endpoint is listed for CleverTap. Nitrosend has a hosted endpoint at https://api.nitrosend.com/mcp.
Other comparisons with CleverTap or Nitrosend
- ActiveCampaign vs CleverTap
- ActiveCampaign vs Nitrosend
- Braze vs CleverTap
- Braze vs Nitrosend
- CleverTap vs Customer.io
- CleverTap vs Iterable
- CleverTap vs Klaviyo API + MCP
- CleverTap vs Mailchimp Marketing API
- CleverTap vs MoEngage
- CleverTap vs Omnisend
- CleverTap vs Sequenzy
- Customer.io vs Nitrosend
- Iterable vs Nitrosend
- Klaviyo API + MCP vs Nitrosend
- Mailchimp Marketing API vs Nitrosend
- MoEngage vs Nitrosend
- Nitrosend vs Omnisend
- Nitrosend vs Sequenzy
- Dreamlit vs Nitrosend
- CleverTap vs Dreamlit
Machine-readable
- This page as Markdown
/compare/clevertap-vs-nitrosend.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/clevertap.json·/api/v1/tools/nitrosend.json - From a terminal
anchor compare clevertap nitrosend(the CLI) - Over MCP
compare_tools {"a": "clevertap", "b": "nitrosend"}at/mcp, no key