{ "data": { "a": { "slug": "copper", "name": "Copper API", "vendor": "Copper", "vendorUrl": "https://www.copper.com", "kind": "http-api", "category": "crm", "summary": "REST API for Copper, the CRM built around Google Workspace.", "url": "https://www.anchorterminal.com/tools/copper", "markdownUrl": "https://www.anchorterminal.com/tools/copper.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/copper.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/copper.json", "dns": "copper.grade.anchorterminal.com", "transports": [ "http" ], "remoteUrl": "https://api.copper.com/developer_api/v1", "packages": [], "auth": "mixed", "authNotes": "Personal API key sent in the `X-PW-AccessToken` header together with `X-PW-Application: developer_api` and `X-PW-UserEmail` (the email of the key's owner). Keys are generated under System settings, API Keys, and admins can see every user's keys. OAuth 2.0 (added 2023-08-11) is the route for partner integrations.", "pricing": "paid", "pricingNotes": "No free plan, only a trial, and the pricing page says no card is needed. The security page gives the trial as 14 days. Basic $29 a seat a month billed monthly or $23 billed yearly (2,500 contacts), Professional $69 or $59 (15,000 contacts), Business $134 or $99 (unlimited contacts). API access is documented for Professional, Business and the trial, not Basic (https://www.copper.com/pricing).", "priceSummary": "$59 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No payments. API access follows the Copper subscription.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://developer.copper.com", "capabilities": [ "crm.records", "crm.pipeline", "crm.activities", "crm.search", "crm.webhooks" ], "tags": [ "hosted", "closed-source", "webhooks", "no-card" ], "lastRelease": "2026-07-02", "graded": true, "anchor": { "graded": true, "score": 47.1, "grade": "D", "agentReady": false, "rank": 1160, "ranked": true, "rankOf": 1510, "categoryRank": 15, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 40, "maintenance": 16, "payments": 30, "reliability": 79, "schema": 48, "security": 28, "transparency": 79 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-05" }, "negative": 0, "verdict": "Published limits of 180 requests a minute and 3 a second for bulk endpoints, and a change policy with at least six months of support for deprecated APIs. No official MCP server or OpenAPI file, and API keys carry their owner's full rights with no scopes.", "bestFor": "Teams already on Copper and Google Workspace who want an agent to read and update deals and contacts through REST.", "strengths": [ "Published limits of 180 requests a minute and 3 a second for bulk endpoints", "Change policy promises notice by email and docs, and at least six months of support, before breaking changes", "No status incidents between 7 August and 5 November 2026, with a Developer API component on the status page", "Privacy policy states US-only hosting, a 180-day purge after expiry and no AI training on Workspace API data", "Trial with no card, per the pricing page" ], "weaknesses": [ "No official MCP server or OpenAPI file, and the website's llms.txt doesn't link the API docs", "API keys carry the owner's full rights, and admins can see every user's key", "No documented error format, Retry-After or idempotency", "Basic plan has no API access, so the first plan with it costs $59 a seat a month yearly", "Three changelog entries in 2026, the newest API change on 2 July, and bulk endpoints still beta since 2023" ], "agentNotes": [ "Send `X-PW-AccessToken`, `X-PW-Application: developer_api` and `X-PW-UserEmail` on every call, or it fails", "Set `page_size` to 200 and stop when a page comes back short, since `X-PW-TOTAL` is only an upper bound", "Back off on 429 on your own clock, since no Retry-After is documented", "Narrow searches that would pass 100,000 records, which is where results stop", "Read connect fields before you update a record, because an update that omits them can delete connections" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 1.5, "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.1 } ], "editorialScores": { "ergonomics": 40, "maintenance": 16, "payments": 30, "reliability": 79, "schema": 48, "security": 28, "transparency": 72 }, "provenanceScore": 86, "checked": { "categories": { "ergonomics": "2026-11-05", "maintenance": "2026-11-05", "payments": "2026-11-05", "reliability": "2026-11-05", "schema": "2026-11-05", "security": "2026-11-05", "transparency": "2026-11-05" }, "last": "2026-11-05", "lastMoved": "2026-11-05", "oldest": "2026-11-05", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.copper.com/developer_api/v1/account \\\n -H \"X-PW-AccessToken: $COPPER_API_KEY\" -H \"X-PW-Application: developer_api\" \\\n -H \"X-PW-UserEmail: $COPPER_USER_EMAIL\" -H \"Content-Type: application/json\"" }, "letme": { "capability": "https://letme.dev/crm.records", "tool": "https://letme.dev/copper" }, "area": "business", "unitPrices": [ { "item": "Professional (first plan with API access)", "unit": "seat-month", "usd": 59, "note": "billed yearly; $69 billed monthly" }, { "item": "Business", "unit": "seat-month", "usd": 99, "note": "billed yearly; $134 billed monthly" }, { "item": "Basic (no API access)", "unit": "seat-month", "usd": 23, "note": "billed yearly; $29 billed monthly" } ], "provenance": { "legalEntity": "Copper CRM, Inc.", "domain": "copper.com", "domainRegistered": "1994-02-07", "domainNote": "copper.com was registered in 1994, long before the company renamed itself from ProsperWorks.", "endpointOnVendorDomain": true, "terms": "https://www.copper.com/terms", "privacy": "https://www.copper.com/privacy", "statusPage": "https://status.copper.com", "changelog": "https://developer.copper.com/introduction/changelog.html", "securityTxt": "none", "checked": "2026-11-05", "score": 86 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/copper.json", "live": { "slug": "copper", "probe": { "target": "https://api.copper.com/developer_api/v1", "method": "get", "lastAt": "2026-11-07T19:22:01.400763Z", "lastOk": true, "lastStatus": 404, "lastMs": 276, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 283, "p95ms24h": 380, "samples24h": 238, "samples30d": 7920, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.copper.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:21:39.938810008Z" }, "securityTxt": { "url": "https://copper.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:55.740585211Z" }, "domain": { "domain": "copper.com", "registered": "1994-02-07", "source": "https://rdap.verisign.com/com/v1/domain/copper.com", "checkedAt": "2026-11-01T14:22:19.335982652Z" }, "pages": [ { "url": "https://developer.copper.com/introduction/changelog.html", "kind": "changelog", "status": 304, "checkedAt": "2026-11-07T14:03:02.035030077Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3189aee56061" }, { "url": "https://www.copper.com/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:27:26.340538898Z", "changedAt": "2026-10-27T03:59:36.989502577Z", "fingerprint": "aeddeadc00c8" }, { "url": "https://www.copper.com/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:27:28.414330533Z", "changedAt": "2026-10-27T03:59:39.052898555Z", "fingerprint": "f9e257003a2a" }, { "url": "https://www.copper.com/terms", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:27:35.89794144Z", "changedAt": "2026-10-27T03:59:41.10357547Z", "fingerprint": "65e534407bd6" } ], "updatedAt": "2026-11-07T19:22:01.400763Z" } }, "answer": "Relaticle scores 59.6 (C) on agent readiness against Copper API's 47.1 (D), and leads in 4 of 7 scored categories. Copper API leads on reliability and transparency \u0026 trust.", "b": { "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": 697, "ranked": true, "rankOf": 1510, "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-07T19:22:29.462221932Z", "lastOk": true, "lastStatus": 405, "lastMs": 164, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 174, "p95ms24h": 294, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "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-07T19:22:29.462221932Z" } }, "edges": [ { "by": 74, "category": "maintenance", "leads": "relaticle", "name": "Maintenance \u0026 community", "reasons": { "a": "Last API change on 2 July 2026 (S3 upload token), 126 days before this check. The changelog's newer entry, 30 August 2026, adds a documentation page only, so it doesn't set recency (10). Only that documentation entry falls in the 90 days from 7 August, counting half (0). Public changelog with three entries in 2026 and a support centre. We didn't test support (6 of 15, the earlier partial, kept). No official SDK in any language (0). No packages to judge (0). 10+0+6+0+0 = 16.", "b": "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." }, "scores": { "a": 16, "b": 90 } }, { "by": 39, "category": "reliability", "leads": "copper", "name": "Reliability", "reasons": { "a": "Status page at status.copper.com with 15 components, among them Developer API and Rest API \u0026 Web Application, read from its history page on 5 November 2026 (20). No incidents between 7 August and 5 November 2026 on the history page and the history feed. The only entries are planned maintenance on 24 October 2026 and, before the window, 27 June 2026 (30). Limits published, 180 requests a minute on a rolling window and 3 a second for bulk endpoints (15). 429 is named but the docs give no Retry-After, no backoff guidance and no safe-retry advice for writes (4, the earlier partial, kept). No SLA found (0). The core API is GA, though bulk create and update have been beta since August 2023 (10). 20+30+15+4+0+10 = 79.", "b": "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." }, "scores": { "a": 79, "b": 40 } }, { "by": 38, "category": "schema", "leads": "relaticle", "name": "Schema \u0026 documentation", "reasons": { "a": "No OpenAPI spec. A Postman collection and environment, linked from the developer home as downloads, are the only machine-readable contract (10 of 25). No llms.txt or Markdown docs on the developer site. The website's llms.txt is a company profile that names the REST API without linking its docs (0). Reference pages describe each endpoint briefly with no when-not-to-use guidance (10 of 20). Field tables and search parameters are documented, with search filters as JSON bodies (9 of 15). Request and response examples, but no error code reference (7 of 15). Dated changelog, a single v1 path and a published change policy. Only three entries in 2026 (12 of 15). 10+0+10+9+7+12 = 48.", "b": "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." }, "scores": { "a": 48, "b": 86 } }, { "by": 29, "category": "security", "leads": "relaticle", "name": "Security \u0026 auth", "reasons": { "a": "Personal API keys sent in `X-PW-AccessToken` with the owner's email, carrying that user's full rights. Admins can see every user's keys. OAuth 2.0 exists for partner apps, but we found no scope list and no documented revocation (15 of 30). No read-only or scoped keys. Access follows the user's role (3 of 20). Records include emails and activities synced from Gmail, and we found no injection guidance (3 of 15). No API audit log found (0 of 15). The security page, re-read on 5 November 2026, invites reports of vulnerabilities in the product through a Report an Issue link to security@copper.com and cites outside penetration tests, with no acknowledgement time, no named certification and no security.txt (404 on 1 October). That is a disclosure route with no stated time (7). The trust centre at trust.copper.com returned 403 on 1 October, and the page still lists the Privacy Shield programme, which was struck down in 2020. 15+3+3+0+7 = 28.", "b": "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." }, "scores": { "a": 28, "b": 57 } }, { "by": 19, "category": "ergonomics", "leads": "relaticle", "name": "Agent ergonomics", "reasons": { "a": "No MCP server. Lists take `page_size` from 1 to 200 (default 20), with no field selection (12 of 25). Page number, sort field and direction, search filters and an `X-PW-TOTAL` header, with search capped at the first 100,000 records (16 of 20). Error responses aren't documented beyond the 429 (5 of 20). No idempotency keys or upserts found (3 of 20). Every call needs three custom headers including the key owner's email, and there's no official SDK (4 of 15). 12+16+5+3+4 = 40.", "b": "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." }, "scores": { "a": 40, "b": 59 } }, { "by": 6, "category": "transparency", "leads": "copper", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service with terms (last modified 1 July 2025) and a privacy policy naming Copper CRM, Inc., San Francisco (15). The privacy policy (11 May 2026) keeps CRM data at least 30 days after termination and purges it within 180 days, hosts in the US only, transfers under the Data Privacy Framework and SCCs, and says Workspace API data isn't used to train AI models. The security page still cites Privacy Shield (22 of 30). A change policy, announced in the changelog on 7 September 2021, says breaking changes are announced in the docs, the changelog, support articles and by email to API key owners, and that deprecated APIs stay supported for at least six months from the announcement. A written policy with a stated notice period (20). Subprocessor list linked from the privacy policy and US-only hosting stated (15 of 20). 15+22+20+15 = 72.", "b": "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." }, "scores": { "a": 79, "b": 73 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Copper", "b": "Relaticle, Inc.", "name": "Vendor" }, { "a": "https://api.copper.com/developer_api/v1", "b": "https://mcp.relaticle.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "AGPL-3.0", "name": "Licence" }, { "a": "none", "b": "50", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "com.relaticle/crm", "name": "MCP registry" }, { "a": "2026-07-02", "b": "2026-11-05", "name": "Last release" }, { "a": "2025-07-01", "b": "2026-08-26", "name": "Terms last updated" }, { "a": "2026-05-11", "b": "2026-11-04", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "1.8k stars", "name": "Popularity" }, { "a": "1.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Relaticle scores 59.6 (C) on agent readiness against Copper API's 47.1 (D), and leads in 4 of 7 scored categories. Copper API leads on reliability and transparency \u0026 trust.", "question": "Which is better for AI agents, Copper API or Relaticle?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Copper API and Relaticle need an API key?" }, { "answer": "Yes. Copper API has a hosted endpoint at https://api.copper.com/developer_api/v1 and Relaticle at https://mcp.relaticle.com.", "question": "Can an agent call Copper API and Relaticle without installing anything?" }, { "answer": "No open-source release is listed for Copper API. Relaticle is open source (AGPL-3.0).", "question": "Are Copper API and Relaticle open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 79 against 40", "Transparency \u0026 trust, 79 against 73" ], "also": null, "goodFor": "Teams already on Copper and Google Workspace who want an agent to read and update deals and contacts through REST.", "slug": "copper", "watchFor": "No official MCP server or OpenAPI file, and the website's llms.txt doesn't link the API docs" }, { "aheadOn": [ "Schema \u0026 documentation, 86 against 48", "Agent ergonomics, 59 against 40", "Security \u0026 auth, 57 against 28", "Maintenance \u0026 community, 90 against 16" ], "also": [ "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" } ], "history": { "copper": [ { "causes": [ "correction", "time" ], "date": "2026-11-05", "delta": 0.4, "from": 46.7, "fromGrade": "D", "to": 47.1, "toGrade": "D" }, { "causes": [ "evidence" ], "date": "2026-10-29", "delta": -0.1, "from": 46.8, "fromGrade": "D", "to": 46.7, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 46.7, "fromGrade": "D", "to": 46.8, "toGrade": "D" } ], "relaticle": null }, "job": { "capability": "crm.records", "name": "CRM records" }, "others": [ { "json": "https://www.anchorterminal.com/compare/affinity-vs-copper.json", "title": "Affinity vs Copper API", "url": "https://www.anchorterminal.com/compare/affinity-vs-copper" }, { "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/attio-vs-copper.json", "title": "Attio API + MCP vs Copper API", "url": "https://www.anchorterminal.com/compare/attio-vs-copper" }, { "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/breakcold-vs-copper.json", "title": "Breakcold vs Copper API", "url": "https://www.anchorterminal.com/compare/breakcold-vs-copper" }, { "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/capsule-crm-vs-copper.json", "title": "Capsule CRM vs Copper API", "url": "https://www.anchorterminal.com/compare/capsule-crm-vs-copper" }, { "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/close-vs-copper.json", "title": "Close API + MCP vs Copper API", "url": "https://www.anchorterminal.com/compare/close-vs-copper" }, { "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/copper-vs-dynamics-365-sales.json", "title": "Copper API vs Microsoft Dynamics 365 Sales", "url": "https://www.anchorterminal.com/compare/copper-vs-dynamics-365-sales" }, { "json": "https://www.anchorterminal.com/compare/copper-vs-folk.json", "title": "Copper API vs folk API + MCP", "url": "https://www.anchorterminal.com/compare/copper-vs-folk" }, { "json": "https://www.anchorterminal.com/compare/copper-vs-freshsales.json", "title": "Copper API vs Freshsales API", "url": "https://www.anchorterminal.com/compare/copper-vs-freshsales" }, { "json": "https://www.anchorterminal.com/compare/copper-vs-hubspot-mcp.json", "title": "Copper API vs HubSpot API + MCP", "url": "https://www.anchorterminal.com/compare/copper-vs-hubspot-mcp" }, { "json": "https://www.anchorterminal.com/compare/copper-vs-nutshell.json", "title": "Copper API vs Nutshell", "url": "https://www.anchorterminal.com/compare/copper-vs-nutshell" }, { "json": "https://www.anchorterminal.com/compare/copper-vs-payani-ai.json", "title": "Copper API vs Payani AI", "url": "https://www.anchorterminal.com/compare/copper-vs-payani-ai" }, { "json": "https://www.anchorterminal.com/compare/copper-vs-pipedrive.json", "title": "Copper API vs Pipedrive API + MCP", "url": "https://www.anchorterminal.com/compare/copper-vs-pipedrive" }, { "json": "https://www.anchorterminal.com/compare/copper-vs-salesflare.json", "title": "Copper API vs Salesflare", "url": "https://www.anchorterminal.com/compare/copper-vs-salesflare" }, { "json": "https://www.anchorterminal.com/compare/copper-vs-salesforce.json", "title": "Copper API vs Salesforce API + MCP", "url": "https://www.anchorterminal.com/compare/copper-vs-salesforce" }, { "json": "https://www.anchorterminal.com/compare/copper-vs-streak.json", "title": "Copper API vs Streak API + MCP", "url": "https://www.anchorterminal.com/compare/copper-vs-streak" }, { "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/copper-vs-twenty.json", "title": "Copper API vs Twenty API + MCP", "url": "https://www.anchorterminal.com/compare/copper-vs-twenty" }, { "json": "https://www.anchorterminal.com/compare/copper-vs-zoho-crm.json", "title": "Copper API vs Zoho CRM", "url": "https://www.anchorterminal.com/compare/copper-vs-zoho-crm" }, { "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/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/freshsales-vs-relaticle.json", "title": "Freshsales API vs Relaticle", "url": "https://www.anchorterminal.com/compare/freshsales-vs-relaticle" }, { "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/nutshell-vs-relaticle.json", "title": "Nutshell vs Relaticle", "url": "https://www.anchorterminal.com/compare/nutshell-vs-relaticle" }, { "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/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/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-sugarcrm.json", "title": "Relaticle vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/relaticle-vs-sugarcrm" }, { "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" } ], "panel": null, "scores": [ { "by": 39, "copper": 79, "edge": "copper", "key": "reliability", "name": "Reliability", "relaticle": 40, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 38, "copper": 48, "edge": "relaticle", "key": "schema", "name": "Schema \u0026 documentation", "relaticle": 86, "weight": 13 }, { "by": 19, "copper": 40, "edge": "relaticle", "key": "ergonomics", "name": "Agent ergonomics", "relaticle": 59, "weight": 13 }, { "by": 29, "copper": 28, "edge": "relaticle", "key": "security", "name": "Security \u0026 auth", "relaticle": 57, "weight": 14 }, { "by": 0, "copper": 30, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "relaticle": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 74, "copper": 16, "edge": "relaticle", "key": "maintenance", "name": "Maintenance \u0026 community", "relaticle": 90, "weight": 7 }, { "by": 6, "copper": 79, "edge": "copper", "key": "transparency", "name": "Transparency \u0026 trust", "relaticle": 73, "weight": 7 } ], "summary": "Relaticle scores 59.6 (C) on agent readiness against Copper API's 47.1 (D), and leads in 4 of 7 scored categories. Copper API leads on reliability and transparency \u0026 trust. Both do crm records.", "tasks": null, "tutorials": [], "verdicts": { "copper": "Published limits of 180 requests a minute and 3 a second for bulk endpoints, and a change policy with at least six months of support for deprecated APIs. No official MCP server or OpenAPI file, and API keys carry their owner's full rights with no scopes.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/copper-vs-relaticle", "json": "https://www.anchorterminal.com/compare/copper-vs-relaticle.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/copper-vs-relaticle.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/copper-vs-relaticle.min.md" }, "markdown": "Relaticle scores 59.6 (C) on agent readiness against Copper API's 47.1 (D), and leads in 4 of 7 scored categories. Copper API leads on reliability and transparency \u0026 trust. Both do crm records.\n\n- Copper API: grade D, 47.1/100, rank #1160 of 1510. Markdown https://www.anchorterminal.com/tools/copper.md · JSON https://www.anchorterminal.com/api/v1/tools/copper.json\n- 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\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### Copper API (D)\n\nGood for: Teams already on Copper and Google Workspace who want an agent to read and update deals and contacts through REST.\n\nAhead on:\n- Reliability, 79 against 40\n- Transparency \u0026 trust, 79 against 73\n\nWatch for: No official MCP server or OpenAPI file, and the website's llms.txt doesn't link the API docs\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 48\n- Agent ergonomics, 59 against 40\n- Security \u0026 auth, 57 against 28\n- Maintenance \u0026 community, 90 against 16\n\nAlso in its favour:\n- Open source\n\nWatch for: Writes over MCP apply immediately, and OAuth's single `mcp:use` scope authorises every tool\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Relaticle +74\n\n- Copper API (16): Last API change on 2 July 2026 (S3 upload token), 126 days before this check. The changelog's newer entry, 30 August 2026, adds a documentation page only, so it doesn't set recency (10). Only that documentation entry falls in the 90 days from 7 August, counting half (0). Public changelog with three entries in 2026 and a support centre. We didn't test support (6 of 15, the earlier partial, kept). No official SDK in any language (0). No packages to judge (0). 10+0+6+0+0 = 16.\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\n### Reliability: Copper API +39\n\n- Copper API (79): Status page at status.copper.com with 15 components, among them Developer API and Rest API \u0026 Web Application, read from its history page on 5 November 2026 (20). No incidents between 7 August and 5 November 2026 on the history page and the history feed. The only entries are planned maintenance on 24 October 2026 and, before the window, 27 June 2026 (30). Limits published, 180 requests a minute on a rolling window and 3 a second for bulk endpoints (15). 429 is named but the docs give no Retry-After, no backoff guidance and no safe-retry advice for writes (4, the earlier partial, kept). No SLA found (0). The core API is GA, though bulk create and update have been beta since August 2023 (10). 20+30+15+4+0+10 = 79.\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\n### Schema \u0026 documentation: Relaticle +38\n\n- Copper API (48): No OpenAPI spec. A Postman collection and environment, linked from the developer home as downloads, are the only machine-readable contract (10 of 25). No llms.txt or Markdown docs on the developer site. The website's llms.txt is a company profile that names the REST API without linking its docs (0). Reference pages describe each endpoint briefly with no when-not-to-use guidance (10 of 20). Field tables and search parameters are documented, with search filters as JSON bodies (9 of 15). Request and response examples, but no error code reference (7 of 15). Dated changelog, a single v1 path and a published change policy. Only three entries in 2026 (12 of 15). 10+0+10+9+7+12 = 48.\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\n### Security \u0026 auth: Relaticle +29\n\n- Copper API (28): Personal API keys sent in `X-PW-AccessToken` with the owner's email, carrying that user's full rights. Admins can see every user's keys. OAuth 2.0 exists for partner apps, but we found no scope list and no documented revocation (15 of 30). No read-only or scoped keys. Access follows the user's role (3 of 20). Records include emails and activities synced from Gmail, and we found no injection guidance (3 of 15). No API audit log found (0 of 15). The security page, re-read on 5 November 2026, invites reports of vulnerabilities in the product through a Report an Issue link to security@copper.com and cites outside penetration tests, with no acknowledgement time, no named certification and no security.txt (404 on 1 October). That is a disclosure route with no stated time (7). The trust centre at trust.copper.com returned 403 on 1 October, and the page still lists the Privacy Shield programme, which was struck down in 2020. 15+3+3+0+7 = 28.\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\n### Agent ergonomics: Relaticle +19\n\n- Copper API (40): No MCP server. Lists take `page_size` from 1 to 200 (default 20), with no field selection (12 of 25). Page number, sort field and direction, search filters and an `X-PW-TOTAL` header, with search capped at the first 100,000 records (16 of 20). Error responses aren't documented beyond the 429 (5 of 20). No idempotency keys or upserts found (3 of 20). Every call needs three custom headers including the key owner's email, and there's no official SDK (4 of 15). 12+16+5+3+4 = 40.\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\n### Transparency \u0026 trust: Copper API +6\n\n- Copper API (79): Closed service with terms (last modified 1 July 2025) and a privacy policy naming Copper CRM, Inc., San Francisco (15). The privacy policy (11 May 2026) keeps CRM data at least 30 days after termination and purges it within 180 days, hosts in the US only, transfers under the Data Privacy Framework and SCCs, and says Workspace API data isn't used to train AI models. The security page still cites Privacy Shield (22 of 30). A change policy, announced in the changelog on 7 September 2021, says breaking changes are announced in the docs, the changelog, support articles and by email to API key owners, and that deprecated APIs stay supported for at least six months from the announcement. A written policy with a stated notice period (20). Subprocessor list linked from the privacy policy and US-only hosting stated (15 of 20). 15+22+20+15 = 72.\n- 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.\n\n## Score by category\n\n| Category | Weight | Copper API | Relaticle | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 79 | 40 | Copper API +39 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 48 | 86 | Relaticle +38 |\n| Agent ergonomics | 13% (16.2 this run) | 40 | 59 | Relaticle +19 |\n| Security \u0026 auth | 14% (17.5 this run) | 28 | 57 | Relaticle +29 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 30 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 16 | 90 | Relaticle +74 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 79 | 73 | Copper API +6 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **47.1 · D** | **59.6 · C** | |\n\n## Facts side by side\n\n| Fact | Copper API | Relaticle |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Copper | Relaticle, Inc. |\n| Hosted endpoint | `https://api.copper.com/developer_api/v1` | `https://mcp.relaticle.com` |\n| Transports | HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | none | AGPL-3.0 |\n| Tools exposed | none | 50 |\n| Read-only variant documented | no | yes |\n| llms.txt | no | yes |\n| MCP registry | not listed | `com.relaticle/crm` |\n| Last release | 2026-07-02 | 2026-11-05 |\n| Terms last updated | 2025-07-01 | 2026-08-26 |\n| Privacy policy last updated | 2026-05-11 | 2026-11-04 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | none | 1.8k stars |\n| Agent reviews | 1.5/5 (2) | none |\n\n## How the scores have moved\n\n### Copper API\n\n- +0.4 on 5 November 2026: correction, time\n- -0.1 on 29 October 2026: new evidence\n- +0.1 on 27 October 2026: checklist\n\n### Relaticle\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Copper API.** Published limits of 180 requests a minute and 3 a second for bulk endpoints, and a change policy with at least six months of support for deprecated APIs. No official MCP server or OpenAPI file, and API keys carry their owner's full rights with no scopes.\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## Before you call either\n\n### Copper API\n\n1. Send `X-PW-AccessToken`, `X-PW-Application: developer_api` and `X-PW-UserEmail` on every call, or it fails\n2. Set `page_size` to 200 and stop when a page comes back short, since `X-PW-TOTAL` is only an upper bound\n3. Back off on 429 on your own clock, since no Retry-After is documented\n4. Narrow searches that would pass 100,000 records, which is where results stop\n5. Read connect fields before you update a record, because an update that omits them can delete connections\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## Questions\n\n### Which is better for AI agents, Copper API or Relaticle?\n\nRelaticle scores 59.6 (C) on agent readiness against Copper API's 47.1 (D), and leads in 4 of 7 scored categories. Copper API leads on reliability and transparency \u0026 trust.\n\n### Do Copper API and Relaticle need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Copper API and Relaticle without installing anything?\n\nYes. Copper API has a hosted endpoint at https://api.copper.com/developer_api/v1 and Relaticle at https://mcp.relaticle.com.\n\n### Are Copper API and Relaticle open source?\n\nNo open-source release is listed for Copper API. Relaticle is open source (AGPL-3.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/copper-vs-relaticle.json, and with the fewest tokens: https://www.anchorterminal.com/compare/copper-vs-relaticle.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"copper\", \"b\": \"relaticle\"}`. From a terminal: `anchor compare copper relaticle`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/copper.json and https://www.anchorterminal.com/api/v1/tools/relaticle.json\n\n## Other comparisons with Copper API or Relaticle\n\n- [Affinity vs Copper API](https://www.anchorterminal.com/compare/affinity-vs-copper.md)\n- [Affinity vs Relaticle](https://www.anchorterminal.com/compare/affinity-vs-relaticle.md)\n- [Attio API + MCP vs Copper API](https://www.anchorterminal.com/compare/attio-vs-copper.md)\n- [Attio API + MCP vs Relaticle](https://www.anchorterminal.com/compare/attio-vs-relaticle.md)\n- [Breakcold vs Copper API](https://www.anchorterminal.com/compare/breakcold-vs-copper.md)\n- [Breakcold vs Relaticle](https://www.anchorterminal.com/compare/breakcold-vs-relaticle.md)\n- [Capsule CRM vs Copper API](https://www.anchorterminal.com/compare/capsule-crm-vs-copper.md)\n- [Capsule CRM vs Relaticle](https://www.anchorterminal.com/compare/capsule-crm-vs-relaticle.md)\n- [Close API + MCP vs Copper API](https://www.anchorterminal.com/compare/close-vs-copper.md)\n- [Close API + MCP vs Relaticle](https://www.anchorterminal.com/compare/close-vs-relaticle.md)\n- [Copper API vs Microsoft Dynamics 365 Sales](https://www.anchorterminal.com/compare/copper-vs-dynamics-365-sales.md)\n- [Copper API vs folk API + MCP](https://www.anchorterminal.com/compare/copper-vs-folk.md)\n- [Copper API vs Freshsales API](https://www.anchorterminal.com/compare/copper-vs-freshsales.md)\n- [Copper API vs HubSpot API + MCP](https://www.anchorterminal.com/compare/copper-vs-hubspot-mcp.md)\n- [Copper API vs Nutshell](https://www.anchorterminal.com/compare/copper-vs-nutshell.md)\n- [Copper API vs Payani AI](https://www.anchorterminal.com/compare/copper-vs-payani-ai.md)\n- [Copper API vs Pipedrive API + MCP](https://www.anchorterminal.com/compare/copper-vs-pipedrive.md)\n- [Copper API vs Salesflare](https://www.anchorterminal.com/compare/copper-vs-salesflare.md)\n- [Copper API vs Salesforce API + MCP](https://www.anchorterminal.com/compare/copper-vs-salesforce.md)\n- [Copper API vs Streak API + MCP](https://www.anchorterminal.com/compare/copper-vs-streak.md)\n- [Copper API vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/copper-vs-sugarcrm.md)\n- [Copper API vs Twenty API + MCP](https://www.anchorterminal.com/compare/copper-vs-twenty.md)\n- [Copper API vs Zoho CRM](https://www.anchorterminal.com/compare/copper-vs-zoho-crm.md)\n- [Microsoft Dynamics 365 Sales vs Relaticle](https://www.anchorterminal.com/compare/dynamics-365-sales-vs-relaticle.md)\n- [folk API + MCP vs Relaticle](https://www.anchorterminal.com/compare/folk-vs-relaticle.md)\n- [Freshsales API vs Relaticle](https://www.anchorterminal.com/compare/freshsales-vs-relaticle.md)\n- [HubSpot API + MCP vs Relaticle](https://www.anchorterminal.com/compare/hubspot-mcp-vs-relaticle.md)\n- [Nutshell vs Relaticle](https://www.anchorterminal.com/compare/nutshell-vs-relaticle.md)\n- [Payani AI vs Relaticle](https://www.anchorterminal.com/compare/payani-ai-vs-relaticle.md)\n- [Pipedrive API + MCP vs Relaticle](https://www.anchorterminal.com/compare/pipedrive-vs-relaticle.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 SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/relaticle-vs-sugarcrm.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", "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": "Copper API vs Relaticle", "url": "" } ], "description": "Relaticle scores 59.6 (C) to Copper's 47.1 (D) for crm records. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Copper API D 47.1", "Relaticle C 59.6", "scores" ], "h1": "Copper API vs Relaticle", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/copper-vs-relaticle", "published": "2026-10-01", "section": "tools", "title": "Copper vs Relaticle for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/copper-vs-relaticle" }, "tokens": { "markdown": 4850, "slim": 2780 }, "version": 1 }