# Freshsales API vs Relaticle (slim)

> Relaticle scores 59.6 (C) to Freshsales's 40.7 (E) for crm records. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/freshsales-vs-relaticle.md (~4,250 tokens) · this version ~2,230 tokens · JSON https://www.anchorterminal.com/compare/freshsales-vs-relaticle.json · canonical https://www.anchorterminal.com/compare/freshsales-vs-relaticle
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Relaticle scores 59.6 (C) on agent readiness against Freshsales API's 40.7 (E), and leads in 4 of 7 scored categories. Freshsales API leads on reliability. Both do crm records.

- Freshsales API: E 40.7, rank #1316 of 1510 · https://www.anchorterminal.com/tools/freshsales.min.md
- Relaticle: C 59.6, rank #697 of 1510 · https://www.anchorterminal.com/tools/relaticle.min.md
- Freshsales API, good for Small teams already paying for Freshworks who want an agent to upsert contacts and log activities through REST. Ahead on Reliability, 51 against 40.
- Relaticle, good for Small teams who want an open-source CRM they can self-host and let an agent write to. Ahead on Schema & documentation, 86 against 27; Agent ergonomics, 59 against 48; Security & auth, 57 against 44; Maintenance & community, 90 against 5. Also A hosted endpoint, with nothing to install; Open source.

| Category | Freshsales API | Relaticle |
| --- | --- | --- |
| Reliability (16%) | 51 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 27 | 86 |
| Agent ergonomics (13%) | 48 | 59 |
| Security & auth (14%) | 44 | 57 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 5 | 90 |
| Transparency & trust (7%) | 73 | 73 |

| Fact (where they differ) | Freshsales API | Relaticle |
| --- | --- | --- |
| Vendor | Freshworks | Relaticle, Inc. |
| Hosted endpoint | no (local only) | `https://mcp.relaticle.com` |
| Transports | HTTP | Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| Licence | none | AGPL-3.0 |
| Tools exposed | none | 50 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| MCP registry | not listed | `com.relaticle/crm` |
| Last release | none | 2026-11-05 |
| Terms last updated | 2026-04-01 | 2026-08-26 |
| Privacy policy last updated | no date given | 2026-11-04 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | none | 1.8k stars |
| Agent reviews | 2/5 (2) | none |

Why the edge:
- Maintenance & community, Relaticle +85: Freshsales API 5 (No public API changelog or release notes for the Freshsales API found, so no last change date (0). No dated entries in the last 90 days found (0). Freshworks runs community forums, but there's no API changelog to follow (5 of 15). No official Freshsales SDK. The FDK is for marketplace apps, not API calls (0). No packages to judge (0). Freshworks' MCP work, GA on 10 September 2026, covers Freshservice, not Freshsales.); 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.)
- Schema & documentation, Relaticle +59: Freshsales API 27 (No OpenAPI or other machine-readable spec found (0). No llms.txt or Markdown docs (0). One long HTML reference page with short endpoint descriptions and no when-not-to-use guidance (8 of 20). Field tables and filter bodies, with free-form filter JSON for views and search (8 of 15). curl examples throughout, an error format of `errors.code` and `errors.message` and a list of status codes (11 of 15). No version scheme or API changelog found (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.)
- Security & auth, Relaticle +13: Freshsales API 44 (One per-user API key in `Authorization: Token token=<key>`, limited by that user's role and visibility. No scopes, no OAuth for the CRM API, and we found no rotation docs (13 of 30). No read-only key. Access is whatever the user's role allows, and bulk delete endpoints exist (3 of 20). Records carry email, notes and chat text from outside parties, and we found no injection guidance (3 of 15). Audit logs listed on the Enterprise plan (8 of 15). HackerOne disclosure programme, a security.txt with contact and policy (no Expires field), and ISO, AICPA and Cyber Essentials Plus logos on the security page (17 of 20).); 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.)
- Reliability, Freshsales API +11: Freshsales API 51 (Freshworks runs its own status page at status.freshworks.com across products and regions, but it renders only with JavaScript and its incidents API returned 403, so we couldn't see a Freshsales component (15 of 20). No readable incident history (5). 1,000 API requests an hour per account, published (15). 429 is documented, with no Retry-After or backoff guidance. Contact upsert and bulk upsert make creates safe to retry (6 of 15). No SLA found on the pricing page (0). The REST API is GA (10).); 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.)
- Agent ergonomics, Relaticle +11: Freshsales API 48 (No MCP server for Freshsales. `include` embeds related records on request and lists default to 25 per page. No field selection to trim responses (10 of 25). `page` pagination, filtered views, search and filter endpoints (14 of 20). Errors carry a code and a message, with status codes documented (12 of 20). `/api/contacts/upsert` and `bulk_upsert` (100 records a request) give idempotent creates for contacts, but nothing similar for deals. `bulk_destroy` deletes in bulk (8 of 20). Every account has its own host, so an agent needs the bundle alias as well as the key, and there's no official SDK (4 of 15).); 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.)