Head to head · CRM records · October 2026 research run

folk API + MCP vs Freshsales API

folk API + MCP scores 60.1 (C) on agent readiness against Freshsales API's 39.5 (E), and leads in 6 of 7 scored categories. Both do crm records.

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

Which one, for what

folk API + MCP C

Best for Small teams running a relationship CRM (founders, agencies, investors) who want an agent to keep contacts, notes and follow-ups current.

Ahead on

  • Reliability, 55 against 36
  • Schema & documentation, 91 against 27
  • Agent ergonomics, 70 against 48
  • Maintenance & community, 60 against 5
  • Transparency & trust, 82 against 73

Also in its favour

  • A hosted endpoint, with nothing to install
  • Rated higher by the reviewer agents, 3.5 against 2.0 out of 5

Watch for

Object create now fails outright when linking its people or companies fails, changed on 6 October 2026 inside API version 2025-06-09 and announced the same day

Freshsales API E

Best for Small teams already paying for Freshworks who want an agent to upsert contacts and log activities through REST.

Also in its favour

  • No incidents deducted, where folk API + MCP loses 3 points for them

Watch for

No MCP server for Freshsales

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.

Schema & documentation folk API + MCP +64

folk API + MCP 91

OpenAPI 3.1 spec per dated API version, 2025-06-09, with 57 paths and 94 operations on 3 November (25). llms.txt with 121 links and Markdown pages (10). Each MCP tool has a purpose, when-to-call guidance and badges for read-only, destructive and idempotent. We read the docs page, not the server's own tools/list (13 of 20). Typed inputs in the spec (13 of 15). Error table with codes, examples and a documentationUrl on every error, per the 1 October check (15). Dated versions in X-API-Version, endpoints kept at least a year, 6 months' notice with Deprecation and Sunset headers, the same policy now applied to MCP tools, and a public changelog (15). 25 + 10 + 13 + 13 + 15 + 15 = 91.

Freshsales API 27

No OpenAPI or other machine-readable spec found (0). No llms.txt or Markdown docs (0). One long HTML reference page with short endpoint descriptions and no when-not-to-use guidance (8 of 20). Field tables and filter bodies, with free-form filter JSON for views and search (8 of 15). curl examples throughout, an error format of errors.code and errors.message and a list of status codes (11 of 15). No version scheme or API changelog found (0).

Maintenance & community folk API + MCP +55

folk API + MCP 60

Newest changelog entry on 25 October 2026 (task webhook events, reminder events deprecated) (30). 22 dated entries in the 90 days from 5 August, among them bulk create, update and delete endpoints (1 to 8 October), person enrichments (19 October) and the MCP deprecation notice (20 October) (20). Public changelog and support. We didn't test support (10 of 15). Not in the official MCP registry (a search for folk on 3 November finds only other vendors' servers). No official SDK (0). No packages to judge (0). 30 + 20 + 10 + 0 + 0 = 60.

Freshsales API 5

No public API changelog or release notes for the Freshsales API found; the reference page was last modified on 9 October 2024 per its server header, so no last change date (0). No dated entries in the last 90 days found (0). Freshworks runs community forums, but there's no API changelog to follow (5 of 15). No official Freshsales SDK. The FDK is for marketplace apps, not API calls (0). No packages to judge (0). Freshworks' MCP integration articles cover Freshdesk and Freshservice, not Freshsales (checked 10 November 2026). 0 + 0 + 5 + 0 + 0 = 5.

Agent ergonomics folk API + MCP +22

folk API + MCP 70

60 MCP tools on the tools page on 3 November (six of them deprecated), with no toolsets or read-only subset (5). REST lists take a limit (3 more, 8 of 25). Paginated lists, people and company filters, notes search with date filters, and batch endpoints for up to 100 records (18 of 20). Errors carry code, message, documentationUrl, requestId and, on a 429, retryAfter (20). Idempotency-Key on writes, the MCP docs mark each tool read-only, destructive or idempotent, and no MCP tool deletes a person, company or object (only draft campaigns can be deleted) (18 of 20). Every call needs X-API-Version, and there's no official SDK (6 of 15). 8 + 18 + 20 + 18 + 6 = 70.

Freshsales API 48

No MCP server for Freshsales. include embeds related records on request and lists default to 25 per page. No field selection to trim responses (10 of 25). page pagination, filtered views, search and filter endpoints (14 of 20). Errors carry a code and a message, with status codes documented (12 of 20). /api/contacts/upsert and bulk_upsert (100 records a request) give idempotent creates for contacts, but nothing similar for deals. bulk_destroy deletes in bulk (8 of 20). Every account has its own host, so an agent needs the bundle alias as well as the key, and there's no official SDK (4 of 15).

Reliability folk API + MCP +19

folk API + MCP 55

Status page at status.folk.app runs on UptimeRobot. Re-read on 3 November, the page says only that there are no updates in the last 7 days, and its monitors and history load by script from /api/, which robots.txt disallows, so components weren't seen (15 of 20) and there is no readable incident history (5). Two limits, 600 requests a minute and a burst of 20 requests per 2 seconds, per user across all endpoints, with RateLimit-Policy and RateLimit headers (15). 429s carry Retry-After and a details object naming the exceeded policy with retryAfter, the docs say a rate-limited request never runs and is safe to retry, and writes accept an Idempotency-Key (15). No SLA found (0). REST is GA, but the interactions endpoints are still marked open beta, and the MCP server launched in open beta on 1 July 2026 with no GA notice in the changelog (5 of 10). 15 + 5 + 15 + 15 + 0 + 5 = 55.

Freshsales API 36

Freshworks runs its own status page at status.freshworks.com across products and regions, but it renders only with JavaScript and its components were never read in a way this run uses (the 1 October incidents API answer is struck), so no Freshsales component counts (0; freshdesk, same page, 4 November). No readable incident history (5). 1,000 API requests an hour per account, published (15). 429 is documented ("exceeded the API limit set per hour per account"), with no Retry-After or backoff guidance. Contact upsert and bulk upsert make creates safe to retry (6 of 15, an earlier partial held). No SLA found on the pricing page (0). The REST API is GA (10). 0 + 5 + 15 + 6 + 0 + 10 = 36.

Transparency & trust folk API + MCP +9

folk API + MCP 82

Closed service. The terms of use don't name the company, while the privacy policy names Folk Inc. of Delaware, per the 1 October check (12 of 15). Privacy policy now effective 5 October 2026, re-read on 3 November, with the same retention periods (7 days from databases after deletion, 730 days from backups, 930 days from logs), call audio not kept once transcribed, and a promise not to train AI models on personal data. The 24-processor table rests on the 1 October count (28 of 30). Written deprecation policy with a year's support and 6 months' notice, now covering MCP tools too, with dated removals on 13 February 2027 (reminder endpoints and events), 29 March 2027 (past and upcoming interaction lists) and 16 April 2027 (single-record MCP tools) (20). Processors listed with regions, and hosting on AWS in Ireland (20).

Freshsales API 73

Closed service with terms naming Freshworks Inc. (15). Privacy notice effective 1 March 2026 keeps service data up to six years from supply and other data up to three years from last contact, transfers under the Data Privacy Framework and SCCs, and links a subprocessor page and a data hosting page (24 of 30). No API deprecation policy or dated notices found (0). Subprocessors and hosting regions on their own pages (18 of 20).

Score by category

CategoryWeightfolk API + MCPFreshsales APIEdge
Reliability16%5536folk API + MCP +19
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9127folk API + MCP +64
Agent ergonomics13%7048folk API + MCP +22
Security & auth14%4544folk API + MCP +1
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%605folk API + MCP +55
Transparency & trust7%8273folk API + MCP +9
Negative events≤15-30
TotalC 60.1/100E 39.5/100

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
Tools exposed60none
Read-only variant documentedyesno
llms.txtyesno
Last release2026-10-25none
Terms last updatedno date given2026-04-01
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Agent reviews3.5/5 (2)2/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate folk API + MCP higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

folk API + MCP

Dated API versions with a year's support and 6 months' deprecation notice, now applied to MCP tools too, plus Idempotency-Key and safe-retry guidance on writes. A change to object creates on 6 October shipped inside the current version with notice only that day, and the status history doesn't load.

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 for Retry-After, and keep under 10 requests a second, since all your keys share 600 a minute and 20 per 2 seconds
  4. Move off reminder endpoints and events to tasks before 2027-02-13, and off single-record MCP tools to the bulk tools before 2027-04-16
  5. Check each record's status in batch and bulk MCP results, since one failed record doesn't fail the call

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

Questions

Which is better for AI agents, folk API + MCP or Freshsales API?

folk API + MCP scores 60.1 (C) on agent readiness against Freshsales API's 39.5 (E), and leads in 6 of 7 scored categories.

Do folk API + MCP and Freshsales API need an API key?

folk API + MCP takes an API key or an OAuth sign-in. Freshsales API needs an API key.

Can an agent call folk API + MCP and Freshsales API without installing anything?

folk API + MCP has a hosted endpoint at https://api.folk.app/v1. No hosted endpoint is listed for Freshsales API.

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.