Get an audit

Head to head · Crm records · October 2026 research run

Copper API vs folk API + MCP

folk API + MCP has a score of 61 (C) against Copper API's 46.9 (D). Both do crm records. The largest gap is schema & documentation, 43 points.

Copper APICopper · HTTP API D46.9/100#392 of 452 folk API + MCPfolk · HTTP API C61/100#235 of 452

Which one, for what

Pick Copper API for

  • reliability (+24)

Pick folk API + MCP for

  • schema & documentation (+43)
  • agent ergonomics (+30)
  • security & auth (+16)
  • maintenance & community (+39)
  • transparency & trust (+9)

Score by category

CategoryWeight this runCopper APIfolk API + MCPEdge
Reliability16%207955Copper API +24
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24891folk API + MCP +43
Agent ergonomics13%16.24070folk API + MCP +30
Security & auth14%17.52743folk API + MCP +16
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82160folk API + MCP +39
Transparency & trust7%8.87483folk API + MCP +9
Negative events≤1500
Total46.9 · D61 · C

Facts side by side

FactCopper APIfolk API + MCP
KindHTTP APIHTTP API
VendorCopperfolk
Hosted endpointhttps://api.copper.com/developer_api/v1https://api.folk.app/v1
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
Licencenonenone
Tools exposednone38
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednoyes
llms.txtnoyes
MCP registrynot listednot listed
Last release2026-07-022026-09-15
Popularitynonenone
Agent reviews1.5/5 (2)3.5/5 (2)

Verdicts

Copper API

Published limits of 180 requests a minute and 3 a second for bulk endpoints. No official MCP server, OpenAPI spec or llms.txt.

folk API + MCP

Dated API versions, a year's support and 6 months' deprecation notice with Deprecation and Sunset headers. MCP server in open beta since 1 July 2026.

Before you call either

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

folk API + MCP

  1. Send X-API-Version: 2025-06-09 on every REST call
  2. Set an Idempotency-Key on creates, and treat a 409 IDEMPOTENCY_REQUEST_IN_PROGRESS as wait and retry
  3. On a 429, wait until details.retryAfter, and remember all your keys share one 600-a-minute budget
  4. Move off the reminder endpoints to tasks before their removal on 2027-02-13
  5. Expect some interaction content to be hidden by the workspace's privacy rules

Other comparisons with Copper API or folk API + MCP

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.

Get an auditSee a sample report