Head to head · CRM records · October 2026 research run

Breakcold vs Copper API

Breakcold scores 58 (C) on agent readiness against Copper API's 47.1 (D), and leads in 4 of 7 scored categories. Copper API leads on reliability, payments & pricing and transparency & trust. Both do crm records.

Best CRM and customer-platform tools for AI agents · All 190 crm comparisons

Which one, for what

Breakcold C

Best for Small sales teams who run outreach on email and social channels and want an agent to keep records, tasks and replies in order.

Ahead on

  • Schema & documentation, 90 against 48
  • Agent ergonomics, 67 against 40
  • Security & auth, 60 against 28
  • Maintenance & community, 60 against 16

Watch for

No status page or SLA was found; status.breakcold.com did not answer

Copper API D

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
  • Payments & pricing, 30 against 15
  • Transparency & trust, 79 against 67

Also in its favour

  • Free to start without a card

Watch for

No official MCP server or OpenAPI file, and the website's llms.txt doesn't link the API docs

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.

Maintenance & community Breakcold +44

Breakcold 60

API changelog entry on 6 November 2026 (30). More than 60 dated entries since 8 August 2026 (20). Closed service with a public API changelog, an RSS feed, a help centre and support by email; no public issue tracker (10 of 15). The CRM MCP server is not in the official MCP registry (the registry's io.github.breakcold/inboxmcp is a separate product at inbox-mcp.com), and no official SDK exists (0). No package to check (0). 30 + 20 + 10 + 0 + 0 = 60.

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.

Schema & documentation Breakcold +42

Breakcold 90

OpenAPI 3.1 contract at docs.breakcold.com/api/openapi.json with 70 operations, each with a description (25). llms.txt and a Markdown copy of each page, plus auth.md and an MCP server card (10). Tool descriptions say how to use them, such as records_create asking for every required field and a stable idempotency key and the send tools saying to send only after the user confirms (17 of 20). 84 enums and 488 required lists, with typed attribute pages for each field type (13 of 15). Every operation documents 400 to 429 responses and the error body is shown, but the spec carries only two examples (10 of 15). /api/v1, and an API changelog with dated entries and migration steps (15). 25 + 10 + 17 + 13 + 10 + 15 = 90.

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.

Reliability Copper API +34

Breakcold 45

Graded as a hosted service on the REST API and hosted MCP server. No status page is linked from the site or docs, and status.breakcold.com failed the TLS handshake (0). With no readable history the incident line scores 5. Rate limits published per organisation (600 a minute), workspace (300), identity or key (180) and route (120), for REST and MCP (15). 429 carries Retry-After and retryAfterMs, the docs give backoff guidance, and creates take an Idempotency-Key so retries return the original result (15). No SLA found in the services agreement summary, the pricing page or the docs (0). Neither surface is marked beta (10). 0 + 5 + 15 + 15 + 0 + 10 = 45.

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.

Security & auth Breakcold +32

Breakcold 60

API keys take chosen read and write scopes, an optional workspace limit and an expiry, are shown once, show activity history and can be revoked. MCP also accepts OAuth with PKCE through WorkOS AuthKit. Tokens travel in headers (30). Read-only keys are possible and message sends stay drafts until sendMode is set after the user confirms (17 of 20). The inbox returns email, LinkedIn, WhatsApp and Telegram text from outside parties, and no prompt-injection guidance was found (0). API key activity history is visible to the user; no organisation audit log was found (7 of 15). A vulnerability disclosure policy (3 September 2026) with reports to support@breakcold.com, no bounty, no security.txt (404) and no SOC 2 or ISO 27001 found (6 of 20). 30 + 17 + 0 + 7 + 6 = 60.

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.

Agent ergonomics Breakcold +27

Breakcold 67

72 MCP tools (5), with tools_search and capabilities_list to find tools by capability or granted scope, and scopes that limit which tools apply (8 back). Cursor pagination, record search and a fields selection on record lists since 3 November (18 of 20). Errors carry a code, message, requestId and retryAfterMs, and the 4 November changelog removed stack frames from messages (17 of 20). Idempotency keys on creates, and compose and send tools return a non-sending draft by default; MCP annotations are not published (14 of 20). No official SDK; setup is one URL with OAuth (5 of 15). 13 + 18 + 17 + 14 + 5 = 67.

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.

Payments & pricing Copper API +15

Breakcold 15

No x402, MPP or L402 (0). Plan prices are public, and each call's cost in usage tokens is published, but the money value of a token is not (10). The 14-day trial needs a card (0). auth.md documents an agent identity endpoint that takes an identity assertion or an anonymous request followed by a claim by a person, which we read and did not call; access still needs a paid or card-backed trial account (5 of 20). 0 + 10 + 0 + 5 = 15.

Copper API 30

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.

Score by category

CategoryWeight this runBreakcoldCopper APIEdge
Reliability16%204579Copper API +34
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29048Breakcold +42
Agent ergonomics13%16.26740Breakcold +27
Security & auth14%17.56028Breakcold +32
Payments & pricing10%12.51530Copper API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86016Breakcold +44
Transparency & trust7%8.86779Copper API +12
Negative events≤1500
TotalC 58/100D 47.1/100

Facts side by side

FactBreakcoldCopper API
KindHTTP APIHTTP API
VendorLogike SASCopper
Hosted endpointhttps://mcp.breakcold.com/mcp/v1https://api.copper.com/developer_api/v1
TransportsStreamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
Tools exposed72none
Read-only variant documentednono
llms.txtyesno
Last release2026-11-062026-07-02
Terms last updatedcouldn't be read2025-07-01
Privacy policy last updatedcouldn't be read2026-05-11
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readyes
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readyes
Agent reviewsnone1.5/5 (2)

How the scores have moved

Verdicts

Breakcold

Breakcold's API and hosted MCP server are built for agents, with an OpenAPI contract, scoped and expiring keys, published rate limits, idempotency keys and message sends that stay drafts until confirmed. No status page, SLA or security certification was found, and the only trial needs a card on a plan from $99 a month.

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.

Before you call either

Breakcold

  1. Call capabilities_list or tools_search first to see which tools the granted scopes allow
  2. Send an Idempotency-Key on REST creates and a stable idempotency key on records_create, so retries return the original result
  3. Leave sendMode unset on compose and send tools until the user has confirmed the message
  4. Pass fields on record lists to cut the response to the fields you need
  5. On 429 wait for Retry-After or retryAfterMs; over MCP the error code is -32029

Copper API

  1. Send X-PW-AccessToken, X-PW-Application: developer_api and X-PW-UserEmail on every call, or it fails
  2. Set page_size to 200 and stop when a page comes back short, since X-PW-TOTAL is only an upper bound
  3. Back off on 429 on your own clock, since no Retry-After is documented
  4. Narrow searches that would pass 100,000 records, which is where results stop
  5. Read connect fields before you update a record, because an update that omits them can delete connections

Questions

Which is better for AI agents, Breakcold or Copper API?

Breakcold scores 58 (C) on agent readiness against Copper API's 47.1 (D), and leads in 4 of 7 scored categories. Copper API leads on reliability, payments & pricing and transparency & trust.

Do Breakcold and Copper API need an API key?

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

Can an agent call Breakcold and Copper API without installing anything?

Yes. Breakcold has a hosted endpoint at https://mcp.breakcold.com/mcp/v1 and Copper API at https://api.copper.com/developer_api/v1.

Other comparisons with Breakcold or Copper API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.