Salesforce publishes 294 APIs on the network and scores 80.1 — an exemplar band, and one of the highest composites of any provider its size.
What is unusual is not the number. It is the shape.
No weak facet
| Facet | Score |
|---|---|
| Contract quality | 84.1 |
| Governance | 80.2 |
| Discoverability | 77.8 |
| Operational transparency | 78.9 |
| Commercial clarity | 78.9 |
| Developer ergonomics | 78.3 |
Six facets inside a six-point band. Most high scorers in the catalog are spiky — a great contract with no governance story, or excellent operational transparency propping up thin specs. Microsoft Graph, profiled yesterday, runs from 47.9 to 84.2 across the same six.
Salesforce has no soft spot. For a surface that accreted across two decades and several acquisitions, that is a governance achievement more than a documentation one.
What is in the surface
The catalog holds 256 contracts, 100% of them callable as published, plus a genuinely multi-protocol artifact set:
- REST, SOAP and Bulk OpenAPI specifications
- Three AsyncAPIs — Change Data Capture, Platform Events, and the Bayeux/CometD Streaming API
- A GraphQL schema
- A first-party MCP server (provenance:
first-party, not derived — Salesforce publishes it, we did not infer it) - Arazzo workflows covering the full Bulk API 2.0 lifecycles
Publishing SOAP alongside REST in 2026 is not embarrassing here; it is honest. The SOAP API is still load-bearing for a large installed base, and describing it beats pretending it retired.
The Arazzo workflows are the interesting artifact
Bulk API 2.0 is a multi-step protocol: create an ingest job, upload a CSV, close the job, poll until JobComplete, download the results. Get the order wrong and you get a job stuck in a state you have to clean up by hand.
Salesforce publishes that sequence as machine-readable Arazzo — insert, upsert, delete and query lifecycles, plus business chains like create an Account then a Contact that belongs to it, and create a Lead with its follow-up Task and Campaign Member records.
This is the artifact type almost nobody ships, and it is precisely what an agent needs. An OpenAPI spec tells an agent that eight operations exist. An Arazzo workflow tells it which four to call, in what order, and when to stop polling.
Agent readiness: 59.9
The highest agent-readiness score in this week’s profiles, and it is earned honestly: spec presence, verified error semantics, verified OpenAPI examples, documented rate-limit signalling, an MCP server, and a .well-known catalog.
Still absent: idempotency signalling, Agent Skills, consent identity, an agent card, and dry-run mode. 389 agentic operations, 172 acting, 5 human-in-the-loop.
Five consent gates against 172 ways to change a CRM record is thin — though against Microsoft Graph’s 93-out-of-17,655, it is an order of magnitude better per acting operation.
Takeaway
294 APIs, 100% callable, six facets inside six points, three AsyncAPIs, a first-party MCP server, and Arazzo workflows for the protocols that are genuinely hard to sequence. Salesforce is what it looks like when a twenty-year-old surface gets governed rather than merely documented.
See the full profile at apis.io/providers/salesforce/.