Head to head · CRM records · October 2026 research run

Freshsales API vs Salesforce API + MCP

Freshsales API scores 39.5 (E) on agent readiness against Salesforce API + MCP's 27.8 (F), and leads in 5 of 7 scored categories. Salesforce API + MCP leads on reliability. Both do crm records.

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

Which one, for what

Freshsales API E

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

Ahead on

  • Schema & documentation, 27 against 0
  • Agent ergonomics, 48 against 0
  • Transparency & trust, 73 against 67

Also in its favour

  • Free to start without a card

Watch for

No MCP server for Freshsales

Salesforce API + MCP F

Best for Organisations already on Salesforce that need an agent to read and update records under existing access rules.

Ahead on

  • Reliability, 45 against 36

Also in its favour

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

Watch for

API access needs the $25 add-on on Pro Suite or a Core seat at $195, and Free and Starter suites have none

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.

Agent ergonomics Freshsales API +48

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).

Salesforce API + MCP 0

developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The tool count, query limits, error format, the Reads, Mutations and Deletes split, the recycle bin and the setup steps were all read there and can't be re-read. No official general-purpose REST SDK was found on a readable host. Every line is unread and scored as absent. 0 + 0 + 0 + 0 + 0 = 0.

Schema & documentation Freshsales API +27

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).

Salesforce API + MCP 0

developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The hosted MCP references, the API reference, llms.txt and the platform versioning notes were all read there. The release notes on help.salesforce.com load only by script, www.salesforce.com/llms.txt lists marketing pages only, and no public OpenAPI or MCP tool definitions were found on a readable host. Contract, llms.txt, descriptions, typed inputs, examples and versioning are unread and scored as absent. 0 + 0 + 0 + 0 + 0 + 0 = 0.

Reliability Salesforce API + MCP +9

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.

Salesforce API + MCP 45

status.salesforce.com is a status site drawn by script, and trust.salesforce.com, read on 4 November, shows current status by product (Sales and Service "Available"). The status-page line is kept on that and the 1 October reading (20). The 1 October incident count came from api.status.salesforce.com, the status site's data API, which this run doesn't read, so it is struck; no incident history could be read on 4 November (5). developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The API allocations, REQUEST_LIMIT_EXCEEDED and Sforce-Limit-Info were published there and weren't found on a readable page (0 and 0). Salesforce's security model page says "99.9%+ uptime SLAs" with no SLA document found, read as listings that give a stated uptime figure 10 (10). The pricing page sells the Web Services API with each edition, so the REST surface is generally available; the hosted MCP GA reading is struck with the docs (10). 20 + 5 + 0 + 0 + 10 + 10 = 45.

Transparency & trust Freshsales API +6

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).

Salesforce API + MCP 67

Closed service with terms naming Salesforce, Inc. (15). Privacy statement effective 19 May 2026, re-read on 4 November, with a DPA, Binding Corporate Rules, the Data Privacy Framework and SCCs linked; retention reads "consistent with the original purpose of collection", and it says Salesforce "may use artificial intelligence to process your Personal Data, including to develop and deploy AI systems" (20 of 30). The beta-to-GA notes and the API version retirement notices were on the blocked developer host or on script-drawn help pages, so no dated deprecation notice could be read (0). Subprocessors and infrastructure are covered in linked trust and compliance documents we didn't read, and the security model page names Hyperforce data residency controls (12 of 20). 15 + 20 + 0 + 12 = 47.

Score by category

CategoryWeightFreshsales APISalesforce API + MCPEdge
Reliability16%3645Salesforce API + MCP +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%270Freshsales API +27
Agent ergonomics13%480Freshsales API +48
Security & auth14%4440Freshsales API +4
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%54Freshsales API +1
Transparency & trust7%7367Freshsales API +6
Negative events≤1500
TotalE 39.5/100F 27.8/100

Facts side by side

FactFreshsales APISalesforce API + MCP
KindHTTP APIHTTP API
VendorFreshworksSalesforce
Hosted endpointno (local only)https://api.salesforce.com/platform/mcp/v1/platform/sobject-all
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth
PricingPaidPaid
x402nono
Tools exposednone11
Read-only variant documentednoyes
llms.txtnoyes
Terms last updated2026-04-012025-04-08
Privacy policy last updatedno date givenno date given
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Agent reviews2/5 (2)4/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Salesforce API + MCP higher, the other way from the total score.

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

Freshsales API

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

Salesforce API + MCP

Salesforce's REST API and hosted MCP servers reach Sales Cloud records under each user's object, field and record access. API access starts at Pro Suite plus a $25 add-on or Core at $195 a user a month. Salesforce's developer documentation answered our crawler with a 403 on 4 November 2026, so its contract, limits and auth model are unverified here.

Before you call either

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

Salesforce API + MCP

  1. Ask the admin for a permission set limited to the objects and fields the job needs, since calls run with the user's object, field and record access
  2. Confirm the org's edition includes the Web Services API (Core and above, or Pro Suite with the $25 add-on) before building on it
  3. Check trust.salesforce.com for the product's status before retrying calls that fail across the board
  4. Test writes in a trial or sandbox org rather than production

Questions

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

Freshsales API scores 39.5 (E) on agent readiness against Salesforce API + MCP's 27.8 (F), and leads in 5 of 7 scored categories. Salesforce API + MCP leads on reliability.

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

Freshsales API needs an API key. Salesforce API + MCP uses an OAuth sign-in.

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

No hosted endpoint is listed for Freshsales API. Salesforce API + MCP has a hosted endpoint at https://api.salesforce.com/platform/mcp/v1/platform/sobject-all.

Other comparisons with Freshsales API or Salesforce 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.