# Salesforce — API Agent Score

> Score: 69/100 (Grade: C) | Domain: salesforce.com | Rubric: 1.0.0 | Checked: July 24, 2026

Salesforce scored 69/100 (C), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/salesforce)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 69/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 89/100 (A)
- Developer Experience: 66/100 (C)
- Agent Discovery: 77/100 (B)
- Agent Understanding: 74/100 (B)
- Agent Usability: 50/100 (D)

## Check Results

### API Design

- [pass] Auth declared & discoverable — OAuth discovery metadata at https://api.salesforce.com/.well-known/oauth-authorization-server. Investigated: wellknown 100%, docs 65%, spec 40%.
- [warn] Schema coverage & depth — 7 of 68 public signatures use loose types (anyTypeRatio=0.103). Investigated: sdk 79%, spec 58%.
- [warn] Machine-readable, versioned contract — info.version="1.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [warn] Security & governance hygiene — 6 credential-shaped strings detected in spec: private-key-pem (×6). Investigated: spec 90%, wellknown 0%.
- [pass] Example coverage — 0% example coverage. Investigated: spec 100%, sdk 100%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://cloud.mail.salesforce.com/request-access; free tier / sandbox documented. Investigated: docs 100%.
- [pass] Description completeness — 36% description completeness. Investigated: spec 100%, sdk 28%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (simple-salesforce/simple-salesforce, 241 snippets). Investigated: docs 100%, sdk 92%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 1 pages. Investigated: docs 42%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap present (1 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — No 4xx/5xx response codes (or default error response) documented anywhere in the spec. Investigated: docs 100%, spec 50%.
- [warn] Operation purpose clarity — 17% of operations are agent-inferable. Investigated: spec 75%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 75%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 1 assessed pages (1 JS-rendered). Investigated: docs 0%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [warn] Pagination documented & consistent — 6 list endpoint(s) exist but no pagination params found. Investigated: docs 50%, spec 44%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%, spec 0%, docs 0%.
- [warn] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 50%.
- [warn] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 20%, docs 20%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 0%.

## Executive Summary

Salesforce's API program has a strong foundation in API design — the contract is machine-readable, well-typed, and auth is solid. However, partners and their AI agents face two critical gaps: there is no structured guidance for agents to understand how to use the APIs (missing AGENTS.md and structured doc metadata), and onboarding is slow due to absent quickstarts and sparse code samples. Prioritize making the API surface agent-readable and adding executable onboarding artifacts first, then shore up operational reliability signals like idempotency documentation so partners can build production-grade integrations with confidence.