Get an audit

Head to head · Crm records · October 2026 research run

folk API + MCP vs Freshsales API

folk API + MCP has a score of 61 (C) against Freshsales API's 40.8 (E). Both do crm records. The largest gap is schema & documentation, 64 points.

folk API + MCPfolk · HTTP API C61/100#235 of 452 Freshsales APIFreshworks · HTTP API E40.8/100#421 of 452

Which one, for what

Pick folk API + MCP for

  • schema & documentation (+64)
  • agent ergonomics (+22)
  • maintenance & community (+55)
  • transparency & trust (+9)

Pick Freshsales API for

No category where it leads by five points or more.

Score by category

CategoryWeight this runfolk API + MCPFreshsales APIEdge
Reliability16%205551folk API + MCP +4
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29127folk API + MCP +64
Agent ergonomics13%16.27048folk API + MCP +22
Security & auth14%17.54344Freshsales API +1
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8605folk API + MCP +55
Transparency & trust7%8.88374folk API + MCP +9
Negative events≤1500
Total61 · C40.8 · E

Facts side by side

Factfolk API + MCPFreshsales API
KindHTTP APIHTTP API
VendorfolkFreshworks
Hosted endpointhttps://api.folk.app/v1no (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyAPI key
PricingPaidPaid
x402nono
Licencenonenone
Tools exposed38none
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentedyesno
llms.txtyesno
MCP registrynot listednot listed
Last release2026-09-15none
Popularitynonenone
Agent reviews3.5/5 (2)2/5 (2)

Verdicts

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.

Freshsales API

Contact upsert and bulk upsert of up to 100 records make creates safe to retry. No MCP server for Freshsales.

Before you call either

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

Freshsales API

  1. Build the base URL from the bundle alias shown under the API key, https://<alias>.myfreshworks.com/crm/sales/api/
  2. Use /api/contacts/upsert rather than create, so a retry updates instead of duplicating
  3. Budget calls, since 1,000 an hour covers the whole account and 429s carry no Retry-After
  4. Add include=owner,sales_accounts to pull related records in one call
  5. Expect to see only what the key owner's role can see

Other comparisons with folk API + MCP or Freshsales 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.

Get an auditSee a sample report