# Freshsales API vs Relaticle

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

- Canonical: https://www.anchorterminal.com/compare/freshsales-vs-relaticle
- Markdown: https://www.anchorterminal.com/compare/freshsales-vs-relaticle.md (~4,250 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

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: grade E, 40.7/100, rank #1316 of 1510. Markdown https://www.anchorterminal.com/tools/freshsales.md · JSON https://www.anchorterminal.com/api/v1/tools/freshsales.json
- Relaticle: grade C, 59.6/100, rank #697 of 1510. Markdown https://www.anchorterminal.com/tools/relaticle.md · JSON https://www.anchorterminal.com/api/v1/tools/relaticle.json
- Best CRM and customer-platform tools for AI agents: https://www.anchorterminal.com/best/crm/index.md
- All 190 crm comparisons: https://www.anchorterminal.com/compare/crm/index.md

## Which one, for what

### Freshsales API (E)

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

Watch for: No MCP server for Freshsales

### Relaticle (C)

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 in its favour:
- A hosted endpoint, with nothing to install
- Open source

Watch for: Writes over MCP apply immediately, and OAuth's single `mcp:use` scope authorises every tool


## 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.

## Score by category

| Category | Weight | Freshsales API | Relaticle | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 51 | 40 | Freshsales API +11 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 27 | 86 | Relaticle +59 |
| Agent ergonomics | 13% (16.2 this run) | 48 | 59 | Relaticle +11 |
| Security & auth | 14% (17.5 this run) | 44 | 57 | Relaticle +13 |
| Payments & pricing | 10% (12.5 this run) | 30 | 30 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 5 | 90 | Relaticle +85 |
| Transparency & trust | 7% (8.8 this run) | 73 | 73 | even |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **40.7 · E** | **59.6 · C** | |

## Facts side by side

| Fact | Freshsales API | Relaticle |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| 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 |
| x402 | no | no |
| 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 automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | 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 |

## How the scores have moved

### Freshsales API

- +0.1 on 27 October 2026: checklist
- -0.2 on 8 October 2026: checklist

### Relaticle

No score change since it was listed.

## Verdicts

**Freshsales API.** Contact upsert and bulk upsert of up to 100 records make creates safe to retry. No MCP server for Freshsales.

**Relaticle.** Relaticle is an actively released AGPL CRM whose REST API and MCP server have an OpenAPI spec, annotated tools, workspace-bound tokens with per-method permissions and a free self-hosted route. MCP writes apply at once with no server-side confirmation, OAuth grants the whole toolset, and Cloud has no status page, SLA or certification.

## Before you call either

### Freshsales API

1. Build the base URL from the bundle alias shown under the API key, `https://<alias>.myfreshworks.com/crm/sales/api/`
2. Use `/api/contacts/upsert` rather than create, so a retry updates instead of duplicating
3. Budget calls, since 1,000 an hour covers the whole account and 429s carry no Retry-After
4. Add `include=owner,sales_accounts` to pull related records in one call
5. Expect to see only what the key owner's role can see

### Relaticle

1. Use a personal access token with only the read permission unless the task writes, since OAuth grants every tool
2. Ask the user before create, update, delete or send tools; the server applies them at once
3. Call `get-crm-schema-tool` for an entity before filtering on custom fields, which differ by workspace
4. Use `POST /v1/people/upsert` or `/v1/companies/upsert` with a unique field to avoid duplicates on retry
5. Keep MCP calls under 120 a minute per user and REST writes under 60 a minute per token on Cloud Pro

## Questions

### Which is better for AI agents, Freshsales API or Relaticle?

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.

### Do Freshsales API and Relaticle need an API key?

Freshsales API needs an API key. Relaticle takes an API key or an OAuth sign-in.

### Can an agent call Freshsales API and Relaticle without installing anything?

No hosted endpoint is listed for Freshsales API. Relaticle has a hosted endpoint at https://mcp.relaticle.com.

### Are Freshsales API and Relaticle open source?

No open-source release is listed for Freshsales API. Relaticle is open source (AGPL-3.0).


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/freshsales-vs-relaticle.json, and with the fewest tokens: https://www.anchorterminal.com/compare/freshsales-vs-relaticle.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "freshsales", "b": "relaticle"}`. From a terminal: `anchor compare freshsales relaticle`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/freshsales.json and https://www.anchorterminal.com/api/v1/tools/relaticle.json

## Other comparisons with Freshsales API or Relaticle

- [Affinity vs Freshsales API](https://www.anchorterminal.com/compare/affinity-vs-freshsales.md)
- [Affinity vs Relaticle](https://www.anchorterminal.com/compare/affinity-vs-relaticle.md)
- [Attio API + MCP vs Freshsales API](https://www.anchorterminal.com/compare/attio-vs-freshsales.md)
- [Attio API + MCP vs Relaticle](https://www.anchorterminal.com/compare/attio-vs-relaticle.md)
- [Breakcold vs Freshsales API](https://www.anchorterminal.com/compare/breakcold-vs-freshsales.md)
- [Breakcold vs Relaticle](https://www.anchorterminal.com/compare/breakcold-vs-relaticle.md)
- [Capsule CRM vs Freshsales API](https://www.anchorterminal.com/compare/capsule-crm-vs-freshsales.md)
- [Capsule CRM vs Relaticle](https://www.anchorterminal.com/compare/capsule-crm-vs-relaticle.md)
- [Close API + MCP vs Freshsales API](https://www.anchorterminal.com/compare/close-vs-freshsales.md)
- [Close API + MCP vs Relaticle](https://www.anchorterminal.com/compare/close-vs-relaticle.md)
- [Copper API vs Freshsales API](https://www.anchorterminal.com/compare/copper-vs-freshsales.md)
- [Copper API vs Relaticle](https://www.anchorterminal.com/compare/copper-vs-relaticle.md)
- [Microsoft Dynamics 365 Sales vs Freshsales API](https://www.anchorterminal.com/compare/dynamics-365-sales-vs-freshsales.md)
- [Microsoft Dynamics 365 Sales vs Relaticle](https://www.anchorterminal.com/compare/dynamics-365-sales-vs-relaticle.md)
- [folk API + MCP vs Freshsales API](https://www.anchorterminal.com/compare/folk-vs-freshsales.md)
- [folk API + MCP vs Relaticle](https://www.anchorterminal.com/compare/folk-vs-relaticle.md)
- [Freshsales API vs HubSpot API + MCP](https://www.anchorterminal.com/compare/freshsales-vs-hubspot-mcp.md)
- [Freshsales API vs Nutshell](https://www.anchorterminal.com/compare/freshsales-vs-nutshell.md)
- [Freshsales API vs Payani AI](https://www.anchorterminal.com/compare/freshsales-vs-payani-ai.md)
- [Freshsales API vs Pipedrive API + MCP](https://www.anchorterminal.com/compare/freshsales-vs-pipedrive.md)
- [Freshsales API vs Salesflare](https://www.anchorterminal.com/compare/freshsales-vs-salesflare.md)
- [Freshsales API vs Salesforce API + MCP](https://www.anchorterminal.com/compare/freshsales-vs-salesforce.md)
- [Freshsales API vs Streak API + MCP](https://www.anchorterminal.com/compare/freshsales-vs-streak.md)
- [Freshsales API vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/freshsales-vs-sugarcrm.md)
- [Freshsales API vs Twenty API + MCP](https://www.anchorterminal.com/compare/freshsales-vs-twenty.md)
- [Freshsales API vs Zoho CRM](https://www.anchorterminal.com/compare/freshsales-vs-zoho-crm.md)
- [HubSpot API + MCP vs Relaticle](https://www.anchorterminal.com/compare/hubspot-mcp-vs-relaticle.md)
- [Nutshell vs Relaticle](https://www.anchorterminal.com/compare/nutshell-vs-relaticle.md)
- [Payani AI vs Relaticle](https://www.anchorterminal.com/compare/payani-ai-vs-relaticle.md)
- [Pipedrive API + MCP vs Relaticle](https://www.anchorterminal.com/compare/pipedrive-vs-relaticle.md)
- [Relaticle vs Salesflare](https://www.anchorterminal.com/compare/relaticle-vs-salesflare.md)
- [Relaticle vs Salesforce API + MCP](https://www.anchorterminal.com/compare/relaticle-vs-salesforce.md)
- [Relaticle vs Streak API + MCP](https://www.anchorterminal.com/compare/relaticle-vs-streak.md)
- [Relaticle vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/relaticle-vs-sugarcrm.md)
- [Relaticle vs Twenty API + MCP](https://www.anchorterminal.com/compare/relaticle-vs-twenty.md)
- [Relaticle vs Zoho CRM](https://www.anchorterminal.com/compare/relaticle-vs-zoho-crm.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp