# Fix list: CleverTap From Anchor Terminal's listing at https://www.anchorterminal.com/tools/clevertap, the October 2026 research run, assessed 9 October 2026. Grade D, 48.8 out of 100. This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public. For a coding agent working on CleverTap: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published. ## 1. Reliability, 30 out of 100, up to 14 more on the total Why it scored 30: 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, and no address was guessed, so the status page (0) and the incident record (0) score as absent. Concurrent request limits are published with numbers for 23 API groups (15 on uploads, 3 elsewhere) with 1,000 records a call, but the Create Campaign page gives 3 requests a second and the Get User Profiles page says limits are account-specific (13). HTTP 429 is documented, 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. No Retry-After header or idempotency key was found (8). The terms 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 (9). Total 30. The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability): Hosted APIs, MCP servers, models and platforms. - 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own). - 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so. - 15, rate limits documented with numbers. - 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved. - 10, an SLA published for any paid tier. - 10, the surface agents use is generally available, not beta or preview. Local packages, SDKs, frameworks and stdio MCP servers. - 20, installs from an official package with supported runtimes stated. - 25, a public CI and test suite, passing on the default branch. - 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered). - 15, semver discipline and breaking changes called out in a changelog. - 15, version 1.0 or later, or declared stable. Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors. ## 2. Payments & pricing, 25 out of 100, up to 9.4 more on the total Why it scored 25: No x402, MPP or L402 (0). The Core plan's entry price is public at 85 dollars a month 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. The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments): The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/). - 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which. - 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login. - 20, a free tier or trial that doesn't need a card. - 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API). Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied. Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol. ## 3. Security & auth, 56 out of 100, up to 7.7 more on the total Why it scored 56: Up to 100 named account passcodes with optional expiry, shown once and deletable, or per-user passcodes an admin can reset and revoke. No scopes or OAuth were found, and the secret travels in a header (22). No read-only passcode was found. The docs say campaigns created via API are not restricted by RBAC settings. A dashboard approval workflow exists, and `draft` lets an API caller save without sending (6). The API returns customer-supplied profile and event content, and no guidance for agents reading it was found (3). Audit logs record API key creation and revocation and API access logs, with CSV download and a daily export for SIEM tools (13). ISO/IEC 27001, ISO/IEC 27017, SOC 2 Type II, CSA STAR Level 2 and HIPAA are named on the pricing and security pages. No security.txt, disclosure policy or bug bounty was found, and the trust portal answered 403 (12). Total 56. The checklist (https://www.anchorterminal.com/benchmark/#checklist-security): - 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option. - 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions. - 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10. - 0 to 15, audit logs or per-call visibility for the operator. - 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public. Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing. ## 4. Agent ergonomics, 53 out of 100, up to 7.6 more on the total Why it scored 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. The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics): - 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries). - 20, pagination, filtering and output-size controls. - 20, actionable, documented error responses, codes and messages an agent can recover from. - 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations. - 15, sensible defaults, few required parameters, and official SDKs in at least two languages. Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs. ## 5. Schema & documentation, 57 out of 100, up to 7 more on the total Why it scored 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. The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema): APIs and MCP servers. - 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool). - 10, llms.txt or Markdown docs served for agents. - 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference. - 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs. - 0 to 15, examples and documented error responses. - 15, versioning and a public changelog. Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference. ## 6. Transparency & trust, 64 out of 100, up to 3.2 more on the total Made of editorial 50, provenance 78. Why it scored 64: Closed service with public Terms of Service, last updated 30 April 2021, that name WizRocket Inc. and state the restrictions plainly (15). The privacy policy of 9 April 2026 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. The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency): - 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms. - 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors). - 0 to 20, a deprecation policy or notices with dates. - 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted). The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two. Provenance checks not met in full (half of this category, computed from checked facts): - Terms of service: read, states 7 of the 7 things a reader expects, and has 1 clause that costs points (8 of 10) - Status page: not found (0 of 10) - security.txt: not found (0 of 10) ## 7. Maintenance & community, 73 out of 100, up to 2.4 more on the total Why it scored 73: The Android SDK repository has a tag dated 1 October 2026 and the Web SDK one dated 7 September (30). The Web SDK has six tags since 11 July and the Android SDK three (20). Public monthly SDK changelogs 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 had a fix on 7 July 2026 after three years without a release, 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). Total 73. The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance): - 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older. - 20, at least three releases or dated changelog entries in the last 90 days. - 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15. - 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models). - 10, package health, current dependencies and CI. Models are read for deprecation notice periods and model churn rather than release counts. ## What we couldn't check What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it. - unchecked: https://trust.clevertap.com/ answered 403 and was not retried, so the sub-processor list, audit reports and any disclosure policy there are unread and scored as absent - unchecked: whether CleverTap runs a public status page. None is linked from the home page, the pricing, security, terms or privacy pages or either docs index, and no address was guessed. A status page with a clean record would add up to 50 points to Reliability - unchecked: prices for the Core tiers above 5,000 monthly active users, which the pricing page sets by script - unchecked: the Postman collection zip in CleverTap/clevertap-snippets, so its coverage of the API is unknown - unchecked: GitHub issues and CI results for the SDK and library repositories. Tags and commit dates were read from clones - unchecked: the Terms of Service for C4S (the startup plan) and the Data Processing Addendum, which was not found in public - Whether the campaign approval workflow holds campaigns created through the API was not stated on the page read. The RBAC page says API-created campaigns are not restricted by RBAC settings - The Terms of Service bar customers from publicly disseminating information regarding the performance of the Services (section 2.3 f). Recorded as a fact with no deduction. It matters before any probe is run - The rate limit statements disagree. The request limit page says no time-based limits, the Create Campaign page says 3 requests a second, and the Get User Profiles page says limits are account-specific - No MCP server was found in either docs index or the official MCP registry. The lead's facts held, and its docs link is the SDK and API docs home - provenance.statusPage is empty because no status page was found ## 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 ## What costs an agent a turn today The notes we give agents before they call it. Each one is a workaround an agent shouldn't need. - 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 ## When it's done Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.