Salesforce: the 360 agent-readiness check
Salesforce scores 51 of 100 on Ora's agent-readiness scan, a C, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 3: a public API, OAuth, a command line. A challenge page at the door, so the act layer behind it is a guess.
On 9 November 2026 the public site at salesforce.com scored 51 of 100 on Ora's agent-readiness scan, a C, in Ora's CRM category. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. This check reads the act layer first, because that is what the directory records, then the door, what an agent can read, and whether the company is found and recommended. Ora's one-line summary: Salesforce offers discoverable developer resources and an SDK package, but lacks a published OpenAPI specification for agent integration.
The score
| Layer | Asks | Points | Share |
|---|---|---|---|
| Usability | Can agents use it | 24 of 56 | 43% |
| Access | Can agents read it | 16 of 48 | 33% |
| Discovery | Can agents find and recommend it | 11 of 12 | 92% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade C | 51 of 100 | 51% |
What an agent can do
The surfaces an agent acts on: an API it can find and call, an MCP server, an agent card, OAuth metadata, a command line. This is the layer the directory records, so it comes first.
In the directory, Salesforce no MCP endpoint on record; the connector run of 4 November 2026 is on the entry page. Ora's MCP server check for the same domain reads partial; the two look for different things, the directory for a server that answers a handshake and lists tools, Ora for a server it can find from the site.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| MCP server / manifest mcp-server | Partial | 5 of 6 | First-party MCP server published by product org (npm, @salesforce/mcp-provider-aura-experts, 18130 score). Add live handshake at /.well-known/mcp for full credit. |
| MCP well-known discovery mcp-well-known-discovery | Fail | 0 of 2 | No MCP server URL discovered |
| Public API with reachable endpoints public-api | Pass | 7 of 7 | API described in documentation at https://docs.salesforce.com but no machine-verifiable API surface confirmed. GraphQL endpoint at https://salesforce.com/graphql is reachable; |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | Documentation site found at https://docs.salesforce.com |
| Developer portal developer-portal | Pass | 6 of 6 | Developer documentation portal found at https://docs.salesforce.com |
| OpenAPI spec published openapi-spec | Fail | 0 of 7 | No OpenAPI/Swagger specification found |
| API catalog (RFC 9727) api-catalog-rfc9727 | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| A2A / agent-card a2a-agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json |
| Agent discovery file agent-discovery-file | Fail | 0 of 2 | No agent discovery file found |
| OAuth 2.0 support oauth-support | Pass | 5 of 5 | OpenID Connect discovery endpoint found at https://login.salesforce.com |
| OAuth Protected Resource metadata (RFC 9728) oauth-protected-resource | Pass | 2 of 2 | no detail published |
| auth.md exists auth-md-exists | Fail | 0 of 2 | No /auth.md found at site root |
| WebMCP support webmcp | Fail | 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found |
| NLWeb /ask endpoint nlweb-ask | Pass | 1 of 1 | NLWeb /ask endpoint exists but requires authentication (HTTP 403, via GET) |
| CLI tool available cli-tool | Pass | 3 of 3 | CLI package found on npm: @salesforce/cli |
| Multi-language SDK packages rest-sdk-packages | Partial | 1 of 3 | SDK package found only in npm |
| Rate limit response headers rate-limit-headers | Fail | 0 of 2 | GraphQL introspection auth-gated and no header convention documented on GraphQL-tagged pages |
| Idempotency-Key support idempotency-key-support | Fail | 0 of 3 | GraphQL introspection auth-gated and no idempotency documentation found on GraphQL-tagged pages |
| JSON error responses json-error-responses | Fail | 0 of 4 | API does not return JSON error responses (or no API detected) |
At the door
What the site answers when a request arrives with an agent's user agent, and what robots.txt says to agents. 4 checks in this group do not apply to this site and are left out.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Not blocked by bot detection bot-detection | Partial | 0 of 2 | Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot. A challenge is an identity check that verified crawlers pass, |
| Agent crawler reachability agent-crawler-reachability | Partial | 0 of 2 | Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot - a challenge is an identity check verified crawlers pass, so reachability is undetermined rather than blocked (ChatGPT-User: challenged, |
| Redirect hygiene redirect-hygiene | Pass | 1 of 1 | no detail published |
| Web Bot Auth directory web-bot-auth-directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |
What an agent can read
Whether the text is in the first response, what the site publishes for agents, and how it describes itself to them. 4 checks in this group do not apply to this site and are left out.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Content without JavaScript content-no-js | Partial | 0 of 3 | Homepage blocked by WAF/security challenge - content not accessible to agents |
| Sitemap exists sitemap | Fail | 0 of 2 | No sitemap found |
| llms.txt exists llms-txt-exists | Pass | 1 of 1 | Found the llms.txt at https://docs.salesforce.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Pass | 2 of 2 | The llms.txt is well-formatted: 9 lines with markdown links, 884 characters in total. |
| Markdown agent docs markdown-negotiation | Fail | 0 of 1 | Missing markdown content negotiation. Homepage returned text/html when probed with Accept: text/markdown (expected text/markdown), and none of the well-known root paths (/llms.md, /auth.md, /agents.md, /developers.md, |
| Markdown URL fallback markdown-url-fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://salesforce.com/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). |
| Agent mode view agent-mode-view | Fail | 0 of 2 | No agent mode view detected at ?mode=agent (optional) |
| JSON-LD structured data json-ld | Fail | 0 of 4 | No JSON-LD structured data found on homepage |
| Organization schema completeness org-schema-completeness | Fail | 0 of 2 | No JSON-LD found - Organization schema missing |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Fail | 0 of 2 | No JSON-LD found - no entity linking possible |
| Schema type breadth schema-type-breadth | Fail | 0 of 2 | No extended schema types found - AI can only answer basic questions about this entity |
| Metadata completeness metadata-completeness | Partial | 1 of 2 | Only 1/4 metadata signals present - missing: canonical URL, og:image, og:type |
| Agent instruction / when-to-use agent-instruction | Partial | 2 of 3 | When-to-use guidance found at https://docs.salesforce.com |
Found and recommended
Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read. 2 checks in this group do not apply to this site and are left out.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Brand name discoverability brand-search-accuracy | Pass | 3 of 3 | salesforce.com ranks #3 for "salesforce" (searched your brand name alone: we could not read a product term from your site) |
| Wikipedia / Wikidata entity presence wikipedia-presence | Partial | 2 of 4 | Wikidata Q941127 (Salesforce) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage |
| Developer resource discoverability agentic-search-specific | Pass | 3 of 3 | no detail published |
| NPM/PyPI SDK package npm-sdk-package | Pass | 1 of 1 | no detail published |
| ChatGPT app listed chatgpt-app-listed | Pass | 2 of 2 | no detail published |
| Listed on skills.sh skills-sh-listed | Fail | 0 of 1 | No official skills self-published on skills.sh (100 community skills with potential relation to this domain found, but only self-published official skills count) |
| ARD discovery ard-catalog | Fail | 0 of 1 | No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json |
Payments
The agent payment protocols Ora probes for. A site that sells nothing has nothing here, and Ora scores the layer out of zero when none applies. None of the 6 payment checks applied to salesforce.com.
The fixes worth most points
Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for Salesforce, with what Ora observed. The wording of each fix is Ora's; the 28 checks it runs on an MCP server are listed with their layer and tier.
- OpenAPI spec published: fail, 0 of 7, about 4.9 points to gain. Ora saw: No OpenAPI/Swagger specification found
- WebMCP support: fail, 0 of 5, about 4 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found
- JSON error responses: fail, 0 of 4, about 3.2 points to gain. Ora saw: API does not return JSON error responses (or no API detected)
- JSON-LD structured data: fail, 0 of 4, about 2.8 points to gain. Ora saw: No JSON-LD structured data found on homepage
- GraphQL typed error model: fail, 0 of 3, about 2.4 points to gain. Ora saw: GraphQL introspection auth-gated and no typed graphql error model documentation found on GraphQL-tagged pages
Our read
Salesforce is the one company in this batch whose door is shut, and the rest of the read follows from it. Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User and PerplexityBot, the home page came back as a security challenge rather than content, and so the content, the structured data and the heading checks all fail for a reason that has nothing to do with the CRM behind them; the Access layer reads 16 of 48. Past the wall Ora found a documentation site with an llms.txt at docs.salesforce.com, OpenID Connect discovery at login.salesforce.com, @salesforce/cli on npm and a first-party MCP package on npm without a live handshake, and it found neither an OpenAPI specification nor a machine-verifiable API surface. The largest enterprise software company in the set is scoring like a brochure site because the scanner is treated as a bot. Letting the named agents through is the first fix, and the only one that lets the others be judged.
Test your own surfaces
The scan above is free and needs no account: enter a domain at ora.ai and read the same four layers for your own site. For an MCP server, Ora scans the server URL itself and runs 28 of its 132 public checks on it, which is why it is the check this directory recommends; the reasons, the limits and the alternatives are on their own page. The command below runs the same audit from a terminal and exits with 1 under the score you set, so it can gate a deploy.
npx ax@0.10 audit https://example.com --min-score 70All 360 checks, one company a day. Corrections to the corrections page.