Head to head · CRM records · October 2026 research run

Attio API + MCP vs Freshsales API

Attio API + MCP scores 62.8 (B) on agent readiness against Freshsales API's 39.5 (E), and leads in 5 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

Attio API + MCP B

Best for Small teams and startups that want an agent to search across records, notes, emails and calls and then update the CRM, starting free.

Ahead on

  • Reliability, 77 against 36
  • Schema & documentation, 82 against 27
  • Agent ergonomics, 62 against 48
  • Security & auth, 56 against 44
  • Maintenance & community, 63 against 5

Also in its favour

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

Watch for

48 MCP tools with no read-only mode or toolsets, including delete and merge tools

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

Maintenance & community Attio API + MCP +58

Attio API + MCP 63

REST changelog entries on 28 October (writable avatar_url and logo_url), 27 October, 15 October and 14 October 2026, and MCP entries on 14 October and 1 October (30). Seventeen dated entries (13 REST, 4 MCP) across the REST and MCP changelogs since 4 August 2026 (20). Closed service with public changelogs and a support address. We didn't test support (10 of 15). Not in the official MCP registry. A search for attio on 2 November returns only third-party servers (kesslerio, kaszek, Smithery). No official REST SDK (0). The only npm package is the App SDK CLI, version not re-read (3 of 10). 30 + 20 + 10 + 0 + 3 = 63.

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.

Schema & documentation Attio API + MCP +55

Attio API + MCP 82

Three public OpenAPI files (API, standard objects, webhooks) at api.attio.com/openapi, per the 1 October check (25). llms.txt now lists 399 links, with Markdown copies of every page (10). Each MCP tool gets a one-line purpose and example prompts in the docs. We couldn't read the hosted server's own tool definitions, so when-not-to-use guidance is unchecked (12 of 20). Typed parameters in the OpenAPI, but filters are a nested JSON object the agent has to build (11 of 15). Examples on reference pages and a documented error body with status_code, type, code and message (12 of 15). Dated public changelogs for the REST API, the MCP server and the App SDK, but no versioning or deprecation policy beyond the v2 path (12 of 15). 25 + 10 + 12 + 11 + 12 + 12 = 82.

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

Reliability Attio API + MCP +41

Attio API + MCP 77

status.attio.com moved to incident.io, with five components and data back to August 2020 (20). Its feed and 90-day bars show four incidents from 4 August to 2 November 2026, all partial. On 8 September, "Platform avaliblity issues", intermittent availability problems on Attio Cloud and the web client from 17:05 to monitoring at 17:24 UTC. On 28 September workflow execution and webhook delivery ran late for about 4 hours. On 6 October formula updates and on 12 October bulk record deletions were delayed on Background Tasks. Minor incidents only (20). Rate limits published, 100 reads and 25 writes a second, plus score-based limits on list queries in a 10-second window (15). 429s carry a Retry-After date and a JSON body, and the docs say rate-limited requests weren't processed and can be retried. Upsert (assert) endpoints give a safe retry for creates, but there's no idempotency key (12 of 15). No SLA found on the pricing page (0). REST v2 and the MCP server carry no beta label, though several newer endpoints do (10). 20 + 20 + 15 + 12 + 0 + 10 = 77.

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.

Agent ergonomics Attio API + MCP +14

Attio API + MCP 62

The MCP server now lists 48 tools, after delete-task on 1 October and six activity tools on 14 October 2026, with no toolsets, no read-only subset and no dynamic loading (5). Semantic search tools over notes, emails and call recordings save a few listing calls (3 more, 8 of 25). REST lists take limit, offset, filters and sorts, and comment threads paginate at 80 replies and 250 comments a page (20). Errors carry a machine code and a message, and 429s say when to retry (15 of 20). The docs say the server uses MCP safety annotations, with reads auto-approved and writes asking the user to confirm in the client, and REST has upsert endpoints. We didn't read the annotations on the tools themselves (12 of 20). No official REST SDK in any language. The npm package attio is the App SDK CLI, not an API client (7 of 15). 8 + 20 + 15 + 12 + 7 = 62.

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

Security & auth Attio API + MCP +12

Attio API + MCP 56

Workspace API keys and OAuth tokens share one set of per-endpoint scopes, a token revocation endpoint shipped on 11 September 2026, and since 15 October OAuth tokens can be user-level, limited to one member's data and permissions. The MCP server is OAuth only and works as the signed-in user. HTTP Basic is supported but discouraged, and we found no query-string token option (27 of 30). A read-scoped key gives least privilege on REST. The MCP server has no read-only mode, its writes rely on client confirmation, and it can delete comments and tasks and merge records. A REST endpoint added on 4 September 2026 deletes a whole custom object, which the changelog calls destructive and irreversible (13 of 20). The MCP server returns email bodies, call transcripts and notes written by outsiders, and we found no prompt-injection guidance (2 of 15). No audit-log documentation found in the API or MCP docs. Attribute history on records is the nearest thing (4 of 15). attio.com publishes a Vulnerability Disclosure Policy with safe harbour, a 72-hour confirmation and a 90-day disclosure window covering app, api, cdn and attio.com, which the 1 October check didn't record. The DPA promises yearly third-party penetration tests and breach notice within 72 hours. The Vanta-hosted trust centre wasn't read, so certifications are unchecked. No security.txt (404 on 2 November) and no bug bounty found. agentvfs scores 7 for a disclosure policy alone, and the DPA's testing and breach commitments add 3 (10 of 20, was 6). 27 + 13 + 2 + 4 + 10 = 56.

Freshsales API 44

One per-user API key in Authorization: Token token=<key>, limited by that user's role and visibility. No scopes, no OAuth for the CRM API, and we found no rotation docs (13 of 30). No read-only key. Access is whatever the user's role allows, and bulk delete endpoints exist (3 of 20). Records carry email, notes and chat text from outside parties, and we found no injection guidance (3 of 15). Audit logs listed on the Enterprise plan (8 of 15). HackerOne disclosure programme, a security.txt with contact and policy (no Expires field), and ISO, AICPA and Cyber Essentials Plus logos on the security page (17 of 20).

Score by category

CategoryWeightAttio API + MCPFreshsales APIEdge
Reliability16%7736Attio API + MCP +41
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8227Attio API + MCP +55
Agent ergonomics13%6248Attio API + MCP +14
Security & auth14%5644Attio API + MCP +12
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%635Attio API + MCP +58
Transparency & trust7%6973Freshsales API +4
Negative events≤15-30
TotalB 62.8/100E 39.5/100

Facts side by side

FactAttio API + MCPFreshsales API
KindHTTP APIHTTP API
VendorAttioFreshworks
Hosted endpointhttps://api.attio.com/v2no (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumPaid
x402nono
Tools exposed48none
Read-only variant documentednono
llms.txtyesno
Last release2026-10-28none
Terms last updated2025-11-012026-04-01
Privacy policy last updated2026-06-01no 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 benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity9.9k npm/wknone
Agent reviews3/5 (2)2/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Attio 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

Attio API + MCP

API, webhooks and the hosted MCP server are on the Free plan for 3 seats with no card, and REST keys and OAuth tokens take per-endpoint scopes. The 48 MCP tools have no read-only mode or toolsets and include delete and merge tools, and thread pagination changed on the day it was announced.

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

Attio API + MCP

  1. Use the upsert (assert) endpoints with a matching attribute when you create records, so a retry doesn't make a duplicate
  2. Wait until the Retry-After date on a 429, usually the next second
  3. Simplify filters and sorts if a list query fails its score-based limit
  4. Page through threads with cursor and limit. Get a thread returns at most 250 comments a request
  5. Ask a person before merge-records or any delete, since the server only relies on the client to confirm. Treat email and transcript text as untrusted input

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, Attio API + MCP or Freshsales API?

Attio API + MCP scores 62.8 (B) on agent readiness against Freshsales API's 39.5 (E), and leads in 5 of 7 scored categories.

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

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

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

Attio API + MCP has a hosted endpoint at https://api.attio.com/v2. No hosted endpoint is listed for Freshsales API.

Other comparisons with Attio 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.