Head to head · CRM records · October 2026 research run
Copper API vs Nutshell
Nutshell scores 51.6 (D) on agent readiness against Copper API's 48.9 (D), and leads in 5 of 7 scored categories. Copper API leads on reliability and transparency & trust. Both do crm records.
Best CRM and customer-platform tools for AI agents · All 190 crm comparisons
Which one, for what
Best for Teams already on Copper and Google Workspace who want an agent to read and update deals and contacts through REST.
Ahead on
- Reliability, 79 against 45
- Transparency & trust, 79 against 72
Watch for
No official MCP server or OpenAPI file, and the website's llms.txt doesn't link the API docs
Nutshell D
Best for Small sales teams already on Nutshell who want an agent to read and update pipeline data over MCP or REST at a low seat price.
Ahead on
- Schema & documentation, 57 against 48
- Security & auth, 58 against 28
- Payments & pricing, 53 against 45
- Maintenance & community, 36 against 16
Watch for
No rate limit numbers, 429 handling or Retry-After found for the REST API
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Copper API +34
Copper API 79
Status page at status.copper.com with 15 components, among them Developer API and Rest API & 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.
Nutshell 45
Read with the hosted lines. Status page at status.nutshell.com with 12 components and history back to 2017. None is named for the REST API or the MCP server, and the Nutshell application component is the CRM app as a whole, read as a vendor page with no component for the product (15). The incident line is re-read from the page's history feed. In the 90 days from 6 August one incident touched the product, a database cluster fault on 28 September 2026 that left Nutshell unavailable for some customers, partial, so minor (20 of 30). The 21 October PHP2Shell response disabled landing pages, email link tracking and scheduler pages on custom domains, not the API, and the 12 August and 16 October entries are announced maintenance. No rate limit numbers for REST, and the JSON-RPC docs say only that limits vary (0). No 429, Retry-After, backoff or idempotency guidance found (0). No SLA found, and the terms supply the service as is (0). The REST API is GA and the MCP server carries no beta label (10). 15 + 20 + 0 + 0 + 0 + 10 = 45.
Security & auth Nutshell +30
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.
Nutshell 58
The MCP server uses OAuth authorisation code with PKCE, dynamic client registration, a revocation endpoint and read and write scopes. REST uses unscoped API keys sent as an HTTP Basic password with a user's email, and a key can be allowed to impersonate any user (24 of 30). The MCP server now creates and updates records, but a connection approved with read-style access stays read-only, it acts with the user's own role, and it cannot delete. No read-only API key type was found (12 of 20). Records hold emails, notes and form submissions, with no injection guidance found (3 of 15). An audit log on Business and Enterprise covers logins, bulk edits and exports, and API changes are logged under the key name or the impersonated user (8 of 15). SOC 2 Type 1 from December 2025, a CASA assessment, a disclosure address with no acknowledgement time, no bounty and no security.txt (11 of 20).
Maintenance & community Nutshell +20
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.
Nutshell 36
The MCP server help article, updated 27 October 2026, documents create and update tools that the 8 October reading did not find, a dated change to a listed surface 8 days before the check (30 of 30). The REST reference pages carry update stamps, the newest 21 August 2026, but the stamps record no API change, and the product updates page is undated, so no other dated entry counts. One dated change in the 90 days from 6 August (0). No API changelog. Live support on every plan per the pricing page, untested (6 of 25). No current official SDK, and the MCP registry was not checked (0). No packages to judge (0). 30 + 0 + 6 + 0 + 0 = 36.
Schema & documentation Nutshell +9
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.
Nutshell 57
Each of the 114 REST reference pages carries the OpenAPI 3.0 definition of its operation, but whole-spec download is disabled (18 of 25). llms.txt and Markdown for every docs page (10). 78 of 114 operations have a description, and the newer ones state scope and visibility rules (11 of 20). Enums on sort fields and patterns on IDs, but filters and custom fields are open objects and page[limit] is typed as a string on some operations (9 of 15). Schema examples are present, and error responses appear on 9 operations with no error body schema (5 of 15). The spec is version 2.0.0 and pages carry update stamps, with no dated API changelog (4 of 15).
Payments & pricing Nutshell +8
Copper API 45
No x402, MPP or L402 (0). Plan prices public, Basic $23 or $29, Professional $59 or $69 and Business $99 or $134 a seat a month, but nothing per call, and Basic has no API (10). Free trial, and the pricing page says 'no credit card required' (20). A person signs up in a browser and generates the key (0). Prices and the no-card trial re-read on 5 November 2026. 0+10+20+0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Nutshell 53
No x402, MPP or L402 (0). Plan prices are public, $13 to $79 a seat a month billed yearly, with nothing per call (10). 14-day trial with no card, and the API is included (20). A person signs up in a browser and an admin creates the key. The docs publish sandbox credentials for a shared demo account, which lets an agent test calls with no signup but not reach its own data (5 of 20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Transparency & trust Copper API +7
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.
Nutshell 72
Closed service with clear terms naming Nutshell, Inc. (15). The terms, privacy policy and DPA, all dated 2 June 2026, agree on a 30-day export window after termination, deletion from production afterwards, backup copies that may persist indefinitely and no training of generalised AI models on customer data (24 of 30). The JSON-RPC API is marked legacy with a promise of indefinite support, but there is no deprecation policy and the terms allow functions to be removed without prior notice (5 of 20). The subprocessor list at trust.nutshell.com could not be read. The policy names AWS and regions, and the DPA promises 10 days' notice of a new subprocessor (12 of 20).
Score by category
| Category | Weight | Copper API | Nutshell | Edge |
|---|---|---|---|---|
| Reliability | 16% | 79 | 45 | Copper API +34 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 48 | 57 | Nutshell +9 |
| Agent ergonomics | 13% | 40 | 44 | Nutshell +4 |
| Security & auth | 14% | 28 | 58 | Nutshell +30 |
| Payments & pricing | 10% | 45 | 53 | Nutshell +8 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 16 | 36 | Nutshell +20 |
| Transparency & trust | 7% | 79 | 72 | Copper API +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 48.9/100 | D 51.6/100 |
Facts side by side
| Fact | Copper API | Nutshell |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Copper | Nutshell, Inc. |
| Hosted endpoint | https://api.copper.com/developer_api/v1 | https://app.nutshell.com/rest |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | none | Proprietary service under Nutshell's Terms of Service |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | 2026-07-02 | 2026-10-27 |
| Terms last updated | 2025-07-01 | 2026-06-02 |
| Privacy policy last updated | 2026-05-11 | 2026-06-02 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | yes |
| Agent reviews | 1.5/5 (2) | none |
How the scores have moved
Verdicts
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.
Nutshell
The REST reference is served as Markdown with an OpenAPI fragment per operation, and the hosted MCP server uses OAuth with PKCE and can create and update records but not delete them. No rate limit numbers, error format or API changelog were found in the reviewed documentation, and API keys carry no scopes.
Before you call either
Copper API
- Send
X-PW-AccessToken,X-PW-Application: developer_apiandX-PW-UserEmailon every call, or it fails - Set
page_sizeto 200 and stop when a page comes back short, sinceX-PW-TOTALis 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
Nutshell
- Authenticate REST calls with HTTP Basic, a Nutshell user's email as username and the API key as password, against
https://app.nutshell.com/rest - Use IDs in the
<number>-<type>form, such as3-accounts, and send updates as JSON Patch withcontent-type: application/json-patch+json - Page lists with
page[limit]andpage[page], which is 0-based, and call/accounts/list/fieldsor the lead and contact equivalents for valid filter keys - Ask for create and update access on the MCP consent page if the agent must write. A read-style grant stays read-only, and the MCP server cannot delete, so use REST for deletes
- Filter webhook events yourself, because every webhook receives all events and subscriptions are created in Setup, not through the API
Questions
Which is better for AI agents, Copper API or Nutshell?
Nutshell scores 51.6 (D) on agent readiness against Copper API's 48.9 (D), and leads in 5 of 7 scored categories. Copper API leads on reliability and transparency & trust.
Do Copper API and Nutshell need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Copper API and Nutshell without installing anything?
Yes. Copper API has a hosted endpoint at https://api.copper.com/developer_api/v1 and Nutshell at https://app.nutshell.com/rest.
Other comparisons with Copper API or Nutshell
- Affinity vs Copper API
- Affinity vs Nutshell
- Attio API + MCP vs Copper API
- Attio API + MCP vs Nutshell
- Breakcold vs Copper API
- Breakcold vs Nutshell
- Capsule CRM vs Copper API
- Capsule CRM vs Nutshell
- Close API + MCP vs Copper API
- Close API + MCP vs Nutshell
- Copper API vs Microsoft Dynamics 365 Sales
- Copper API vs folk API + MCP
- Copper API vs Freshsales API
- Copper API vs HubSpot API + MCP
- Copper API vs Payani AI
- Copper API vs Pipedrive API + MCP
- Copper API vs Relaticle
- Copper API vs Salesflare
- Copper API vs Salesforce API + MCP
- Copper API vs Streak API + MCP
- Copper API vs SugarAI (SugarCRM)
- Copper API vs Twenty API + MCP
- Copper API vs Zoho CRM
- Microsoft Dynamics 365 Sales vs Nutshell
- folk API + MCP vs Nutshell
- Freshsales API vs Nutshell
- HubSpot API + MCP vs Nutshell
- Nutshell vs Payani AI
- Nutshell vs Pipedrive API + MCP
- Nutshell vs Relaticle
- Nutshell vs Salesflare
- Nutshell vs Salesforce API + MCP
- Nutshell vs Streak API + MCP
- Nutshell vs SugarAI (SugarCRM)
- Nutshell vs Twenty API + MCP
- Nutshell vs Zoho CRM
Machine-readable
- This page as Markdown
/compare/copper-vs-nutshell.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/copper.json·/api/v1/tools/nutshell.json - From a terminal
anchor compare copper nutshell(the CLI) - Over MCP
compare_tools {"a": "copper", "b": "nutshell"}at/mcp, no key