{ "data": { "a": { "slug": "relaticle", "name": "Relaticle", "vendor": "Relaticle, Inc.", "vendorUrl": "https://relaticle.com", "kind": "http-api", "category": "crm", "summary": "Relaticle is an open-source CRM under AGPL-3.0 for companies, people, opportunities, tasks and notes, run on Relaticle Cloud or self-hosted. Agents use its REST API and an MCP server with OAuth or scoped tokens.", "url": "https://www.anchorterminal.com/tools/relaticle", "markdownUrl": "https://www.anchorterminal.com/tools/relaticle.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/relaticle.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/relaticle.json", "dns": "relaticle.grade.anchorterminal.com", "repo": "https://github.com/relaticle/relaticle", "license": "AGPL-3.0", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.relaticle.com", "packages": [], "auth": "mixed", "authNotes": "Personal access tokens from Settings \u003e Access Tokens are tied to one workspace, take an expiry and carry chosen permissions (read, create, update, delete for REST, plus read, draft and send email for MCP). MCP clients can also use OAuth 2.1 through Laravel Passport and choose one workspace on the consent screen; the source says the OAuth scope `mcp:use` authorises the whole toolset.", "pricing": "freemium", "pricingNotes": "Self-hosting is free under AGPL-3.0. Relaticle Cloud is priced per workspace with unlimited users: Cloud Pro $19 a month billed yearly ($24 monthly) and Cloud Scale $49 ($59 monthly), Enterprise from $20,000 a year. A 14-day Cloud Pro trial needs no card. Scale has three times the API and MCP throughput.", "priceSummary": "$19 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the OpenAPI spec, the developer docs or the source (checked 2026-11-06). Over-limit Cloud calls return 402 for plan limits without payment requirements.", "endpoints": [] }, "toolCount": 50, "popularity": { "githubStars": 1811, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://relaticle.com/developers/rest-api", "llmsTxt": "https://relaticle.com/llms.txt", "openapi": "https://relaticle.com/openapi.json", "registryName": "com.relaticle/crm", "capabilities": [ "crm.records", "crm.pipeline", "crm.activities", "crm.search", "email.send", "email.threads" ], "tags": [ "official", "open-source", "agpl", "self-hosted", "hosted", "mcp", "remote-mcp", "mcp-registry", "oauth", "openapi", "llms-txt", "freemium", "trial", "no-card", "php", "eu-hosting" ], "lastRelease": "2026-11-05", "graded": true, "anchor": { "graded": true, "score": 59.6, "grade": "C", "agentReady": false, "rank": 694, "ranked": true, "rankOf": 1486, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 59, "maintenance": 90, "payments": 30, "reliability": 40, "schema": 86, "security": 57, "transparency": 73 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "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.", "bestFor": "Small teams who want an open-source CRM they can self-host and let an agent write to.", "strengths": [ "AGPL-3.0 source, free to self-host, with tagged releases about twice a week", "Tokens are bound to one workspace with an expiry and per-method permissions, so a read-only token is possible", "OpenAPI 3.1 spec, llms.txt and MCP tools with readOnly, destructive and idempotent hints", "Filter grammar with $and, $or and $not, cursor paging and upserts by unique field", "Cloud providers listed with what each receives, hosting at Hetzner in Germany" ], "weaknesses": [ "Writes over MCP apply immediately, and OAuth's single `mcp:use` scope authorises every tool", "No status page or SLA for Relaticle Cloud was found", "No SOC 2 or ISO 27001, which the security page says plainly", "No changelog page beyond GitHub tags, and no deprecation policy", "50 MCP tools by default, with no toolsets or read-only subset" ], "agentNotes": [ "Use a personal access token with only the read permission unless the task writes, since OAuth grants every tool", "Ask the user before create, update, delete or send tools; the server applies them at once", "Call `get-crm-schema-tool` for an entity before filtering on custom fields, which differ by workspace", "Use `POST /v1/people/upsert` or `/v1/companies/upsert` with a unique field to avoid duplicates on retry", "Keep MCP calls under 120 a minute per user and REST writes under 60 a minute per token on Cloud Pro" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59.6 } ], "editorialScores": { "ergonomics": 59, "maintenance": 90, "payments": 30, "reliability": 40, "schema": 86, "security": 57, "transparency": 72 }, "provenanceScore": 74, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.relaticle.com/v1/companies -H \"Authorization: Bearer YOUR_TOKEN\" -H \"Accept: application/json\"", "claudeCode": "claude mcp add --transport http relaticle https://mcp.relaticle.com", "config": { "mcpServers": { "relaticle": { "url": "https://mcp.relaticle.com" } } } }, "letme": { "capability": "https://letme.dev/crm.records", "tool": "https://letme.dev/relaticle" }, "area": "business", "unitPrices": [ { "item": "Cloud Pro workspace", "unit": "month", "usd": 19, "note": "Billed yearly at $228; $24 billed monthly" }, { "item": "Cloud Scale workspace", "unit": "month", "usd": 49, "note": "Billed yearly at $588; $59 billed monthly" } ], "provenance": { "legalEntity": "Relaticle, Inc.", "domain": "relaticle.com", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://relaticle.com/terms-of-service", "privacy": "https://relaticle.com/privacy-policy", "statusPage": "", "changelog": "https://github.com/relaticle/relaticle/releases", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "Terms of service effective 26 August 2026 and privacy policy effective 4 November 2026; the footer names Relaticle, Inc. No clause on automated access to the website was found.", "relaticle.com/robots.txt allows all crawlers and names ClaudeBot as allowed.", "security.txt names security@relaticle.com and expires 6 May 2027. The security page asks for reports by email and aims to acknowledge within 48 hours.", "status.relaticle.com did not connect and no status page is linked. relaticle.com/changelog is 404; releases are tagged on GitHub.", "The press page says Relaticle was founded in 2024 and lists 1,811 GitHub stars, verified 26 September 2026. Domain registration date not checked." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/relaticle.json", "live": { "slug": "relaticle", "probe": { "target": "https://mcp.relaticle.com", "method": "get", "lastAt": "2026-11-07T18:20:50.642634031Z", "lastOk": true, "lastStatus": 405, "lastMs": 234, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 174, "p95ms24h": 292, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "versions": [ { "registry": "github", "name": "relaticle/relaticle", "version": "v3.8.2", "released": "2026-11-04", "seenAt": "2026-11-07T00:00:54.651079547Z" }, { "registry": "mcp-registry", "name": "com.relaticle/crm", "version": "3.8.2", "seenAt": "2026-11-07T18:16:28.95801333Z" } ], "githubStars": 1811, "securityTxt": { "url": "https://relaticle.com/.well-known/security.txt", "state": "valid", "expires": "2027-05-07T16:01:18Z", "checkedAt": "2026-11-07T16:01:18.554359358Z" }, "llmsTxt": { "url": "https://relaticle.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:44.579905089Z" }, "pages": [ { "url": "https://relaticle.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:18:13.002922035Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6e701d3eab86" }, { "url": "https://relaticle.com/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:18:15.26331735Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1e5fff279d1d" } ], "mcpTools": { "url": "https://mcp.relaticle.com", "checkedAt": "2026-11-07T01:47:13.278550358Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:47:13.278550358Z" }, "updatedAt": "2026-11-07T18:20:50.642634031Z" } }, "answer": "Relaticle scores 59.6 (C) on agent readiness against SugarAI (SugarCRM)'s 47.2 (D), and leads in 5 of 7 scored categories. SugarAI (SugarCRM) leads on reliability and agent ergonomics.", "b": { "slug": "sugarcrm", "name": "SugarAI (SugarCRM)", "vendor": "SugarAI Software Inc.", "vendorUrl": "https://sugarai.com", "kind": "http-api", "category": "crm", "summary": "SugarAI, formerly SugarCRM, sells the Sugar Sell, Serve and Enterprise CRM applications, hosted on SugarCloud or installed on-site. Agents reach records through a versioned REST API (v11.27 in release 26.1) on each customer instance, with a legacy SOAP API.", "url": "https://www.anchorterminal.com/tools/sugarcrm", "markdownUrl": "https://www.anchorterminal.com/tools/sugarcrm.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sugarcrm.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sugarcrm.json", "dns": "sugarcrm.grade.anchorterminal.com", "license": "Proprietary service under the SugarAI Customer Terms of Service", "transports": [ "http" ], "packages": [], "auth": "oauth", "authNotes": "Access follows a sales contract. An admin creates a Sugar user, and the caller POSTs that user's username and plaintext password to `/rest/v11_27/oauth2/token` with `grant_type` `password`. The default `client_id` is `sugar` with an empty secret, and an admin can create other OAuth keys. The token goes in the `OAuth-Token` header, lasts 60 minutes by default and is renewed with a refresh token valid for up to two weeks. The reference says there is no scope implementation, so a token has the user's roles and teams. An admin can obtain a token as another user through `/oauth2/sudo/:user_name`. SugarCloud instances must use SugarIdentity.", "pricing": "paid", "pricingNotes": "Sugar Sell costs $68 (Standard+), $98 (Advanced+) or $155 (Premier+) a user a month, billed annually. No free tier or self-serve trial was found, and the site asks visitors to book a demo or contact sales. API calls are not priced separately. Sandboxes are included on Sell Standard and above per the SugarCloud Offerings page, and are provisioned through a support case (https://sugarai.com/pricing, checked 2026-10-09).", "priceSummary": "$68 / seat-mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Developer Guide, the Postman collection or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://support.sugarai.com/documentation/sugar_developer/sugar_developer_guide_26.1/integration/web_services/", "capabilities": [ "crm.records", "crm.search", "crm.pipeline", "crm.activities" ], "tags": [ "hosted", "on-site", "closed-source", "oauth", "rest", "soap", "sales-led", "status-page", "soc2", "iso27001", "security-txt" ], "graded": true, "anchor": { "graded": true, "score": 47.2, "grade": "D", "agentReady": false, "rank": 1144, "ranked": true, "rankOf": 1486, "categoryRank": 14, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 12, "payments": 10, "reliability": 61, "schema": 40, "security": 51, "transparency": 69 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": 0, "verdict": "The REST reference covers 350 endpoint pages with filters, field selection, bulk calls and upsert by `sync_key`. SugarAI's AI Supplemental Terms forbid connecting a customer's or third party's AI agent or MCP connector to the APIs unless Sugar has approved it, tokens carry no scopes, and no OpenAPI file, trial or SLA was found.", "bestFor": "Companies already running Sugar Sell, Serve or Enterprise that want an agent to read and write records under a named user's roles, and that have Sugar's approval for the integration.", "strengths": [ "The 26.1 Developer Guide lists 350 REST endpoint pages, each with argument tables, a request and response example and a per-endpoint change log", "List calls take `fields`, `view`, `max_num` (default 20), `offset`, `order_by` and a filter grammar with 13 operators plus `$and` and `$or`", "`/integrate` endpoints upsert by `sync_key`, and `/bulk` runs a sequence of calls in one request with a status per call", "The Customer Terms of Service, the DPA and the security FAQ agree that customer data stays available for 120 days after termination and is then deleted", "SOC 2 Type II and ISO/IEC 27001:2022 per the trust page, a valid security.txt, and a public sub-processor list with countries" ], "weaknesses": [ "The AI Supplemental Terms forbid connecting customer-owned or third-party AI systems, agents or MCP connectors to the Services or APIs except through functionality Sugar has approved. This matters before any probe is run", "Access tokens come from an OAuth 2.0 password grant with a user's plaintext password, and the reference says there is no scope implementation", "No OpenAPI file or `llms.txt` was found, and no download link for the Postman collection was recorded", "No trial signup, free tier or SLA was found. Sugar Sell starts at $68 a user a month billed annually and other products are quoted by sales", "SugarCloud may block an IP address sending more than 20 requests a second, and no 429 or Retry-After behaviour is documented", "The Customer Terms of Service forbid performing or disclosing benchmarking, availability or performance testing of the Services" ], "agentNotes": [ "Confirm that Sugar has approved the agent integration before connecting. The AI Supplemental Terms forbid unapproved AI agents and MCP connectors on the APIs", "POST to `/rest/v11_27/oauth2/token` with `grant_type` `password` and a `platform` other than `base`, `mobile` or `portal`, or the login can end the user's own session", "Send the access token in the `OAuth-Token` header. It lasts 60 minutes by default, so store the refresh token and not the password", "Stay under 20 requests a second on SugarCloud and reuse one session for batches. Over-limit traffic is blocked by IP address until support lifts it", "Page with `max_num` and `offset` until `next_offset` is -1, and pass `fields` to keep responses small", "Use `PATCH /integrate/:module/:sync_key_field_name/:sync_key_field_value` for writes that may be retried, since it inserts or updates by `sync_key`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 47.2 } ], "editorialScores": { "ergonomics": 69, "maintenance": 12, "payments": 10, "reliability": 61, "schema": 40, "security": 51, "transparency": 71 }, "provenanceScore": 66, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -X POST -H Cache-Control:no-cache -H \"Content-Type: application/json\" -d '{\n \"grant_type\":\"password\",\n \"client_id\":\"sugar\",\n \"client_secret\":\"\",\n \"username\":\"\u003cusername\u003e\",\n \"password\":\"\u003cpassword\u003e\",\n \"platform\":\"custom\"\n}' https://\u003csite_url\u003e/rest/\u003cversion\u003e/oauth2/token" }, "letme": { "capability": "https://letme.dev/crm.records", "tool": "https://letme.dev/sugarcrm" }, "area": "business", "unitPrices": [ { "item": "Sugar Sell Standard+", "unit": "seat-month", "usd": 68, "note": "billed annually" }, { "item": "Sugar Sell Advanced+", "unit": "seat-month", "usd": 98, "note": "billed annually" }, { "item": "Sugar Sell Premier+", "unit": "seat-month", "usd": 155, "note": "billed annually" }, { "item": "Sugar Connect+ add-on", "unit": "seat-month", "usd": 20, "note": "billed annually, on top of a Sell plan" } ], "provenance": { "legalEntity": "SugarAI Software Inc.", "domain": "sugarai.com", "domainRegistered": "2018-03-19", "endpointOnVendorDomain": false, "terms": "https://framerusercontent.com/assets/eu2GiGUMAeMAwAn8rqawpURGnP4.pdf", "privacy": "https://sugarai.com/legal/privacy-policy", "statusPage": "https://status.cloud.sugarai.com", "changelog": "", "securityTxt": "valid", "checked": "2026-11-04", "notes": [ "The Customer Terms of Service (published 7 April 2026) name the contracting entity by region. It is SugarAI Software Inc., a Delaware corporation at 548 Market Street PMB 59423, San Francisco, for all regions except Australia and New Zealand (SugarAI Australia Pty Ltd) and new UK customers (SugarAI UK Limited). California law governs outside the listed regions.", "The terms are a PDF on framerusercontent.com, the asset host of the vendor's Framer site, linked from sugarai.com/legal/customers. The same agreements on support.sugarai.com sit under a path robots.txt disallows.", "The API answers on each customer's instance at `https://\u003csite_url\u003e/rest/`. The host name of a SugarCloud instance was not established, so the endpoint is recorded as not on the vendor's domain.", "The privacy policy (effective 7 April 2026) covers the websites and the products and says Customer Data is processed under the subscription agreement.", "sugarai.com/.well-known/security.txt gives security@sugarcrm.com and expires on 1 April 2027.", "No dated API changelog or release notes page was reached. The documentation index lists its topics by script.", "RDAP gives 2018-03-19 for sugarai.com and 2004-03-05 for sugarcrm.com. The rename from SugarCRM to SugarAI was announced on 13 April 2026.", "The website Terms of Use (sugarai.com/legal/terms-of-use, read 4 November 2026) govern all Sugar websites and bar using 'any robot, spider, or other automatic device, process, or means to access the Site for any purpose'. robots.txt on sugarai.com allows ClaudeBot. From 4 November 2026 we read nothing on Sugar hosts beyond robots.txt and that page, including the status page.", "The registration date 2018-03-19 for sugarai.com rests on an earlier registry lookup, not repeated on 4 November 2026." ], "score": 66 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/sugarcrm.json", "live": { "slug": "sugarcrm", "vendorStatus": { "page": "https://status.cloud.sugarai.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:50.321464475Z" }, "securityTxt": { "url": "https://sugarai.com/.well-known/security.txt", "state": "valid", "expires": "2027-04-01T00:00:00.000Z", "checkedAt": "2026-11-07T16:00:22.302072051Z" }, "domain": { "domain": "sugarai.com", "registered": "2018-03-19", "source": "https://rdap.verisign.com/com/v1/domain/sugarai.com", "checkedAt": "2026-11-01T14:14:50.441227683Z" }, "pages": [ { "url": "https://sugarai.com/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:21:08.610436131Z", "changedAt": "2026-11-03T07:59:47.547321924Z", "fingerprint": "bfe2c5a7dcd1" }, { "url": "https://sugarai.com/legal/privacy-policy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:21:06.450319025Z", "changedAt": "2026-11-03T07:59:45.233632156Z", "fingerprint": "4ab7bb5b94f6" } ], "updatedAt": "2026-11-07T16:00:22.302072051Z" } }, "edges": [ { "by": 78, "category": "maintenance", "leads": "relaticle", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "SugarAI's website Terms of Use bar any robot or automatic means from accessing Sugar websites, so Sugar pages are per the 9 October check, not re-read on 4 November. The newest dated evidence of an API release is the 26.1 Developer Guide, whose REST pages are stamped 15 May 2026. A page stamp records no change, and no release note or dated API change was read, so no recency is credited (0). Three releases in the last 90 days were not established (0). The support site and its policy pages are current, with a support portal. The SugarClub community answered with a bot check on 9 October and was not read (7 of 25). No current SDKs in several languages. `ventana`, the JavaScript client, was last tagged 1.1.25 on 16 January 2026 (clone read 4 November), a partial held (5 of 15). No package was checked on a registry (0). 0 + 0 + 7 + 5 + 0 = 12." }, "scores": { "a": 90, "b": 12 } }, { "by": 46, "category": "schema", "leads": "relaticle", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "SugarAI's website Terms of Use bar any robot or automatic means from accessing Sugar websites, so Sugar pages are per the 9 October check, not re-read on 4 November. No OpenAPI file was found. A Postman collection was read on 9 October behind the viewer page at rest.apidocs.sugarcrm.com, with no download link recorded, so it isn't counted as a published contract. Each instance serves its own reference at `/rest/v{version}/help` and a `/metadata` endpoint, which we could not read without an instance (0). `llms.txt` on support.sugarai.com returned 404 and no Markdown docs were found (0). The 26.1 Developer Guide lists 350 endpoint pages. The five sampled carry an overview and a summary, and the filter page warns about unindexed filters, but none says when not to use an endpoint (11 of 20). Arguments are tabled with type and required flag. Record bodies are described only as `\u003crecord field\u003e`, and filters are a free-form expression (7 of 15). Every sampled page has a request and response example, and a separate page lists 21 exception classes with HTTP codes and error labels. The examples carry dates from 2013 and 2014 (10 of 15). The API is versioned in the path, a table maps each Sugar release to its REST version, and each endpoint page has a change log. No dated API changelog was found (12 of 15). 0 + 0 + 11 + 7 + 10 + 12 = 40." }, "scores": { "a": 86, "b": 40 } }, { "by": 21, "category": "reliability", "leads": "sugarcrm", "name": "Reliability", "reasons": { "a": "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.", "b": "SugarAI's website Terms of Use bar any robot or automatic means from accessing Sugar websites, so Sugar pages are per the 9 October check, not re-read on 4 November. Read with the hosted lines, for the SugarCloud REST API. Status page at status.cloud.sugarai.com on Better Stack with more than 100 components by region and cluster, and incident history (20). The RSS feed, read on 9 October, shows about 18 dated incidents between 15 July and 4 October 2026, most of them one to three minutes on a single cluster. The longest were 41 minutes on Sugar Cloud Premium DE 02 on 21 September and 39 minutes on US 02 on 16 July. On 24 July, 15 services including SugarIdentity global login and eight US clusters were down for about 11 minutes. No outage of an hour was found, and the wide one is why this sits below the minor band (14 of 30). The 24 July incident is now outside the 90 days from 6 August, and the window from 5 October is unread, so the line keeps its recorded value as a partial. The SugarCloud Policy Guide gives 20 requests a second as the level above which traffic may be blocked, and ends SELECT queries after 120 seconds. The limit is enforced at Sugar's discretion (12 of 15). No 429 or Retry-After behaviour is documented. Blocked traffic is lifted through a support case. Upsert by `sync_key` and a 409 `edit_conflict` error give some retry safety (5 of 15). No SLA was found in the Customer Terms of Service, which do not warrant uninterrupted service (0). The REST API is GA and versioned (10). 20 + 14 + 12 + 5 + 0 + 10 = 61." }, "scores": { "a": 40, "b": 61 } }, { "by": 20, "category": "payments", "leads": "relaticle", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "SugarAI's website Terms of Use bar any robot or automatic means from accessing Sugar websites, so Sugar pages are per the 9 October check, not re-read on 4 November. No x402, MPP or L402 (0). Plan prices are public for Sugar Sell, at $68, $98 and $155 a user a month billed annually, with Precision+ bundles quoted by sales and nothing per call (10). No free tier or self-serve trial was found. The site's buttons ask for a demo, and a 30-day Evaluation Agreement exists for evaluations Sugar arranges (0). A person buys through sales and an admin creates the user an agent logs in as (0)." }, "scores": { "a": 30, "b": 10 } }, { "by": 10, "category": "ergonomics", "leads": "sugarcrm", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "SugarAI's website Terms of Use bar any robot or automatic means from accessing Sugar websites, so Sugar pages are per the 9 October check, not re-read on 4 November. List and filter calls take `fields`, `view` and `max_num`, with a default of 20 records (20 of 25). `offset` and `next_offset` pagination, 13 filter operators with `$and` and `$or`, `order_by`, `q`, and count endpoints (20). Errors return JSON with `error` and `error_message`, and the exceptions page maps 21 classes to HTTP codes including 409, 412, 413 and 422 (14 of 20). No idempotency keys. The `/integrate` endpoints upsert by `sync_key`, and updates can fail with 409 `edit_conflict` (10 of 20). Few required parameters. The only official client found is `ventana`, a JavaScript client on GitHub last pushed on 16 January 2026, so there are not SDKs in two languages (5 of 15). 20 + 20 + 14 + 10 + 5 = 69." }, "scores": { "a": 59, "b": 69 } }, { "by": 6, "category": "security", "leads": "relaticle", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "SugarAI's website Terms of Use bar any robot or automatic means from accessing Sugar websites, so Sugar pages are per the 9 October check, not re-read on 4 November. Tokens come from an OAuth 2.0 password grant that sends a user's username and plaintext password. The default `client_id` is `sugar` with an empty secret, the reference says there is no scope implementation, and an admin can obtain a token as any user through `/oauth2/sudo/:user_name`. Access tokens last 60 minutes and refresh tokens up to two weeks, both configurable in SugarIdentity (12 of 30). A token is limited by the user's roles and teams. No read-only token type or confirmation step for destructive calls was found (10 of 20). Records hold emails, notes and case text, and no prompt-injection guidance was found (3 of 15). SugarIdentity keeps an exportable audit log of logins, record audit endpoints exist (`/:module/:record/audit`), and access logs are available in SugarCloud Insights (10 of 15). security.txt is valid until 1 April 2027. The trust page lists SOC 2 Type II, ISO/IEC 27001:2022 and a CSA STAR listing, and the security FAQ states a bug bounty programme and patch targets of 14 days for critical flaws. The advisories page is closed to us by robots.txt and was not read (16 of 20). 12 + 10 + 3 + 10 + 16 = 51." }, "scores": { "a": 57, "b": 51 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Relaticle, Inc.", "b": "SugarAI Software Inc.", "name": "Vendor" }, { "a": "https://mcp.relaticle.com", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "AGPL-3.0", "b": "Proprietary service under the SugarAI Customer Terms of Service", "name": "Licence" }, { "a": "50", "b": "none", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "com.relaticle/crm", "b": "not listed", "name": "MCP registry" }, { "a": "2026-11-05", "b": "none", "name": "Last release" }, { "a": "2026-08-26", "b": "not read yet", "name": "Terms last updated" }, { "a": "2026-11-04", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not read yet", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "1.8k stars", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Relaticle scores 59.6 (C) on agent readiness against SugarAI (SugarCRM)'s 47.2 (D), and leads in 5 of 7 scored categories. SugarAI (SugarCRM) leads on reliability and agent ergonomics.", "question": "Which is better for AI agents, Relaticle or SugarAI (SugarCRM)?" }, { "answer": "Relaticle takes an API key or an OAuth sign-in. SugarAI (SugarCRM) uses an OAuth sign-in.", "question": "Do Relaticle and SugarAI (SugarCRM) need an API key?" }, { "answer": "Relaticle has a hosted endpoint at https://mcp.relaticle.com. No hosted endpoint is listed for SugarAI (SugarCRM).", "question": "Can an agent call Relaticle and SugarAI (SugarCRM) without installing anything?" }, { "answer": "Relaticle is open source (AGPL-3.0). No open-source release is listed for SugarAI (SugarCRM).", "question": "Are Relaticle and SugarAI (SugarCRM) open source?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 86 against 40", "Security \u0026 auth, 57 against 51", "Payments \u0026 pricing, 30 against 10", "Maintenance \u0026 community, 90 against 12" ], "also": [ "A hosted endpoint, with nothing to install", "Free to start without a card", "Open source" ], "goodFor": "Small teams who want an open-source CRM they can self-host and let an agent write to.", "slug": "relaticle", "watchFor": "Writes over MCP apply immediately, and OAuth's single `mcp:use` scope authorises every tool" }, { "aheadOn": [ "Reliability, 61 against 40", "Agent ergonomics, 69 against 59" ], "also": null, "goodFor": "Companies already running Sugar Sell, Serve or Enterprise that want an agent to read and write records under a named user's roles, and that have Sugar's approval for the integration.", "slug": "sugarcrm", "watchFor": "The AI Supplemental Terms forbid connecting customer-owned or third-party AI systems, agents or MCP connectors to the Services or APIs except through functionality Sugar has approved. This matters before any probe is run" } ], "history": { "relaticle": null, "sugarcrm": [ { "causes": [ "correction" ], "date": "2026-11-04", "delta": -2.2, "from": 49.4, "fromGrade": "D", "to": 47.2, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-30", "delta": -0.2, "from": 49.6, "fromGrade": "D", "to": 49.4, "toGrade": "D" }, { "causes": [ "correction" ], "date": "2026-10-28", "delta": -0.1, "from": 49.7, "fromGrade": "D", "to": 49.6, "toGrade": "D" } ] }, "job": { "capability": "crm.records", "name": "CRM records" }, "others": [ { "json": "https://www.anchorterminal.com/compare/affinity-vs-relaticle.json", "title": "Affinity vs Relaticle", "url": "https://www.anchorterminal.com/compare/affinity-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/affinity-vs-sugarcrm.json", "title": "Affinity vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/affinity-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/attio-vs-relaticle.json", "title": "Attio API + MCP vs Relaticle", "url": "https://www.anchorterminal.com/compare/attio-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/attio-vs-sugarcrm.json", "title": "Attio API + MCP vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/attio-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/breakcold-vs-relaticle.json", "title": "Breakcold vs Relaticle", "url": "https://www.anchorterminal.com/compare/breakcold-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/breakcold-vs-sugarcrm.json", "title": "Breakcold vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/breakcold-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/capsule-crm-vs-relaticle.json", "title": "Capsule CRM vs Relaticle", "url": "https://www.anchorterminal.com/compare/capsule-crm-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/capsule-crm-vs-sugarcrm.json", "title": "Capsule CRM vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/capsule-crm-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/close-vs-relaticle.json", "title": "Close API + MCP vs Relaticle", "url": "https://www.anchorterminal.com/compare/close-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/close-vs-sugarcrm.json", "title": "Close API + MCP vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/close-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/copper-vs-relaticle.json", "title": "Copper API vs Relaticle", "url": "https://www.anchorterminal.com/compare/copper-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/copper-vs-sugarcrm.json", "title": "Copper API vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/copper-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/dynamics-365-sales-vs-relaticle.json", "title": "Microsoft Dynamics 365 Sales vs Relaticle", "url": "https://www.anchorterminal.com/compare/dynamics-365-sales-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/dynamics-365-sales-vs-sugarcrm.json", "title": "Microsoft Dynamics 365 Sales vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/dynamics-365-sales-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/folk-vs-relaticle.json", "title": "folk API + MCP vs Relaticle", "url": "https://www.anchorterminal.com/compare/folk-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/folk-vs-sugarcrm.json", "title": "folk API + MCP vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/folk-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/freshsales-vs-relaticle.json", "title": "Freshsales API vs Relaticle", "url": "https://www.anchorterminal.com/compare/freshsales-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/freshsales-vs-sugarcrm.json", "title": "Freshsales API vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/freshsales-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/hubspot-mcp-vs-relaticle.json", "title": "HubSpot API + MCP vs Relaticle", "url": "https://www.anchorterminal.com/compare/hubspot-mcp-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/hubspot-mcp-vs-sugarcrm.json", "title": "HubSpot API + MCP vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/hubspot-mcp-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/nutshell-vs-relaticle.json", "title": "Nutshell vs Relaticle", "url": "https://www.anchorterminal.com/compare/nutshell-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/nutshell-vs-sugarcrm.json", "title": "Nutshell vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/nutshell-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/payani-ai-vs-relaticle.json", "title": "Payani AI vs Relaticle", "url": "https://www.anchorterminal.com/compare/payani-ai-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/payani-ai-vs-sugarcrm.json", "title": "Payani AI vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/payani-ai-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/pipedrive-vs-relaticle.json", "title": "Pipedrive API + MCP vs Relaticle", "url": "https://www.anchorterminal.com/compare/pipedrive-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/pipedrive-vs-sugarcrm.json", "title": "Pipedrive API + MCP vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/pipedrive-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/relaticle-vs-salesflare.json", "title": "Relaticle vs Salesflare", "url": "https://www.anchorterminal.com/compare/relaticle-vs-salesflare" }, { "json": "https://www.anchorterminal.com/compare/relaticle-vs-salesforce.json", "title": "Relaticle vs Salesforce API + MCP", "url": "https://www.anchorterminal.com/compare/relaticle-vs-salesforce" }, { "json": "https://www.anchorterminal.com/compare/relaticle-vs-streak.json", "title": "Relaticle vs Streak API + MCP", "url": "https://www.anchorterminal.com/compare/relaticle-vs-streak" }, { "json": "https://www.anchorterminal.com/compare/relaticle-vs-twenty.json", "title": "Relaticle vs Twenty API + MCP", "url": "https://www.anchorterminal.com/compare/relaticle-vs-twenty" }, { "json": "https://www.anchorterminal.com/compare/relaticle-vs-zoho-crm.json", "title": "Relaticle vs Zoho CRM", "url": "https://www.anchorterminal.com/compare/relaticle-vs-zoho-crm" }, { "json": "https://www.anchorterminal.com/compare/salesflare-vs-sugarcrm.json", "title": "Salesflare vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/salesflare-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/salesforce-vs-sugarcrm.json", "title": "Salesforce API + MCP vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/salesforce-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/streak-vs-sugarcrm.json", "title": "Streak API + MCP vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/streak-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/sugarcrm-vs-twenty.json", "title": "SugarAI (SugarCRM) vs Twenty API + MCP", "url": "https://www.anchorterminal.com/compare/sugarcrm-vs-twenty" }, { "json": "https://www.anchorterminal.com/compare/sugarcrm-vs-zoho-crm.json", "title": "SugarAI (SugarCRM) vs Zoho CRM", "url": "https://www.anchorterminal.com/compare/sugarcrm-vs-zoho-crm" } ], "panel": null, "scores": [ { "by": 21, "edge": "sugarcrm", "key": "reliability", "name": "Reliability", "relaticle": 40, "sugarcrm": 61, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 46, "edge": "relaticle", "key": "schema", "name": "Schema \u0026 documentation", "relaticle": 86, "sugarcrm": 40, "weight": 13 }, { "by": 10, "edge": "sugarcrm", "key": "ergonomics", "name": "Agent ergonomics", "relaticle": 59, "sugarcrm": 69, "weight": 13 }, { "by": 6, "edge": "relaticle", "key": "security", "name": "Security \u0026 auth", "relaticle": 57, "sugarcrm": 51, "weight": 14 }, { "by": 20, "edge": "relaticle", "key": "payments", "name": "Payments \u0026 pricing", "relaticle": 30, "sugarcrm": 10, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 78, "edge": "relaticle", "key": "maintenance", "name": "Maintenance \u0026 community", "relaticle": 90, "sugarcrm": 12, "weight": 7 }, { "by": 4, "edge": "relaticle", "key": "transparency", "name": "Transparency \u0026 trust", "relaticle": 73, "sugarcrm": 69, "weight": 7 } ], "summary": "Relaticle scores 59.6 (C) on agent readiness against SugarAI (SugarCRM)'s 47.2 (D), and leads in 5 of 7 scored categories. SugarAI (SugarCRM) leads on reliability and agent ergonomics. Both do crm records.", "tasks": null, "tutorials": [], "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.", "sugarcrm": "The REST reference covers 350 endpoint pages with filters, field selection, bulk calls and upsert by `sync_key`. SugarAI's AI Supplemental Terms forbid connecting a customer's or third party's AI agent or MCP connector to the APIs unless Sugar has approved it, tokens carry no scopes, and no OpenAPI file, trial or SLA was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/relaticle-vs-sugarcrm", "json": "https://www.anchorterminal.com/compare/relaticle-vs-sugarcrm.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/relaticle-vs-sugarcrm.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/relaticle-vs-sugarcrm.min.md" }, "markdown": "Relaticle scores 59.6 (C) on agent readiness against SugarAI (SugarCRM)'s 47.2 (D), and leads in 5 of 7 scored categories. SugarAI (SugarCRM) leads on reliability and agent ergonomics. Both do crm records.\n\n- Relaticle: grade C, 59.6/100, rank #694 of 1486. Markdown https://www.anchorterminal.com/tools/relaticle.md · JSON https://www.anchorterminal.com/api/v1/tools/relaticle.json\n- SugarAI (SugarCRM): grade D, 47.2/100, rank #1144 of 1486. Markdown https://www.anchorterminal.com/tools/sugarcrm.md · JSON https://www.anchorterminal.com/api/v1/tools/sugarcrm.json\n- Best CRM and customer-platform tools for AI agents: https://www.anchorterminal.com/best/crm/index.md\n- All 190 crm comparisons: https://www.anchorterminal.com/compare/crm/index.md\n\n## Which one, for what\n\n### Relaticle (C)\n\nGood for: Small teams who want an open-source CRM they can self-host and let an agent write to.\n\nAhead on:\n- Schema \u0026 documentation, 86 against 40\n- Security \u0026 auth, 57 against 51\n- Payments \u0026 pricing, 30 against 10\n- Maintenance \u0026 community, 90 against 12\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n- Open source\n\nWatch for: Writes over MCP apply immediately, and OAuth's single `mcp:use` scope authorises every tool\n\n### SugarAI (SugarCRM) (D)\n\nGood for: Companies already running Sugar Sell, Serve or Enterprise that want an agent to read and write records under a named user's roles, and that have Sugar's approval for the integration.\n\nAhead on:\n- Reliability, 61 against 40\n- Agent ergonomics, 69 against 59\n\nWatch for: The AI Supplemental Terms forbid connecting customer-owned or third-party AI systems, agents or MCP connectors to the Services or APIs except through functionality Sugar has approved. This matters before any probe is run\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Relaticle +78\n\n- 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.\n- SugarAI (SugarCRM) (12): SugarAI's website Terms of Use bar any robot or automatic means from accessing Sugar websites, so Sugar pages are per the 9 October check, not re-read on 4 November. The newest dated evidence of an API release is the 26.1 Developer Guide, whose REST pages are stamped 15 May 2026. A page stamp records no change, and no release note or dated API change was read, so no recency is credited (0). Three releases in the last 90 days were not established (0). The support site and its policy pages are current, with a support portal. The SugarClub community answered with a bot check on 9 October and was not read (7 of 25). No current SDKs in several languages. `ventana`, the JavaScript client, was last tagged 1.1.25 on 16 January 2026 (clone read 4 November), a partial held (5 of 15). No package was checked on a registry (0). 0 + 0 + 7 + 5 + 0 = 12.\n\n### Schema \u0026 documentation: Relaticle +46\n\n- 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.\n- SugarAI (SugarCRM) (40): SugarAI's website Terms of Use bar any robot or automatic means from accessing Sugar websites, so Sugar pages are per the 9 October check, not re-read on 4 November. No OpenAPI file was found. A Postman collection was read on 9 October behind the viewer page at rest.apidocs.sugarcrm.com, with no download link recorded, so it isn't counted as a published contract. Each instance serves its own reference at `/rest/v{version}/help` and a `/metadata` endpoint, which we could not read without an instance (0). `llms.txt` on support.sugarai.com returned 404 and no Markdown docs were found (0). The 26.1 Developer Guide lists 350 endpoint pages. The five sampled carry an overview and a summary, and the filter page warns about unindexed filters, but none says when not to use an endpoint (11 of 20). Arguments are tabled with type and required flag. Record bodies are described only as `\u003crecord field\u003e`, and filters are a free-form expression (7 of 15). Every sampled page has a request and response example, and a separate page lists 21 exception classes with HTTP codes and error labels. The examples carry dates from 2013 and 2014 (10 of 15). The API is versioned in the path, a table maps each Sugar release to its REST version, and each endpoint page has a change log. No dated API changelog was found (12 of 15). 0 + 0 + 11 + 7 + 10 + 12 = 40.\n\n### Reliability: SugarAI (SugarCRM) +21\n\n- 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.\n- SugarAI (SugarCRM) (61): SugarAI's website Terms of Use bar any robot or automatic means from accessing Sugar websites, so Sugar pages are per the 9 October check, not re-read on 4 November. Read with the hosted lines, for the SugarCloud REST API. Status page at status.cloud.sugarai.com on Better Stack with more than 100 components by region and cluster, and incident history (20). The RSS feed, read on 9 October, shows about 18 dated incidents between 15 July and 4 October 2026, most of them one to three minutes on a single cluster. The longest were 41 minutes on Sugar Cloud Premium DE 02 on 21 September and 39 minutes on US 02 on 16 July. On 24 July, 15 services including SugarIdentity global login and eight US clusters were down for about 11 minutes. No outage of an hour was found, and the wide one is why this sits below the minor band (14 of 30). The 24 July incident is now outside the 90 days from 6 August, and the window from 5 October is unread, so the line keeps its recorded value as a partial. The SugarCloud Policy Guide gives 20 requests a second as the level above which traffic may be blocked, and ends SELECT queries after 120 seconds. The limit is enforced at Sugar's discretion (12 of 15). No 429 or Retry-After behaviour is documented. Blocked traffic is lifted through a support case. Upsert by `sync_key` and a 409 `edit_conflict` error give some retry safety (5 of 15). No SLA was found in the Customer Terms of Service, which do not warrant uninterrupted service (0). The REST API is GA and versioned (10). 20 + 14 + 12 + 5 + 0 + 10 = 61.\n\n### Payments \u0026 pricing: Relaticle +20\n\n- 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.\n- SugarAI (SugarCRM) (10): SugarAI's website Terms of Use bar any robot or automatic means from accessing Sugar websites, so Sugar pages are per the 9 October check, not re-read on 4 November. No x402, MPP or L402 (0). Plan prices are public for Sugar Sell, at $68, $98 and $155 a user a month billed annually, with Precision+ bundles quoted by sales and nothing per call (10). No free tier or self-serve trial was found. The site's buttons ask for a demo, and a 30-day Evaluation Agreement exists for evaluations Sugar arranges (0). A person buys through sales and an admin creates the user an agent logs in as (0).\n\n### Agent ergonomics: SugarAI (SugarCRM) +10\n\n- 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.\n- SugarAI (SugarCRM) (69): SugarAI's website Terms of Use bar any robot or automatic means from accessing Sugar websites, so Sugar pages are per the 9 October check, not re-read on 4 November. List and filter calls take `fields`, `view` and `max_num`, with a default of 20 records (20 of 25). `offset` and `next_offset` pagination, 13 filter operators with `$and` and `$or`, `order_by`, `q`, and count endpoints (20). Errors return JSON with `error` and `error_message`, and the exceptions page maps 21 classes to HTTP codes including 409, 412, 413 and 422 (14 of 20). No idempotency keys. The `/integrate` endpoints upsert by `sync_key`, and updates can fail with 409 `edit_conflict` (10 of 20). Few required parameters. The only official client found is `ventana`, a JavaScript client on GitHub last pushed on 16 January 2026, so there are not SDKs in two languages (5 of 15). 20 + 20 + 14 + 10 + 5 = 69.\n\n### Security \u0026 auth: Relaticle +6\n\n- 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.\n- SugarAI (SugarCRM) (51): SugarAI's website Terms of Use bar any robot or automatic means from accessing Sugar websites, so Sugar pages are per the 9 October check, not re-read on 4 November. Tokens come from an OAuth 2.0 password grant that sends a user's username and plaintext password. The default `client_id` is `sugar` with an empty secret, the reference says there is no scope implementation, and an admin can obtain a token as any user through `/oauth2/sudo/:user_name`. Access tokens last 60 minutes and refresh tokens up to two weeks, both configurable in SugarIdentity (12 of 30). A token is limited by the user's roles and teams. No read-only token type or confirmation step for destructive calls was found (10 of 20). Records hold emails, notes and case text, and no prompt-injection guidance was found (3 of 15). SugarIdentity keeps an exportable audit log of logins, record audit endpoints exist (`/:module/:record/audit`), and access logs are available in SugarCloud Insights (10 of 15). security.txt is valid until 1 April 2027. The trust page lists SOC 2 Type II, ISO/IEC 27001:2022 and a CSA STAR listing, and the security FAQ states a bug bounty programme and patch targets of 14 days for critical flaws. The advisories page is closed to us by robots.txt and was not read (16 of 20). 12 + 10 + 3 + 10 + 16 = 51.\n\n## Score by category\n\n| Category | Weight | Relaticle | SugarAI (SugarCRM) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 61 | SugarAI (SugarCRM) +21 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 40 | Relaticle +46 |\n| Agent ergonomics | 13% (16.2 this run) | 59 | 69 | SugarAI (SugarCRM) +10 |\n| Security \u0026 auth | 14% (17.5 this run) | 57 | 51 | Relaticle +6 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 10 | Relaticle +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 90 | 12 | Relaticle +78 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 73 | 69 | Relaticle +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **59.6 · C** | **47.2 · D** | |\n\n## Facts side by side\n\n| Fact | Relaticle | SugarAI (SugarCRM) |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Relaticle, Inc. | SugarAI Software Inc. |\n| Hosted endpoint | `https://mcp.relaticle.com` | no (local only) |\n| Transports | Streamable HTTP | HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | AGPL-3.0 | Proprietary service under the SugarAI Customer Terms of Service |\n| Tools exposed | 50 | none |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | no |\n| MCP registry | `com.relaticle/crm` | not listed |\n| Last release | 2026-11-05 | none |\n| Terms last updated | 2026-08-26 | not read yet |\n| Privacy policy last updated | 2026-11-04 | no date given |\n| Customer content may train models | not found in the text | not read yet |\n| Terms restrict automated access | not found in the text | not read yet |\n| Terms restrict benchmarking | not found in the text | not read yet |\n| Terms or service can change without notice | not found in the text | not read yet |\n| Arbitration or class-action waiver | not found in the text | not read yet |\n| Popularity | 1.8k stars | none |\n\n## How the scores have moved\n\n### Relaticle\n\nNo score change since it was listed.\n\n### SugarAI (SugarCRM)\n\n- -2.2 on 4 November 2026: correction\n- -0.2 on 30 October 2026: checklist\n- -0.1 on 28 October 2026: correction\n\n## Verdicts\n\n**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.\n\n**SugarAI (SugarCRM).** The REST reference covers 350 endpoint pages with filters, field selection, bulk calls and upsert by `sync_key`. SugarAI's AI Supplemental Terms forbid connecting a customer's or third party's AI agent or MCP connector to the APIs unless Sugar has approved it, tokens carry no scopes, and no OpenAPI file, trial or SLA was found.\n\n## Before you call either\n\n### Relaticle\n\n1. Use a personal access token with only the read permission unless the task writes, since OAuth grants every tool\n2. Ask the user before create, update, delete or send tools; the server applies them at once\n3. Call `get-crm-schema-tool` for an entity before filtering on custom fields, which differ by workspace\n4. Use `POST /v1/people/upsert` or `/v1/companies/upsert` with a unique field to avoid duplicates on retry\n5. Keep MCP calls under 120 a minute per user and REST writes under 60 a minute per token on Cloud Pro\n\n### SugarAI (SugarCRM)\n\n1. Confirm that Sugar has approved the agent integration before connecting. The AI Supplemental Terms forbid unapproved AI agents and MCP connectors on the APIs\n2. POST to `/rest/v11_27/oauth2/token` with `grant_type` `password` and a `platform` other than `base`, `mobile` or `portal`, or the login can end the user's own session\n3. Send the access token in the `OAuth-Token` header. It lasts 60 minutes by default, so store the refresh token and not the password\n4. Stay under 20 requests a second on SugarCloud and reuse one session for batches. Over-limit traffic is blocked by IP address until support lifts it\n5. Page with `max_num` and `offset` until `next_offset` is -1, and pass `fields` to keep responses small\n6. Use `PATCH /integrate/:module/:sync_key_field_name/:sync_key_field_value` for writes that may be retried, since it inserts or updates by `sync_key`\n\n## Questions\n\n### Which is better for AI agents, Relaticle or SugarAI (SugarCRM)?\n\nRelaticle scores 59.6 (C) on agent readiness against SugarAI (SugarCRM)'s 47.2 (D), and leads in 5 of 7 scored categories. SugarAI (SugarCRM) leads on reliability and agent ergonomics.\n\n### Do Relaticle and SugarAI (SugarCRM) need an API key?\n\nRelaticle takes an API key or an OAuth sign-in. SugarAI (SugarCRM) uses an OAuth sign-in.\n\n### Can an agent call Relaticle and SugarAI (SugarCRM) without installing anything?\n\nRelaticle has a hosted endpoint at https://mcp.relaticle.com. No hosted endpoint is listed for SugarAI (SugarCRM).\n\n### Are Relaticle and SugarAI (SugarCRM) open source?\n\nRelaticle is open source (AGPL-3.0). No open-source release is listed for SugarAI (SugarCRM).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/relaticle-vs-sugarcrm.json, and with the fewest tokens: https://www.anchorterminal.com/compare/relaticle-vs-sugarcrm.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"relaticle\", \"b\": \"sugarcrm\"}`. From a terminal: `anchor compare relaticle sugarcrm`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/relaticle.json and https://www.anchorterminal.com/api/v1/tools/sugarcrm.json\n\n## Other comparisons with Relaticle or SugarAI (SugarCRM)\n\n- [Affinity vs Relaticle](https://www.anchorterminal.com/compare/affinity-vs-relaticle.md)\n- [Affinity vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/affinity-vs-sugarcrm.md)\n- [Attio API + MCP vs Relaticle](https://www.anchorterminal.com/compare/attio-vs-relaticle.md)\n- [Attio API + MCP vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/attio-vs-sugarcrm.md)\n- [Breakcold vs Relaticle](https://www.anchorterminal.com/compare/breakcold-vs-relaticle.md)\n- [Breakcold vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/breakcold-vs-sugarcrm.md)\n- [Capsule CRM vs Relaticle](https://www.anchorterminal.com/compare/capsule-crm-vs-relaticle.md)\n- [Capsule CRM vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/capsule-crm-vs-sugarcrm.md)\n- [Close API + MCP vs Relaticle](https://www.anchorterminal.com/compare/close-vs-relaticle.md)\n- [Close API + MCP vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/close-vs-sugarcrm.md)\n- [Copper API vs Relaticle](https://www.anchorterminal.com/compare/copper-vs-relaticle.md)\n- [Copper API vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/copper-vs-sugarcrm.md)\n- [Microsoft Dynamics 365 Sales vs Relaticle](https://www.anchorterminal.com/compare/dynamics-365-sales-vs-relaticle.md)\n- [Microsoft Dynamics 365 Sales vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/dynamics-365-sales-vs-sugarcrm.md)\n- [folk API + MCP vs Relaticle](https://www.anchorterminal.com/compare/folk-vs-relaticle.md)\n- [folk API + MCP vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/folk-vs-sugarcrm.md)\n- [Freshsales API vs Relaticle](https://www.anchorterminal.com/compare/freshsales-vs-relaticle.md)\n- [Freshsales API vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/freshsales-vs-sugarcrm.md)\n- [HubSpot API + MCP vs Relaticle](https://www.anchorterminal.com/compare/hubspot-mcp-vs-relaticle.md)\n- [HubSpot API + MCP vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/hubspot-mcp-vs-sugarcrm.md)\n- [Nutshell vs Relaticle](https://www.anchorterminal.com/compare/nutshell-vs-relaticle.md)\n- [Nutshell vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/nutshell-vs-sugarcrm.md)\n- [Payani AI vs Relaticle](https://www.anchorterminal.com/compare/payani-ai-vs-relaticle.md)\n- [Payani AI vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/payani-ai-vs-sugarcrm.md)\n- [Pipedrive API + MCP vs Relaticle](https://www.anchorterminal.com/compare/pipedrive-vs-relaticle.md)\n- [Pipedrive API + MCP vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/pipedrive-vs-sugarcrm.md)\n- [Relaticle vs Salesflare](https://www.anchorterminal.com/compare/relaticle-vs-salesflare.md)\n- [Relaticle vs Salesforce API + MCP](https://www.anchorterminal.com/compare/relaticle-vs-salesforce.md)\n- [Relaticle vs Streak API + MCP](https://www.anchorterminal.com/compare/relaticle-vs-streak.md)\n- [Relaticle vs Twenty API + MCP](https://www.anchorterminal.com/compare/relaticle-vs-twenty.md)\n- [Relaticle vs Zoho CRM](https://www.anchorterminal.com/compare/relaticle-vs-zoho-crm.md)\n- [Salesflare vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/salesflare-vs-sugarcrm.md)\n- [Salesforce API + MCP vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/salesforce-vs-sugarcrm.md)\n- [Streak API + MCP vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/streak-vs-sugarcrm.md)\n- [SugarAI (SugarCRM) vs Twenty API + MCP](https://www.anchorterminal.com/compare/sugarcrm-vs-twenty.md)\n- [SugarAI (SugarCRM) vs Zoho CRM](https://www.anchorterminal.com/compare/sugarcrm-vs-zoho-crm.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Relaticle vs SugarAI (SugarCRM)", "url": "" } ], "description": "Relaticle scores 59.6 (C) to SugarAI's 47.2 (D) for crm records. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Relaticle C 59.6", "SugarAI (SugarCRM) D 47.2", "scores" ], "h1": "Relaticle vs SugarAI (SugarCRM)", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/relaticle-vs-sugarcrm", "published": "2026-10-01", "section": "tools", "title": "Relaticle vs SugarAI for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/relaticle-vs-sugarcrm" }, "tokens": { "markdown": 5650, "slim": 3380 }, "version": 1 }