◎ Discry Score
salesforce.com
crm · API
D
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 89 (B)
Discry your API →
CRM · RANK #9 OF 13

Salesforce is Poor to agents.

Discry independently scored how well an AI agent can discover and understand the Salesforce API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.

Discry your API — freeView the docs ↗

SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.

Discovery

45% of score · 17/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Partial
llms.txtAn llms.txt index that points agents to the docs that matter.Fail
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Fail
llms-full.txtA full-text bundle agents can load in one request.Fail
AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Fail
.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail
MCP registryThe API is listed in a public MCP registry.Pass
robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Fail
SitemapA sitemap so agents can enumerate the docs surface.Fail

Comprehension

55% of score · 69/100
Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Pass
Realistic examplesRunnable, real-world request/response examples.Pass
Multi-step workflowsDocs that chain calls into complete jobs an agent can follow.Pass
Error-recovery guidanceDocumented failure modes and how to recover from them.Partial
Answer-first formatThe answer leads; preamble does not bury it.Partial
Capability boundariesClear limits — what the API can and cannot do.Pass
Naming consistencyConsistent, predictable naming across endpoints.Pass
Heading hierarchyClean heading structure agents can navigate.Partial
Markdown docsDocs available as clean markdown, not JS-rendered HTML only.Fail
Token efficiencyDocs are concise enough to fit an agent context window.Fail

What we found

  • developer.salesforce.com returns HTTP 403 for all programmatic access (robots.txt, llms.txt, sitemap, .well-known/) — the developer portal actively blocks automated discovery.
  • Salesforce has an llms.txt at www.salesforce.com/llms.txt but it is entirely product/marketing focused (Agentforce, AI courses, pricing pages) with no API documentation links.
  • The OpenAPI spec for Salesforce REST API is only available as a beta feature that requires authentication and org-level opt-in — not publicly accessible.
  • Strong MCP ecosystem presence with official Salesforce CLI MCP Server and Platform MCP Server on PulseMCP, plus multiple community servers.
  • Despite blocking automated access, Salesforce has extensive human-readable API documentation with SOQL, REST API, and Bulk API guides — but agents must navigate JavaScript-rendered pages.

What to change

Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.

  1. 01Remove the HTTP 403 block on developer.salesforce.com for automated access — this is the single biggest barrier to agent discovery.
  2. 02Create a developer-focused llms.txt at developer.salesforce.com covering REST API, SOQL, Bulk API, and Metadata API patterns.
  3. 03Make the OpenAPI spec publicly accessible without requiring org authentication.
  4. 04Add AGENTS.md to the salesforce/agent-sdk or forcedotcom/agents repositories.
  5. 05Create llms-full.txt covering core REST API operations, SOQL syntax, and common integration patterns.

Execution coverage · INFORMATIONAL, UNSCORED

Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.

OAuth2 (Web Server Flow, JWT Bearer, Device Flow)Session IDConnected App✓ Error format documented✓ Rate limits documented✓ Pagination documented✕ Idempotency documented

Comprehensive OAuth2 documentation with multiple grant types. REST API returns structured JSON errors. API limits documented per edition (API calls per 24 hours). Pagination via nextRecordsUrl in query results. No idempotency key mechanism documented.

See your own Discry Score.

Drop your API docs URL. See what an agent sees — in 60 seconds, free.

Discry your API — free