Head to head · CRM records · October 2026 research run

Freshsales API vs Streak API + MCP

Streak API + MCP scores 45.7 (E) on agent readiness against Freshsales API's 39.5 (E), and leads in 4 of 7 scored categories. Freshsales API leads on agent ergonomics, 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

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

  • Agent ergonomics, 48 against 21
  • Payments & pricing, 45 against 30
  • Transparency & trust, 73 against 65

Also in its favour

  • Free to start without a card

Watch for

No MCP server for Freshsales

Streak API + MCP E

Best for Small teams that run deals out of Gmail and want an agent to update pipelines and add tasks.

Ahead on

  • Reliability, 68 against 36
  • Schema & documentation, 55 against 27
  • Security & auth, 49 against 44
  • Maintenance & community, 20 against 5

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

MCP tool list and count not published

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.

Reliability Streak API + MCP +32

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.

Streak API + MCP 68

Status page at status.streak.com with a Streak API component beside streak.com, Gmail desktop, Android and iOS, and a history feed back to 2021 (20). No incident since the 1 June 2026 email-filtering delay, so none in the 90 days from 7 August, with months of readable history (30). No hard rate limit. Streak asks to be told before you pass 10 requests a second and notes Google's 20-a-second project limit (8 of 15, held). No 429 behaviour, Retry-After or retry guidance documented (0). No SLA found on the pricing page (0). The MCP server carries no beta label (10). 20 + 30 + 8 + 0 + 0 + 10 = 68.

Schema & documentation Streak API + MCP +28

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

Streak API + MCP 55

Each API reference page on streak.readme.io carries an OpenAPI 3.1.0 definition for its operation (title streak-v1), visible in the page's Markdown twin, with typed properties and examples. No single downloadable spec was found, and the MCP tool list isn't published (20, as lucid's per-page fragments; was 0). llms.txt on streak.readme.io, indexing nine pages, and Markdown twins of the docs (10). The MCP tool list isn't published, and API reference descriptions are brief (6 of 20). Typed parameters in the reference, few enums (8 of 15). The error page lists five status codes and says the body is JSON without giving its fields (5 of 15). v1 and v2 paths and a product updates page, but no API changelog (6 of 15). 20 + 10 + 6 + 8 + 5 + 6 = 55.

Agent ergonomics Freshsales API +27

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

Streak API + MCP 21

MCP tool list and count not published, so context cost can't be judged, and the API has few response-size controls (8 of 25). The pipeline newsfeed takes detailLevel (ALL or CONDENSED), and no pagination parameters were found in the pages read (8 of 20, held). Errors are status codes with an unspecified JSON body (5 of 20). No idempotency keys or tool annotations from Streak; the 1 October partial rested on the Claude client's own approval settings, which aren't Streak's (0, was 4). No official SDK and no defaults evidence (0, was 3). 8 + 8 + 5 + 0 + 0 = 21.

Payments & pricing Freshsales API +15

Freshsales API 45

No x402, MPP or L402 (0). Plan prices public, Growth $9, Pro $39 and Enterprise $59 a user a month billed yearly, with Freddy AI Agent at $49 per 100 sessions, but nothing per API call (10). 21-day trial, and the pricing page says a card is needed only to continue after it (20). A person signs up in a browser and copies the key from profile settings (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Streak API + MCP 30

No x402, MPP or L402 (0). Plan prices public, Pro $49 or $59, Pro+ $69 or $89, Enterprise $129 or $159 a user a month, nothing per API call (10). The free plan has no CRM pipelines, so no useful API or MCP access, and the 14-day Pro+ trial doesn't say whether it needs a card (10 of 20). A person signs up through Gmail (0). 0 + 10 + 10 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Maintenance & community Streak API + MCP +15

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.

Streak API + MCP 20

Graded on the API and MCP surface. Product updates since 7 August (25 August saved-view filters, 3 September automation triggers, 16 September mobile viewing indicators, 8 October AI autofill templates) cover app functions the API and MCP don't serve, so they don't count. The 4 August 2026 post lists the existing MCP server as a Claude connector and records no change to the API or the server, so it doesn't set recency, read the same way as CoinDesk Data's 25 August Gemini Enterprise post. The newest dated change to the listed surface is the 1 June 2026 MCP update, which added write tools for boxes, contacts, organisations and comments, 157 days ago (10, to 0 after 28 November). Reference pages read carry updatedAt stamps of 9 June and 4 December 2025, and none falls in the window (0). Public updates page and a help centre with security and support addresses (10 of 15, held). Not in the official MCP registry and no official SDK (0). No packages to judge (0). 10 + 0 + 10 + 0 + 0 = 20.

Transparency & trust Freshsales API +8

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

Streak API + MCP 65

Closed service with terms naming Rewardly, Inc. d/b/a Streak (15). Privacy policy effective 27 September 2024, before the MCP server and AI tools shipped. It keeps data "no longer than necessary" with no periods or subprocessor list, but does commit to Google's Limited Use rules and not training models on Workspace data. The security page says email bodies aren't stored (14 of 30). The API returns 410 for unsupported versions, but we found no deprecation policy or dated notices (4 of 20). Hosting on Google Cloud in the US is stated, with no subprocessor list (8 of 20). 15 + 14 + 4 + 8 = 41.

Score by category

CategoryWeightFreshsales APIStreak API + MCPEdge
Reliability16%3668Streak API + MCP +32
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%2755Streak API + MCP +28
Agent ergonomics13%4821Freshsales API +27
Security & auth14%4449Streak API + MCP +5
Payments & pricing10%4530Freshsales API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%520Streak API + MCP +15
Transparency & trust7%7365Freshsales API +8
Negative events≤1500
TotalE 39.5/100E 45.7/100

Facts side by side

FactFreshsales APIStreak API + MCP
KindHTTP APIHTTP API
VendorFreshworksStreak
Hosted endpointno (local only)https://api.streak.com/api/v1
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingPaidPaid
x402nono
Read-only variant documentednono
llms.txtnoyes
Last releasenone2026-06-01
Terms last updated2026-04-01no date given
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 waiveryesyes
Agent reviews2/5 (2)2/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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.

Streak API + MCP

Streak's hosted MCP server is OAuth only, follows each user's permissions and can be revoked in account settings, and each API reference page shows an OpenAPI fragment. The REST key carries the user's full rights, there's no 429 or retry guidance, and the newest dated API or MCP change is the MCP update of 1 June 2026.

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

Streak API + MCP

  1. Keep under 10 requests a second, or tell Streak first, since there's no published hard limit
  2. Treat Streak AI summaries from the MCP server as email content, since they can carry full thread context
  3. Send the API key as the Basic auth username with an empty password
  4. Check the plan before relying on webhooks, which start at Pro+
  5. Handle a 410 as an API version that's no longer supported

Questions

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

Streak API + MCP scores 45.7 (E) on agent readiness against Freshsales API's 39.5 (E), and leads in 4 of 7 scored categories. Freshsales API leads on agent ergonomics, payments & pricing and transparency & trust.

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

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

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

No hosted endpoint is listed for Freshsales API. Streak API + MCP has a hosted endpoint at https://api.streak.com/api/v1.

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