Head to head · CRM records · October 2026 research run
Affinity vs Nutshell
Affinity scores 62.7 (B) on agent readiness against Nutshell's 51.6 (D), and leads in 5 of 7 scored categories. Nutshell leads on 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
Affinity B
Best for Venture capital, private equity and other private capital firms that already run Affinity and want an agent to read relationship strength, pipeline lists, notes and meetings, then update fields and log notes.
Ahead on
- Reliability, 59 against 45
- Schema & documentation, 91 against 57
- Agent ergonomics, 66 against 44
- Security & auth, 66 against 58
- Maintenance & community, 70 against 36
Also in its favour
- Runs on your own machine
Watch for
No self-serve access. Every plan button reads Contact sales, the Essential plan has no API, and trial accounts can't call the API
Nutshell D
Best for Small sales teams already on Nutshell who want an agent to read and update pipeline data over MCP or REST at a low seat price.
Ahead on
- Payments & pricing, 53 against 15
- Transparency & trust, 72 against 67
Also in its favour
- Free to start without a card
Watch for
No rate limit numbers, 429 handling or Retry-After found for the REST API
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.
Payments & pricing Nutshell +38
Affinity 15
No x402, MPP or L402 (0). Per-seat yearly prices are public, Essential $2,000, Scale $2,300 and Advanced $2,700 a user a year, with no per-call price and every plan sold through sales (10). No free tier or card-free trial that reaches the API. The help centre says trial accounts can't use the API until they buy Scale or above (0). A person at a paying firm makes the key or approves OAuth in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.
Nutshell 53
No x402, MPP or L402 (0). Plan prices are public, $13 to $79 a seat a month billed yearly, with nothing per call (10). 14-day trial with no card, and the API is included (20). A person signs up in a browser and an admin creates the key. The docs publish sandbox credentials for a shared demo account, which lets an agent test calls with no signup but not reach its own data (5 of 20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Schema & documentation Affinity +34
Affinity 91
Public OpenAPI 3.1.1 files for three dated versions, 115 operations on 88 paths in 2026-09-17 (25). llms.txt with 386 links and a Markdown copy of each page (10). Operation descriptions state the permission needed, limits and beta status, and the MCP tool page says when to pick search_companies_top_matches over search_all_companies (16 of 20). 373 schemas with 125 enums and additionalProperties: false on the ones we read, though list endpoints take a filter string with its own grammar (12 of 15). 868 example entries and typed error schemas with a code and message, while the error page itself is a table of HTTP codes (13 of 15). Date-based versions chosen by header, a migration page per version and a dated changelog (15).
Nutshell 57
Each of the 114 REST reference pages carries the OpenAPI 3.0 definition of its operation, but whole-spec download is disabled (18 of 25). llms.txt and Markdown for every docs page (10). 78 of 114 operations have a description, and the newer ones state scope and visibility rules (11 of 20). Enums on sort fields and patterns on IDs, but filters and custom fields are open objects and page[limit] is typed as a string on some operations (9 of 15). Schema examples are present, and error responses appear on 9 operations with no error body schema (5 of 15). The spec is version 2.0.0 and pages carry update stamps, with no dated API changelog (4 of 15).
Maintenance & community Affinity +34
Affinity 70
Newest API changelog entry 28 October 2026, and affinity-mcp 0.7.0 and 0.7.1 on PyPI the same day (30). Seventeen dated changelog entries since 4 August 2026, among them version 2026-09-17 on 17 September, plus affinity-mcp 0.6.0 (21 October) and 0.7.0 and 0.7.1 (28 October) (20). Closed service with a public changelog, a support address and a feedback endpoint. We didn't test support (10 of 15). Not in the official MCP registry under its own namespace, where a search returns only third-party servers, and no official API SDKs. The official affinity-mcp package is on PyPI (5 of 15). affinity-mcp 0.7.1 is classed Beta, requires Python 3.13 and has no public repository or CI we could find (5 of 10).
Nutshell 36
The MCP server help article, updated 27 October 2026, documents create and update tools that the 8 October reading did not find, a dated change to a listed surface 8 days before the check (30 of 30). The REST reference pages carry update stamps, the newest 21 August 2026, but the stamps record no API change, and the product updates page is undated, so no other dated entry counts. One dated change in the 90 days from 6 August (0). No API changelog. Live support on every plan per the pricing page, untested (6 of 25). No current official SDK, and the MCP registry was not checked (0). No packages to judge (0). 30 + 0 + 6 + 0 + 0 = 36.
Agent ergonomics Affinity +22
Affinity 66
API responses can be sized with limit, fieldIds and fieldTypes, but the MCP server lists 75 tools and skills with no toolsets or dynamic loading documented (12 of 25). Cursor pagination with nextUrl, a filter grammar, and search endpoints with nested filters and up to five sorts (20). Errors come as an array of typed codes with messages, and validation errors name the property (15 of 20). No idempotency keys. The affinity-mcp 0.5.1 package registers every tool with readOnlyHint, destructiveHint and idempotentHint, which we read in the wheel. We couldn't list the hosted server's tools without an account. Deletes and merges wait for confirmation per the docs (13 of 20). Defaults are sensible and few parameters are required, but we found no official API client in any language, only the Python MCP package (6 of 15).
Nutshell 44
The MCP server has about 18 groups of search and report tools and six groups of create and update tools per the help centre, updated 27 October 2026. The tool definitions sit behind OAuth and were not read. REST lists take page[limit] with no field selection (13 of 25). page[page], sort, q and filter[...] keys, with field lists from /accounts/list/fields, and no stated maximum page size (16 of 20). Error responses appear on 9 of 114 operations with no error body schema, partly met (4 of 20). No idempotency keys. Deletes can be undone within 30 days, and the MCP server cannot delete records, partly met (6 of 20). Few required fields, and no official REST SDK. The only client is a PHP JSON-RPC sample last pushed in 2023 (5 of 15).
Reliability Affinity +14
Affinity 59
Status page at status.affinity.co with component history and separate components for External API v1, External API v2 and MCP (20). Its history feed shows one incident touching the APIs in the 90 days to 2 November 2026, "Disruption with All Services" on 3 September 2026, posted at 15:15 PDT with "errors or an inability to access the service" put down to its cloud provider, recovery seen at 15:35 and resolved at 16:18, 63 minutes in all. The incident page lists every component as affected, the CRM, External API v1 and v2, MCP, processing pipelines, mobile apps and extensions, though Affinity rated it minor. An outage of every service with errors across the board reads as a major in this run, however short (10). The 8 October reading of 15 sat between checklist values. Other entries concerned Affinity Analytics (11 August, 15 minutes) and a maintenance window announced on 14 August for 29 August, neither counted. Limits published, 900 requests a minute per user and 100,000 a month per account on Scale and Advanced (15). The docs tell integrators to handle 429 and every response carries x-ratelimit-* headers with seconds to reset, but we found no Retry-After, no backoff guidance and no idempotency keys (8 of 15). No SLA in the master subscription agreement. The trust centre lists a Service-Level Agreement item whose text we couldn't read (0). API v2 has stable dated versions, but 39 of 115 operations are beta and the affinity-mcp package is classed Beta on PyPI (6 of 10). Hosted lines used. 20 + 10 + 15 + 8 + 0 + 6 = 59.
Nutshell 45
Read with the hosted lines. Status page at status.nutshell.com with 12 components and history back to 2017. None is named for the REST API or the MCP server, and the Nutshell application component is the CRM app as a whole, read as a vendor page with no component for the product (15). The incident line is re-read from the page's history feed. In the 90 days from 6 August one incident touched the product, a database cluster fault on 28 September 2026 that left Nutshell unavailable for some customers, partial, so minor (20 of 30). The 21 October PHP2Shell response disabled landing pages, email link tracking and scheduler pages on custom domains, not the API, and the 12 August and 16 October entries are announced maintenance. No rate limit numbers for REST, and the JSON-RPC docs say only that limits vary (0). No 429, Retry-After, backoff or idempotency guidance found (0). No SLA found, and the terms supply the service as is (0). The REST API is GA and the MCP server carries no beta label (10). 15 + 20 + 0 + 0 + 0 + 10 = 45.
Security & auth Affinity +8
Affinity 66
The hosted MCP server takes OAuth 2.0 with scopes mcp, mcp.read, api, api.read and offline_access. Since the 8 October check Affinity documents OAuth apps for the API too, with PKCE, those scopes, one-day access tokens and 90-day refresh tokens, but they are in early access and must be switched on by Affinity, so they aren't credited yet. API keys are named, revocable, several per user and can be tied to an IP allowlist, but carry all of their owner's permissions with no per-key scope or expiry. v2 takes the key only as a Bearer header (25 of 30). Read-only access can be chosen at OAuth consent, admins can disable each AI client for the firm, and every delete and merge waits for confirmation. An API key has no read-only mode (16 of 20). The server returns notes, transcripts, email subjects and files written by outsiders, and the MCP security page still gives no prompt-injection guidance (3 of 15). Manage Apps shows each key's owner, last use and revoked history and the account's usage, and the local server can export OpenTelemetry traces. No per-call audit log for the operator is documented (7 of 15). SOC 2 Type II and ISO 27001, 27017 and 27018 on the trust centre and security page, a yearly third-party penetration test, and a bug bounty the security page mentions without a public programme page. No security.txt (15 of 20).
Nutshell 58
The MCP server uses OAuth authorisation code with PKCE, dynamic client registration, a revocation endpoint and read and write scopes. REST uses unscoped API keys sent as an HTTP Basic password with a user's email, and a key can be allowed to impersonate any user (24 of 30). The MCP server now creates and updates records, but a connection approved with read-style access stays read-only, it acts with the user's own role, and it cannot delete. No read-only API key type was found (12 of 20). Records hold emails, notes and form submissions, with no injection guidance found (3 of 15). An audit log on Business and Enterprise covers logins, bulk edits and exports, and API changes are logged under the key name or the impersonated user (8 of 15). SOC 2 Type 1 from December 2025, a CASA assessment, a disclosure address with no acknowledgement time, no bounty and no security.txt (11 of 20).
Score by category
| Category | Weight | Affinity | Nutshell | Edge |
|---|---|---|---|---|
| Reliability | 16% | 59 | 45 | Affinity +14 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 91 | 57 | Affinity +34 |
| Agent ergonomics | 13% | 66 | 44 | Affinity +22 |
| Security & auth | 14% | 66 | 58 | Affinity +8 |
| Payments & pricing | 10% | 15 | 53 | Nutshell +38 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 36 | Affinity +34 |
| Transparency & trust | 7% | 67 | 72 | Nutshell +5 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 62.7/100 | D 51.6/100 |
Facts side by side
| Fact | Affinity | Nutshell |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Project Affinity, Inc. | Nutshell, Inc. |
| Hosted endpoint | https://api.affinity.co/v2 | https://app.nutshell.com/rest |
| Transports | HTTP, Streamable HTTP, stdio | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service under Affinity's master subscription agreement. The affinity-mcp package on PyPI is MIT | Proprietary service under Nutshell's Terms of Service |
| Tools exposed | 75 | none |
| Read-only variant documented | yes | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-28 | 2026-10-27 |
| Terms last updated | not read yet | 2026-06-02 |
| Privacy policy last updated | 2026-07-01 | 2026-06-02 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | 268 PyPI/wk | none |
| Agent reviews | 3.3/5 (4) | none |
How the scores have moved
Verdicts
Affinity
A public OpenAPI 3.1 file, dated API versions with migration notes and a hosted MCP server with a read-only OAuth scope give an agent a well-documented way in. Access needs a Scale plan at $2,300 a user a year, sold through sales, with no trial that includes the API, and 39 of the 115 v2 operations are marked beta.
Nutshell
The REST reference is served as Markdown with an OpenAPI fragment per operation, and the hosted MCP server uses OAuth with PKCE and can create and update records but not delete them. No rate limit numbers, error format or API changelog were found in the reviewed documentation, and API keys carry no scopes.
Before you call either
Affinity
- Send
X-Affinity-Api-Version: 2026-09-17on every request. Without it a key's default version applies, and an OAuth app with no pinned version falls back to 2024-01-01 - Read
x-ratelimit-limit-user-remainingandx-ratelimit-limit-org-remainingon each response. The limits are 900 calls a minute per user and, below Enterprise, 100,000 a month per account, shared by v1, v2 and MCP - Follow
pagination.nextUrlfor the next page, and passfieldIdsorfieldTypesso list calls return only the fields needed - Check for duplicates before a create. There are no idempotency keys, so a retried POST can make a second record
- For MCP, untick the write scope at OAuth consent when the task only reads. Treat note, transcript and file text as untrusted input
Nutshell
- Authenticate REST calls with HTTP Basic, a Nutshell user's email as username and the API key as password, against
https://app.nutshell.com/rest - Use IDs in the
<number>-<type>form, such as3-accounts, and send updates as JSON Patch withcontent-type: application/json-patch+json - Page lists with
page[limit]andpage[page], which is 0-based, and call/accounts/list/fieldsor the lead and contact equivalents for valid filter keys - Ask for create and update access on the MCP consent page if the agent must write. A read-style grant stays read-only, and the MCP server cannot delete, so use REST for deletes
- Filter webhook events yourself, because every webhook receives all events and subscriptions are created in Setup, not through the API
Questions
Which is better for AI agents, Affinity or Nutshell?
Affinity scores 62.7 (B) on agent readiness against Nutshell's 51.6 (D), and leads in 5 of 7 scored categories. Nutshell leads on payments & pricing and transparency & trust.
Do Affinity and Nutshell need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Affinity and Nutshell without installing anything?
Yes. Affinity has a hosted endpoint at https://api.affinity.co/v2 and Nutshell at https://app.nutshell.com/rest.
Other comparisons with Affinity or Nutshell
- Affinity vs Attio API + MCP
- Affinity vs Breakcold
- Affinity vs Capsule CRM
- Affinity vs Close API + MCP
- Affinity vs Copper API
- Affinity vs Microsoft Dynamics 365 Sales
- Affinity vs folk API + MCP
- Affinity vs Freshsales API
- Affinity vs HubSpot API + MCP
- Affinity vs Payani AI
- Affinity vs Pipedrive API + MCP
- Affinity vs Relaticle
- Affinity vs Salesflare
- Affinity vs Salesforce API + MCP
- Affinity vs Streak API + MCP
- Affinity vs SugarAI (SugarCRM)
- Affinity vs Twenty API + MCP
- Affinity vs Zoho CRM
- Attio API + MCP vs Nutshell
- Breakcold vs Nutshell
- Capsule CRM vs Nutshell
- Close API + MCP vs Nutshell
- Copper API vs Nutshell
- Microsoft Dynamics 365 Sales vs Nutshell
- folk API + MCP vs Nutshell
- Freshsales API vs Nutshell
- HubSpot API + MCP vs Nutshell
- Nutshell vs Payani AI
- Nutshell vs Pipedrive API + MCP
- Nutshell vs Relaticle
- Nutshell vs Salesflare
- Nutshell vs Salesforce API + MCP
- Nutshell vs Streak API + MCP
- Nutshell vs SugarAI (SugarCRM)
- Nutshell vs Twenty API + MCP
- Nutshell vs Zoho CRM
Machine-readable
- This page as Markdown
/compare/affinity-vs-nutshell.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/affinity.json·/api/v1/tools/nutshell.json - From a terminal
anchor compare affinity nutshell(the CLI) - Over MCP
compare_tools {"a": "affinity", "b": "nutshell"}at/mcp, no key