{ "data": { "a": { "slug": "clevertap", "name": "CleverTap", "vendor": "WizRocket Inc.", "vendorUrl": "https://clevertap.com", "kind": "http-api", "category": "lifecycle-marketing", "summary": "CleverTap is a hosted customer engagement platform that stores user profiles and events and sends campaigns by push, email, SMS, WhatsApp and in-app messages. Agents reach it through a REST API authenticated with an account ID and passcode.", "url": "https://www.anchorterminal.com/tools/clevertap", "markdownUrl": "https://www.anchorterminal.com/tools/clevertap.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/clevertap.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/clevertap.json", "dns": "clevertap.grade.anchorterminal.com", "repo": "https://github.com/CleverTap/clevertap-node", "license": "Proprietary service under CleverTap's Terms of Service. The Node.js API library on GitHub is MIT", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "clevertap" } ], "auth": "api-key", "authNotes": "Access needs a CleverTap account, which the Core plan's 30-day trial opens through a browser signup. Every call sends `X-CleverTap-Account-Id` and `X-CleverTap-Passcode` headers. An admin, or a user with write access to User Settings, creates up to 100 named account passcodes under Settings, Passcodes, each with an optional expiry, and can delete them. An admin can instead grant per-user passcodes, valid for 1 to 365 days or up to 10 years, and reset or revoke them. No scopes, read-only passcodes or OAuth were found for the customer API. Partners that connect customer accounts through `/v1/connect` are allowlisted by email request. SCIM provisioning has its own endpoints.", "pricing": "paid", "pricingNotes": "Core starts at 85 dollars a month for up to 5,000 monthly active users, before tax and add-ons, with a 30-day free trial. Billing details are needed before the last seven days of the trial, per the account docs. Prices for the larger tiers (20,000 to 100,000 users) are chosen in a selector that our reader did not see. Pro and Ultimate are sold through a demo. The plan table lists API access (import and export) as a plan item, and no per-call price was found. Each user is allowed 10,000 data points a month, with overage charges (checked 2026-10-09).", "priceSummary": "$85 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs index, the API pages read, the pricing page or the terms (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 2985, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://developer.clevertap.com/docs/api-overview", "llmsTxt": "https://developer.clevertap.com/llms.txt", "capabilities": [ "marketing.profiles", "marketing.events", "marketing.campaigns", "marketing.segments", "notify.push" ], "tags": [ "official", "hosted", "api-key", "llms-txt", "closed-source", "eu-region", "soc2", "node" ], "lastRelease": "2026-10-01", "graded": true, "anchor": { "graded": true, "score": 50.4, "grade": "D", "agentReady": false, "rank": 1066, "ranked": true, "rankOf": 1510, "categoryRank": 11, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 53, "maintenance": 73, "payments": 25, "reliability": 37, "schema": 57, "security": 56, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Both docs hosts publish llms.txt and a Markdown twin of every page, with request examples in up to six languages", "A concurrency limit is published for 23 API groups, 15 parallel requests on uploads and 3 on the others", "Up to 100 named account passcodes with optional expiry, plus per-user passcodes an admin can reset or revoke", "Create Campaign accepts `estimate_only` to return reach without creating anything and `draft` to save without sending", "Audit logs list API key creation and revocation and API access, with CSV download and a daily export to cloud storage" ], "weaknesses": [ "No OpenAPI file was found. The contract is prose tables plus a Postman collection published as a zip on GitHub", "No public status page or SLA was found on the site, the docs or the terms, which leave service levels to each order", "Passcodes carry no scopes or read-only mode, and the docs say campaigns created through the API are not restricted by role-based access control", "Get User Profiles returns some throttling errors with HTTP 200 and a `fail` status in the body", "The Terms of Service (30 April 2021) bar customers from publicly disseminating information on the performance of the Services, which matters before any probe is run" ], "agentNotes": [ "Call the host for the account's region, such as `in1.api.clevertap.com` or `us1.api.clevertap.com`. `api.clevertap.com` is the Europe region", "Send `X-CleverTap-Account-Id` and `X-CleverTap-Passcode` headers on every call, and ask for a named passcode with an expiry date", "Check `status` in the body as well as the HTTP code. Get User Profiles can answer 200 with `\"status\":\"fail\"` when throttled", "Add `dryRun=1` to an upload URL to validate up to 1,000 records without storing them", "Set `estimate_only` or `draft` to true on Create Campaign before a real send. API campaigns bypass dashboard role restrictions" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50.4 } ], "editorialScores": { "ergonomics": 53, "maintenance": 73, "payments": 25, "reliability": 37, "schema": 57, "security": 56, "transparency": 50 }, "provenanceScore": 81, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install clevertap", "http": "curl -X POST -d '{\"d\":[{\"identity\":\"USER_ID\",\"type\":\"profile\",\"profileData\":{\"Name\": \"George Montana\", \"Customer Type\": \"Silver\"}}]}' \"https://in1.api.clevertap.com/1/upload\" \\\n-H \"X-CleverTap-Account-Id: ACCOUNT_ID\" \\\n-H \"X-CleverTap-Passcode: PASSCODE\" \\\n-H \"Content-Type: application/json; charset=utf-8\"" }, "letme": { "capability": "https://letme.dev/marketing.profiles", "tool": "https://letme.dev/clevertap" }, "area": "communication", "unitPrices": [ { "item": "Core, up to 5,000 monthly active users", "unit": "month", "usd": 85, "note": "before tax and add-ons, after a 30-day trial" } ], "provenance": { "legalEntity": "WizRocket Inc.", "domain": "clevertap.com", "domainRegistered": "2015-08-19", "endpointOnVendorDomain": true, "terms": "https://clevertap.com/terms-service/", "privacy": "https://clevertap.com/privacy-policy/", "statusPage": "", "changelog": "https://docs.clevertap.com/docs/whats-new", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "The Terms of Service (last updated 30 April 2021) govern the software-as-a-service products of WizRocket Inc. and its affiliates and choose California law. The site footer gives CleverTap Private Limited as the legal name.", "The privacy policy (last updated 9 April 2026) names WizRocket Inc., a Delaware corporation, CleverTap Private Limited (India) and CleverTap Pte. Ltd. (Singapore), and covers CleverTap as processor of customers' end-user data.", "The API answers on api.clevertap.com and regional subdomains of it, all on the vendor's domain.", "https://clevertap.com/.well-known/security.txt returns 404 (re-read 4 November). No disclosure policy or bug bounty was found on the pages read.", "No status page is linked from the home page, the pricing, security, terms or privacy pages or either docs index. No status address was guessed.", "Product release notes are grouped by month with no day. SDK changelogs are monthly pages that link dated GitHub releases." ], "score": 81 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/clevertap.json", "live": { "slug": "clevertap", "versions": [ { "registry": "github", "name": "CleverTap/clevertap-node", "version": "v1.3.1", "released": "2026-07-07", "seenAt": "2026-11-06T23:15:02.824352522Z" }, { "registry": "npm", "name": "clevertap", "version": "1.3.1", "seenAt": "2026-11-06T23:15:02.609154774Z" } ], "githubStars": 8, "npmWeekly": 10088, "securityTxt": { "url": "https://clevertap.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:22.421579743Z" }, "llmsTxt": { "url": "https://developer.clevertap.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:50.896256339Z" }, "domain": { "domain": "clevertap.com", "registered": "2015-08-19", "source": "https://rdap.verisign.com/com/v1/domain/clevertap.com", "checkedAt": "2026-11-01T14:10:49.050572856Z" }, "pages": [ { "url": "https://docs.clevertap.com/docs/whats-new", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:05:31.280592866Z", "changedAt": "2026-11-06T13:28:00.574826487Z", "fingerprint": "2dd6b2658580" }, { "url": "https://clevertap.com/privacy-policy/", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:01:05.114901781Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "df19d42437f7" }, { "url": "https://clevertap.com/terms-service/", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:01:07.156662057Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e8f066ae0f2d" } ], "github": { "repo": "clevertap/clevertap-node", "checkedAt": "2026-11-02T08:39:02.273868525Z", "stars": 8, "archived": false, "issuesEnabled": true, "pushedAt": "2026-07-07T06:20:22Z", "openIssues": 2, "openPRs": 2, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0, "replies": { "sampled": 9, "unanswered": 2, "medianDays": 235.1 } }, "updatedAt": "2026-11-07T16:00:22.421579743Z" } }, "answer": "Nitrosend scores 69.4 (B) on agent readiness against CleverTap's 50.4 (D), and leads in every scored category.", "b": { "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" } }, "edges": [ { "by": 36, "category": "schema", "leads": "nitrosend", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 57, "b": 93 } }, { "by": 30, "category": "ergonomics", "leads": "nitrosend", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 53, "b": 83 } }, { "by": 30, "category": "payments", "leads": "nitrosend", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 25, "b": 55 } }, { "by": 11, "category": "reliability", "leads": "nitrosend", "name": "Reliability", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 37, "b": 48 } }, { "by": 8, "category": "maintenance", "leads": "nitrosend", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "@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." }, "scores": { "a": 73, "b": 81 } }, { "by": 7, "category": "transparency", "leads": "nitrosend", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 66, "b": 73 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "WizRocket Inc.", "b": "Nitrosend Pty Ltd", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.nitrosend.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP, stdio", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under CleverTap's Terms of Service. The Node.js API library on GitHub is MIT", "b": "none", "name": "Licence" }, { "a": "none", "b": "25", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "com.nitrosend/nitrosend", "name": "MCP registry" }, { "a": "2026-10-01", "b": "2026-11-06", "name": "Last release" }, { "a": "2021-04-30", "b": "2026-11-04", "name": "Terms last updated" }, { "a": "2026-04-09", "b": "2026-10-14", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "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": "3k npm/wk", "b": "1k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Nitrosend scores 69.4 (B) on agent readiness against CleverTap's 50.4 (D), and leads in every scored category.", "question": "Which is better for AI agents, CleverTap or Nitrosend?" }, { "answer": "CleverTap needs an API key. Nitrosend takes an API key or an OAuth sign-in.", "question": "Do CleverTap and Nitrosend need an API key?" }, { "answer": "No hosted endpoint is listed for CleverTap. Nitrosend has a hosted endpoint at https://api.nitrosend.com/mcp.", "question": "Can an agent call CleverTap and Nitrosend without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "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.", "slug": "clevertap", "watchFor": "No OpenAPI file was found. The contract is prose tables plus a Postman collection published as a zip on GitHub" }, { "aheadOn": [ "Reliability, 48 against 37", "Schema \u0026 documentation, 93 against 57", "Agent ergonomics, 83 against 53", "Security \u0026 auth, 62 against 56", "Payments \u0026 pricing, 55 against 25", "Maintenance \u0026 community, 81 against 73", "Transparency \u0026 trust, 73 against 66" ], "also": [ "A hosted endpoint, with nothing to install", "Runs on your own machine", "Free to start without a card" ], "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" } ], "history": { "clevertap": [ { "causes": [ "correction" ], "date": "2026-11-04", "delta": 1.4, "from": 49, "fromGrade": "D", "to": 50.4, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 48.8, "fromGrade": "D", "to": 49, "toGrade": "D" } ], "nitrosend": null }, "job": { "capability": "marketing.profiles", "name": "Marketing audiences" }, "others": [ { "json": "https://www.anchorterminal.com/compare/activecampaign-vs-clevertap.json", "title": "ActiveCampaign vs CleverTap", "url": "https://www.anchorterminal.com/compare/activecampaign-vs-clevertap" }, { "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/braze-vs-clevertap.json", "title": "Braze vs CleverTap", "url": "https://www.anchorterminal.com/compare/braze-vs-clevertap" }, { "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/clevertap-vs-customer-io.json", "title": "CleverTap vs Customer.io", "url": "https://www.anchorterminal.com/compare/clevertap-vs-customer-io" }, { "json": "https://www.anchorterminal.com/compare/clevertap-vs-iterable.json", "title": "CleverTap vs Iterable", "url": "https://www.anchorterminal.com/compare/clevertap-vs-iterable" }, { "json": "https://www.anchorterminal.com/compare/clevertap-vs-klaviyo.json", "title": "CleverTap vs Klaviyo API + MCP", "url": "https://www.anchorterminal.com/compare/clevertap-vs-klaviyo" }, { "json": "https://www.anchorterminal.com/compare/clevertap-vs-mailchimp-marketing.json", "title": "CleverTap vs Mailchimp Marketing API", "url": "https://www.anchorterminal.com/compare/clevertap-vs-mailchimp-marketing" }, { "json": "https://www.anchorterminal.com/compare/clevertap-vs-moengage.json", "title": "CleverTap vs MoEngage", "url": "https://www.anchorterminal.com/compare/clevertap-vs-moengage" }, { "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/clevertap-vs-sequenzy.json", "title": "CleverTap vs Sequenzy", "url": "https://www.anchorterminal.com/compare/clevertap-vs-sequenzy" }, { "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/iterable-vs-nitrosend.json", "title": "Iterable vs Nitrosend", "url": "https://www.anchorterminal.com/compare/iterable-vs-nitrosend" }, { "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/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/moengage-vs-nitrosend.json", "title": "MoEngage vs Nitrosend", "url": "https://www.anchorterminal.com/compare/moengage-vs-nitrosend" }, { "json": "https://www.anchorterminal.com/compare/nitrosend-vs-omnisend.json", "title": "Nitrosend vs Omnisend", "url": "https://www.anchorterminal.com/compare/nitrosend-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/dreamlit-vs-nitrosend.json", "title": "Dreamlit vs Nitrosend", "url": "https://www.anchorterminal.com/compare/dreamlit-vs-nitrosend" }, { "json": "https://www.anchorterminal.com/compare/clevertap-vs-dreamlit.json", "title": "CleverTap vs Dreamlit", "url": "https://www.anchorterminal.com/compare/clevertap-vs-dreamlit" } ], "panel": null, "scores": [ { "by": 11, "clevertap": 37, "edge": "nitrosend", "key": "reliability", "name": "Reliability", "nitrosend": 48, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 36, "clevertap": 57, "edge": "nitrosend", "key": "schema", "name": "Schema \u0026 documentation", "nitrosend": 93, "weight": 13 }, { "by": 30, "clevertap": 53, "edge": "nitrosend", "key": "ergonomics", "name": "Agent ergonomics", "nitrosend": 83, "weight": 13 }, { "by": 6, "clevertap": 56, "edge": "nitrosend", "key": "security", "name": "Security \u0026 auth", "nitrosend": 62, "weight": 14 }, { "by": 30, "clevertap": 25, "edge": "nitrosend", "key": "payments", "name": "Payments \u0026 pricing", "nitrosend": 55, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 8, "clevertap": 73, "edge": "nitrosend", "key": "maintenance", "name": "Maintenance \u0026 community", "nitrosend": 81, "weight": 7 }, { "by": 7, "clevertap": 66, "edge": "nitrosend", "key": "transparency", "name": "Transparency \u0026 trust", "nitrosend": 73, "weight": 7 } ], "summary": "Nitrosend scores 69.4 (B) on agent readiness against CleverTap's 50.4 (D), and leads in every scored category. Both do marketing audiences.", "tasks": null, "tutorials": [], "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/clevertap-vs-nitrosend", "json": "https://www.anchorterminal.com/compare/clevertap-vs-nitrosend.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/clevertap-vs-nitrosend.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/clevertap-vs-nitrosend.min.md" }, "markdown": "Nitrosend scores 69.4 (B) on agent readiness against CleverTap's 50.4 (D), and leads in every scored category. Both do marketing audiences.\n\n- CleverTap: grade D, 50.4/100, rank #1066 of 1510. Markdown https://www.anchorterminal.com/tools/clevertap.md · JSON https://www.anchorterminal.com/api/v1/tools/clevertap.json\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- 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### CleverTap (D)\n\nGood 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.\n\nWatch for: No OpenAPI file was found. The contract is prose tables plus a Postman collection published as a zip on GitHub\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- Reliability, 48 against 37\n- Schema \u0026 documentation, 93 against 57\n- Agent ergonomics, 83 against 53\n- Security \u0026 auth, 62 against 56\n- Payments \u0026 pricing, 55 against 25\n- Maintenance \u0026 community, 81 against 73\n- Transparency \u0026 trust, 73 against 66\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: status.nitrosend.com answered 526 on 6 November 2026, so no incident history could be read\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Nitrosend +36\n\n- 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.\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\n### Agent ergonomics: Nitrosend +30\n\n- 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.\n- 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.\n\n### Payments \u0026 pricing: Nitrosend +30\n\n- 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.\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\n### Reliability: Nitrosend +11\n\n- 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.\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\n### Maintenance \u0026 community: Nitrosend +8\n\n- 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.\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\n### Transparency \u0026 trust: Nitrosend +7\n\n- 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.\n- 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.\n\n## Score by category\n\n| Category | Weight | CleverTap | Nitrosend | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 37 | 48 | Nitrosend +11 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 57 | 93 | Nitrosend +36 |\n| Agent ergonomics | 13% (16.2 this run) | 53 | 83 | Nitrosend +30 |\n| Security \u0026 auth | 14% (17.5 this run) | 56 | 62 | Nitrosend +6 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 55 | Nitrosend +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 73 | 81 | Nitrosend +8 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 73 | Nitrosend +7 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **50.4 · D** | **69.4 · B** | |\n\n## Facts side by side\n\n| Fact | CleverTap | Nitrosend |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | WizRocket Inc. | Nitrosend Pty Ltd |\n| Hosted endpoint | no (local only) | `https://api.nitrosend.com/mcp` |\n| Transports | HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | API key | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under CleverTap's Terms of Service. The Node.js API library on GitHub is MIT | none |\n| Tools exposed | none | 25 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `com.nitrosend/nitrosend` |\n| Last release | 2026-10-01 | 2026-11-06 |\n| Terms last updated | 2021-04-30 | 2026-11-04 |\n| Privacy policy last updated | 2026-04-09 | 2026-10-14 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | yes | not found in the text |\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 | 3k npm/wk | 1k npm/wk |\n\n## How the scores have moved\n\n### CleverTap\n\n- +1.4 on 4 November 2026: correction\n- +0.2 on 27 October 2026: checklist\n\n### Nitrosend\n\nNo score change since it was listed.\n\n## Verdicts\n\n**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.\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## Before you call either\n\n### CleverTap\n\n1. Call the host for the account's region, such as `in1.api.clevertap.com` or `us1.api.clevertap.com`. `api.clevertap.com` is the Europe region\n2. Send `X-CleverTap-Account-Id` and `X-CleverTap-Passcode` headers on every call, and ask for a named passcode with an expiry date\n3. Check `status` in the body as well as the HTTP code. Get User Profiles can answer 200 with `\"status\":\"fail\"` when throttled\n4. Add `dryRun=1` to an upload URL to validate up to 1,000 records without storing them\n5. Set `estimate_only` or `draft` to true on Create Campaign before a real send. API campaigns bypass dashboard role restrictions\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## Questions\n\n### Which is better for AI agents, CleverTap or Nitrosend?\n\nNitrosend scores 69.4 (B) on agent readiness against CleverTap's 50.4 (D), and leads in every scored category.\n\n### Do CleverTap and Nitrosend need an API key?\n\nCleverTap needs an API key. Nitrosend takes an API key or an OAuth sign-in.\n\n### Can an agent call CleverTap and Nitrosend without installing anything?\n\nNo hosted endpoint is listed for CleverTap. Nitrosend has a hosted endpoint at https://api.nitrosend.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/clevertap-vs-nitrosend.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clevertap-vs-nitrosend.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"clevertap\", \"b\": \"nitrosend\"}`. From a terminal: `anchor compare clevertap nitrosend`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clevertap.json and https://www.anchorterminal.com/api/v1/tools/nitrosend.json\n\n## Other comparisons with CleverTap or Nitrosend\n\n- [ActiveCampaign vs CleverTap](https://www.anchorterminal.com/compare/activecampaign-vs-clevertap.md)\n- [ActiveCampaign vs Nitrosend](https://www.anchorterminal.com/compare/activecampaign-vs-nitrosend.md)\n- [Braze vs CleverTap](https://www.anchorterminal.com/compare/braze-vs-clevertap.md)\n- [Braze vs Nitrosend](https://www.anchorterminal.com/compare/braze-vs-nitrosend.md)\n- [CleverTap vs Customer.io](https://www.anchorterminal.com/compare/clevertap-vs-customer-io.md)\n- [CleverTap vs Iterable](https://www.anchorterminal.com/compare/clevertap-vs-iterable.md)\n- [CleverTap vs Klaviyo API + MCP](https://www.anchorterminal.com/compare/clevertap-vs-klaviyo.md)\n- [CleverTap vs Mailchimp Marketing API](https://www.anchorterminal.com/compare/clevertap-vs-mailchimp-marketing.md)\n- [CleverTap vs MoEngage](https://www.anchorterminal.com/compare/clevertap-vs-moengage.md)\n- [CleverTap vs Omnisend](https://www.anchorterminal.com/compare/clevertap-vs-omnisend.md)\n- [CleverTap vs Sequenzy](https://www.anchorterminal.com/compare/clevertap-vs-sequenzy.md)\n- [Customer.io vs Nitrosend](https://www.anchorterminal.com/compare/customer-io-vs-nitrosend.md)\n- [Iterable vs Nitrosend](https://www.anchorterminal.com/compare/iterable-vs-nitrosend.md)\n- [Klaviyo API + MCP vs Nitrosend](https://www.anchorterminal.com/compare/klaviyo-vs-nitrosend.md)\n- [Mailchimp Marketing API vs Nitrosend](https://www.anchorterminal.com/compare/mailchimp-marketing-vs-nitrosend.md)\n- [MoEngage vs Nitrosend](https://www.anchorterminal.com/compare/moengage-vs-nitrosend.md)\n- [Nitrosend vs Omnisend](https://www.anchorterminal.com/compare/nitrosend-vs-omnisend.md)\n- [Nitrosend vs Sequenzy](https://www.anchorterminal.com/compare/nitrosend-vs-sequenzy.md)\n- [Dreamlit vs Nitrosend](https://www.anchorterminal.com/compare/dreamlit-vs-nitrosend.md)\n- [CleverTap vs Dreamlit](https://www.anchorterminal.com/compare/clevertap-vs-dreamlit.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": "CleverTap vs Nitrosend", "url": "" } ], "description": "Nitrosend scores 69.4 (B) to CleverTap's 50.4 (D) for marketing audiences. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "CleverTap D 50.4", "Nitrosend B 69.4", "scores" ], "h1": "CleverTap vs Nitrosend", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/clevertap-vs-nitrosend", "published": "2026-10-01", "section": "tools", "title": "CleverTap vs Nitrosend for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/clevertap-vs-nitrosend" }, "tokens": { "markdown": 4800, "slim": 2980 }, "version": 1 }