Relaticle vs Zoho CRM

Relaticle 40

Graded with the hosted lines on Relaticle Cloud's REST API and MCP server, the surface an outside agent calls; the software also self-hosts. No status page is linked and status.relaticle.com did not connect (0). With no readable history the incident line scores 5. Limits have numbers: 600 a minute per workspace and 300 reads or 60 writes a minute per token in the source, and 120 MCP calls a minute per user in the docs (15). 429 is in the OpenAPI responses and upserts by unique field give a safe retry for creates, but the backoff guidance sits on a docs section we read only as a heading (10 of 15). No SLA (0). Version 3.8, not labelled beta (10). 0 + 5 + 15 + 10 + 0 + 10 = 40.

Zoho CRM 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 December 2025 (20). From 3 August to 1 November the history lists 21 incidents across Zoho services, most of them a few minutes long. One touches CRM: on 24 October a multi-service outage ("Qntrl and a few other components") ran 16 minutes 16 seconds, and the status feed shows the Zoho CRM component returning to Operational at 18:12 IST within it. On 3 September a Zoho Deluge outage ran 2 hours 34 minutes, and the CRM component's state changed when it ended. Both read as partial, so 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).

Relaticle 59

50 MCP tools, six schema resources and a prompt, with no toolsets or read-only subset (5). Filters combine native fields, custom fields and linked records with $and, $or and $not, plus sort, include, per_page (MCP maximum 25) and cursors (20). Errors come back as HTTP codes and inline MCP error responses such as Invalid ability provided.; no error catalogue was read (12 of 20). Base tool classes set readOnlyHint, destructiveHint, idempotentHint and openWorldHint, and upserts by unique field make creates safe to retry (17 of 20). One URL with OAuth or a token; no official SDK (5 of 15). 5 + 20 + 12 + 17 + 5 = 59.

Zoho CRM 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).

Relaticle 90

v3.8.2 tagged on 5 November 2026 and commits on 6 November (30). Thirteen tags between 9 October and 5 November alone (20). More than 2,500 commits since 1 August and merged pull requests numbered past 1,100; the GitHub API did not answer, so open issues and reply times were not counted (15 of 25). Verified com.relaticle/crm namespace in the official MCP registry with the hosted remote (15). CI, tests, security-audit and Dependabot workflows, PHP 8.5 and Laravel 13 (10). 30 + 20 + 15 + 15 + 10 = 90.

Zoho CRM 77

The Node.js SDK for v8 reached 5.0.0 on 15 October 2026 (30). Three dated changes from 3 August to 1 November, the OpenAPI files on 2 September, Node.js SDK 4.0.0 on 21 September and 5.0.0 on 15 October. Python SDK 7.0.0 of 24 July has left the window (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 and the Ruby SDK on 16 April 2025 (4 of 10).

Relaticle 57

Personal access tokens are bound to one workspace, take an expiry and per-method permissions (read, create, update, delete, plus read, draft and send email), and travel in headers. OAuth 2.1 through Passport is also offered, but the source says its single mcp:use scope authorises the whole toolset (25 of 30). A read-only token is possible; the docs say MCP writes apply immediately and leave confirmation to the client (10 of 20). Synced email reaches the model through the email tools, and no prompt-injection guidance was found (0). Each record has an activity log of field changes and who made them, and admins see it across the workspace (12 of 15). security.txt valid to May 2027, a disclosure address with a 48-hour acknowledgement target and security-audit workflows in CI; the security page says there is no SOC 2 or ISO 27001 (10 of 20). 25 + 10 + 0 + 12 + 10 = 57.

Zoho CRM 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).

Relaticle 30

No x402, MPP or L402 (0). Cloud prices are public per workspace with nothing per call (10). A 14-day Cloud Pro trial with no card, and self-hosting is free (20). A person signs up in a browser behind a Cloudflare check, or deploys a server (0). 0 + 10 + 20 + 0 = 30.

Zoho CRM 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).

Relaticle 86

OpenAPI 3.1 at /openapi.json and /openapi.yaml with 34 operations (25). llms.txt with a when-to-use and when-not section, and developer pages (10). The llms.txt and MCP docs say what the API is for and what it doesn't do (no email over REST, no meetings), while only 5 of 34 operations carry a description (14 of 20). 114 required lists and typed MCP inputs, but few enums (11 of 15). 661 examples and responses for 401, 402, 403, 404, 409, 422 and 429 (14 of 15). /v1 and frequent tagged releases, with no changelog page (relaticle.com/changelog is 404) (12 of 15). 25 + 10 + 14 + 11 + 14 + 12 = 86.

Zoho CRM 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).