# Relaticle vs Salesflare

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

- Canonical: https://www.anchorterminal.com/compare/relaticle-vs-salesflare
- Markdown: https://www.anchorterminal.com/compare/relaticle-vs-salesflare.md (~5,050 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 Salesflare's 37.8 (F), and leads in 6 of 7 scored categories. Both do crm records.

- 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
- Salesflare: grade F, 37.8/100, rank #1372 of 1510. Markdown https://www.anchorterminal.com/tools/salesflare.md · JSON https://www.anchorterminal.com/api/v1/tools/salesflare.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

### Relaticle (C)

Good for: Small teams who want an open-source CRM they can self-host and let an agent write to.

Ahead on:
- Reliability, 40 against 18
- Schema & documentation, 86 against 57
- Agent ergonomics, 59 against 49
- Security & auth, 57 against 44
- Maintenance & community, 90 against 5
- Transparency & trust, 73 against 58

Also in its favour:
- Open source

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

### Salesflare (F)

Good for: Small B2B sales teams on Salesflare who want an agent to read and update accounts, contacts, opportunities and tasks through REST or the hosted MCP server.

Watch for: No rate limit numbers found. The API introduction lists 429 among its status codes with no limit, Retry-After or backoff guidance


## Why the edge

### Maintenance & community: Relaticle +85

- 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.
- Salesflare (5): No API changelog or release notes found. The 9 October recency credit rested on the spec file's Last-Modified header (8 October), and on 4 November the same header read 4 November 2026 with the operation count unchanged, so it is a deployment stamp that records no change and sets no recency (20 to 0). No dated changelog entries (0). Support by chat and email per the help centre, untested, and no public issue tracker for the API (5 of 25). No official SDK. No official MCP registry entry was read (0). No packages to judge (0). Total 5.

### Schema & documentation: Relaticle +29

- 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.
- Salesflare (57): Public Swagger 2.0 file with 71 operations, linked as a download from the API introduction ("You can download it here") and from `llms.txt`, re-read on 4 November (25). `llms.txt` on the main site and help centre, with a Markdown twin for every page. The API reference itself is a Redoc page drawn from the spec (10). 17 of 71 operations have a description, and most repeat the summary (5 of 20). Enums, formats, minimums and required fields are widespread, but custom fields travel as a string, alternatives use a non-standard `x-alternatives` key, and the help centre says phone number arrays are not well described (10 of 15). No examples. 47 operations document only a `default` response, and errors appear only as a table of five status codes (4 of 15). The spec is version 1.0.0 with no changelog. Old fields are marked deprecated in their descriptions (3 of 15). Total 57.

### Reliability: Relaticle +22

- 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.
- Salesflare (18): Read with the hosted lines. Salesflare links a status page at status.salesflare.com, but on 4 November its robots.txt answered an empty 406, which this run reads as a refusal (as pipedrive's), so the 9 October readings of its components and history are struck and the line has no readable component history (20 to 0). No part of the window from 6 August could be read (30 to 5). No rate limit numbers found (0). The API introduction, re-read on 4 November, lists 429 with no Retry-After or backoff guidance, and there are no idempotency keys. `update_if_exists` on account creation and `force=false` on contact creation allow a safe retry of two writes (3 of 15, partial kept). No SLA found, and the terms promise reasonable endeavours without a figure (0). The REST API carries no beta label (10). 0+5+0+3+0+10 = 18.

### Transparency & trust: Relaticle +15

- Relaticle (73): AGPL-3.0 source with an integration exception, and terms for the Cloud service (30). The privacy policy (4 November 2026) gives retention for server logs (90 days), contact forms (12 months) and paused trial workspaces (deleted after 60 days with notice), and names provider categories; no DPA was found (20 of 30). No deprecation policy or dated notices found (5 of 20). The security page lists each Cloud provider and what it receives, with hosting at Hetzner in Germany, and website analytics through Fathom without CRM content (17 of 20). 30 + 20 + 5 + 17 = 72.
- Salesflare (58): Closed service with terms, re-read on 4 November and still undated, that name Salesflare BVBA in Antwerp and Belgian law (15). The terms promise daily backups and processing only on the customer's instructions, and the help centre places data on Google Cloud in St. Ghislain, Belgium. The DPA is supplied on request, the privacy policy could not be read, and no retention period after termination was found (12 of 30). Spec fields are marked deprecated with their replacements, with no dates or policy (5 of 20). Hosting provider and location are disclosed. No subprocessor list was found (8 of 20). Total 40.

### Security & auth: Relaticle +13

- 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.
- Salesflare (44): REST uses API keys sent as a Bearer header, created in Settings with no documented scopes, expiry or rotation. The MCP server uses OAuth authorisation code with PKCE (S256) and dynamic client registration, and its metadata lists only `openid` and `offline_access`, so tokens are not scoped by resource (22 of 30). Viewer, team member, manager and admin roles with data scopes exist on the Pro plan, but whether an API key inherits its creator's role is not documented. The MCP guide tells users to start with read-only requests and review writes (8 of 20). Account feeds return email and message content, with no injection guidance found (3 of 15). No audit log found (0). A disclosure programme with bounties generally of $20 to $80 and reports to security@salesflare.com (re-read on 4 November), CASA Tier 2 verification revalidated yearly and testing by an independent lab per the help centre. No SOC 2 or ISO 27001 of its own and no security.txt (11 of 20). Total 44.

### Agent ergonomics: Relaticle +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.
- Salesflare (49): Graded on the REST API. The MCP tool definitions sit behind OAuth and were not read. Lists take `limit` and `offset`, and `details=false` on accounts and opportunities trims the response, with no field selection (14 of 25). `search`, `order_by`, typed field filters and a `q` rule builder on every main list, with no documented maximum page size or total count (16 of 20). The docs list five status codes without causes and 47 operations type their response only as `default`; the 9 October reading of an error body came from an unauthenticated request to the API, which is struck. The status-code table still partly meets the line, so the earlier partial is kept (8 of 20, partial kept). No idempotency keys. `update_if_exists` and `force=false` cover account and contact creation only (5 of 20). Few required fields, and no official SDK was found among the vendor's 47 public repositories (6 of 15). 14+16+8+5+6 = 49.

## Score by category

| Category | Weight | Relaticle | Salesflare | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 40 | 18 | Relaticle +22 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 86 | 57 | Relaticle +29 |
| Agent ergonomics | 13% (16.2 this run) | 59 | 49 | Relaticle +10 |
| Security & auth | 14% (17.5 this run) | 57 | 44 | 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) | 90 | 5 | Relaticle +85 |
| Transparency & trust | 7% (8.8 this run) | 73 | 58 | Relaticle +15 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **59.6 · C** | **37.8 · F** | |

## Facts side by side

| Fact | Relaticle | Salesflare |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Relaticle, Inc. | Salesflare BVBA |
| Hosted endpoint | `https://mcp.relaticle.com` | `https://api.salesflare.com` |
| Transports | Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | AGPL-3.0 | Proprietary service under Salesflare's Terms of Service |
| Tools exposed | 50 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | `com.relaticle/crm` | not listed |
| Last release | 2026-11-05 | 2026-10-08 |
| Terms last updated | 2026-08-26 | no date given |
| Privacy policy last updated | 2026-11-04 | couldn't be read |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | 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 | not found in the text | not found in the text |
| Popularity | 1.8k stars | none |

## How the scores have moved

### Relaticle

No score change since it was listed.

### Salesflare

- -10.7 on 4 November 2026 (D to F): new evidence, correction
- -0.2 on 28 October 2026: correction
- +0.2 on 27 October 2026: checklist

## Verdicts

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

**Salesflare.** The REST API has a public Swagger 2.0 file covering 71 operations, with typed filters on every list call and a 30-day trial that needs no card. No rate limit numbers, API changelog, SDK or audit log were found in the reviewed documentation, and API keys carry no documented scopes.

## Before you call either

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

### Salesflare

1. Send `Authorization: Bearer <API key>` to `https://api.salesflare.com`. A person creates the key in Settings, API keys
2. Set `limit` on every list call. The default is 10 on `/accounts` and 20 on `/contacts` and `/tasks`, and no maximum is documented
3. Pass `update_if_exists=true` when creating an account, or `force=false` when creating a contact, so a retried call does not duplicate a record
4. Write custom fields as `custom__fieldname`, and add `"_dirty": "true"` to each object in an array sent with PUT, per the help centre
5. Back off on 429, because no limit or Retry-After guidance is published, and expect only a status code from the documented table

## Questions

### Which is better for AI agents, Relaticle or Salesflare?

Relaticle scores 59.6 (C) on agent readiness against Salesflare's 37.8 (F), and leads in 6 of 7 scored categories.

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

Both take an API key or an OAuth sign-in.

### Can an agent call Relaticle and Salesflare without installing anything?

Yes. Relaticle has a hosted endpoint at https://mcp.relaticle.com and Salesflare at https://api.salesflare.com.

### Are Relaticle and Salesflare open source?

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


## For agents

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

## Other comparisons with Relaticle or Salesflare

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