# Fix list: Zoho CRM From Anchor Terminal's listing at https://www.anchorterminal.com/tools/zoho-crm, the October 2026 research run, assessed 8 October 2026. Grade BB, 70.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 Zoho CRM: 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. Payments & pricing, 40 out of 100, up to 7.5 more on the total Why it scored 40: No x402, MPP or L402 (0). Edition prices are public, $14 to $52 a user a month billed yearly, and extra API credits have a published unit price from $0.14 per 1,000 a day (20). The Free edition covers three users with 5,000 API credits a day and needs no card at signup (20). A person signs up in a browser, registers an OAuth client in the API console and approves scopes (0). 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. ## 2. Security & auth, 67 out of 100, up to 5.8 more on the total Why it scored 67: OAuth 2.0 with scopes down to one module and one operation, one-hour access tokens and revocable refresh tokens (30). Less 10 because the documented refresh and revoke calls carry the refresh token and client secret in the URL query string (20 of 30). READ-only scopes per module and a read-only Data Insights MCP server. Calls are also bound by the user's CRM role. No approval step for deletes, and mass delete exists (14 of 20). Records hold text from outside parties and no prompt-injection guidance was found (3 of 15). Audit Logs in paid editions, and an API dashboard of credits by application (10 of 15). security.txt valid to 30 June 2028, a bug bounty, SOC 2 Type 2 and ISO/IEC 27001, 27701 and 27017 (20). 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. ## 3. Reliability, 72 out of 100, up to 5.6 more on the total Why it scored 72: Graded on the REST API v8, read as a hosted service. status.zoho.com redirects to us.zohostatus.com, which has a Zoho CRM component and incident history back to November 2025 (20). No incident in the last 90 days names CRM. On 3 September 2026 a Zoho Deluge outage ran 2 hours 34 minutes and the status feed shows the CRM component changing state when it ended, so we read the record as minor incidents only (20 of 30). Only the US page was read. Daily credits and concurrency are published with numbers per edition (15). 429 is documented and `X-API-CREDITS-REMAINING` appears once half the allowance is used, but no Retry-After or backoff guidance was found. Upsert and `If-Unmodified-Since` make writes safer to retry (7 of 15). No SLA found (0). v8 is the current documented version (10). 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. ## 4. Schema & documentation, 81 out of 100, up to 3.1 more on the total Why it scored 81: zoho/crm-oas on GitHub holds OpenAPI 3.1 files for 103 resources and 644 operations (25). No llms.txt at zoho.com, but the same repository carries a compressed Markdown page and examples per operation, written for Zoho's CRM agent skills (7 of 10). Operation descriptions state the purpose and name the call that supplies each ID, with little on when not to use one (15 of 20). Parameters carry enums, patterns and length limits. Record bodies accept any property because modules have custom fields, and search criteria are a string grammar (11 of 15). Each reference page has curl samples and a Possible Errors list with a resolution per code (15). The version is in the path, and What's New in V8 lists changes without dates. No dated changelog found (8 of 15). 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. ## 5. Agent ergonomics, 81 out of 100, up to 3.1 more on the total Why it scored 81: Graded on the REST API. `fields` is mandatory on list calls with at most 50 names, and COQL selects columns, so responses can be kept small (22 of 25). `per_page` up to 200, `page` to 2,000 records and `page_token` to 100,000, plus search by criteria, email, phone or word, custom views and COQL (20). Errors carry a code, a message and details naming the field or the existing record, each documented with a resolution (18 of 20). Upsert on duplicate check fields and `If-Unmodified-Since`, with no idempotency key (10 of 20). Official SDKs in six languages, but the one-hour token, the refresh step and per-data-centre hosts add setup (11 of 15). 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. ## 6. Transparency & trust, 75 out of 100, up to 2.2 more on the total Made of editorial 54, provenance 95. Why it scored 75: Closed service under the Zoho Terms of Service, last updated 2 March 2022, with Apache-2.0 SDKs (15 of 30). The privacy policy of 22 December 2025 says Zoho does not sell personal information, and that data is deleted from the active database within six months of account termination and from backups three months later. The DPA is sent on request by email (24 of 30). No API deprecation policy or dated notices found (0). A sub-processor page exists, but its directory loads by script and we could not read the list. The data centre page names locations and their certifications (15 of 20). 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 6 of the 7 things a reader expects, and has 1 clause that costs points (7.1 of 10) - Privacy policy: read, states 8 of the 8 things a reader expects, and has 1 clause that costs points (8 of 10) ## 7. Maintenance & community, 77 out of 100, up to 2 more on the total Why it scored 77: The Node.js SDK for v8 reached 4.0.0 on 21 September 2026, 17 days before this check (30). Three dated changes in the last 90 days, Python SDK 7.0.0 on 24 July, the OpenAPI files on 2 September and Node.js SDK 4.0.0 on 21 September (20). No dated API changelog. The docs link to community posts on help.zoho.com, which we did not test for replies (8 of 25). Current official SDKs for Java, Python, PHP, Node.js, C# and Ruby (15). The SDK repositories show no public CI, and the Java SDK was last released on 7 January 2026 (4 of 10). 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: GitHub star counts for the SDK and OpenAPI repositories, the repositories were cloned and the web pages not read - unchecked: the sub-processor directory at zoho.com/privacy/sub-processors.html, which loads by script - unchecked: status pages for data centres other than the US - unchecked: the number and definitions of tools on the four MCP servers, which need a signed-in session - unchecked: whether the CRM REST API was affected during the Deluge outage of 3 September 2026 - No SLA page, API deprecation policy or dated API changelog was found. Zoho may publish version retirement notices in its community forum, which we did not search - Whether failed calls and 429 responses use credits is not stated in the reviewed pages - The lead was right on the vendor, URL, docs link and interface. It did not mention the four MCP servers ## Weaknesses - The documented refresh and revoke calls put the refresh token and client secret in the URL query string - No SLA, API deprecation policy or dated API changelog found in the reviewed pages - 429 is documented without a Retry-After header or backoff guidance - Access tokens last one hour and hosts differ by data centre, so setup needs a token exchange and the right domain - Sub-processor directory loads by script and the DPA is sent on request by email ## 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. - Use the `api_domain` returned with the token, since each data centre has its own host (zohoapis.com, zohoapis.eu, zohoapis.in and others) - Send `Authorization: Zoho-oauthtoken ` and refresh hourly. Put refresh parameters in the POST body, not the URL - Pass `fields` on every list call. Page with `page` up to 2,000 records, then `page_token` up to 100,000 - Create through `/{module}/upsert` so a retry updates instead of duplicating - Budget credits. Convert Lead costs 5, Send Mail 20, a bulk read 50, and calls through the MCP servers draw on the same allowance ## 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.