HonestClaw · What is Agent Readiness? · How we score
Limited. Agents will struggle to discover or use this site without human help.
HonestClaw measured how well salesforce.com's site and APIs work for AI agents — across 9 dimensions and 27 automated checks. Score: 17/100 (Limited).
Scanned · scanner v1.3.0 · 27 of 27 checks conclusive.
5 of 6 scored areas have measured gaps. Permissions & policy is furthest along; Interfaces & data has the largest measured point gap.
1 additional observation provides context and does not affect the score.
Reachable entry points
No RFC 9727 API Catalog found at /.well-known/api-catalog.
These are recorded points before the total is normalized to 100.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No non-owned /.well-known/ descriptors found.
These are recorded points before the total is normalized to 100.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No public evidence URL recorded for this check
No RFC 8288 Link headers found on any probed response.
These are recorded points before the total is normalized to 100.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No public evidence URL recorded for this check
An agent-relevant subdomain is live and serves its expected content kind (developer.salesforce.com).
These are recorded points before the total is normalized to 100.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No public evidence URL recorded for this check
Root and www converge on www.salesforce.com, with a matching canonical tag.
These are recorded points before the total is normalized to 100.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
https://www.salesforce.com/sitemap.xml is a dated sitemap whose URLs include docs/pricing/api surfaces.
These are recorded points before the total is normalized to 100.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Clear and consistent publisher policy
robots.txt at https://salesforce.com/robots.txt declares a sitemap. Declared sitemap https://www.salesforce.com/sitemap.xml resolves as valid XML.
These are recorded points before the total is normalized to 100.
Published policy for the relevant use: indexing, training or user retrieval
Different policy syntaxes and business permissions are not independent readiness capabilities. Blocking training should not imply that an agent cannot use a public API.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Usable API reference and examples
API reference documentation lacks depth or was not found.
These are recorded points before the total is normalized to 100.
A documented API or tool interface
Reference depth and valid fenced examples contribute to the same documentation outcome. Parsing an example is weaker than executing it successfully.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Usable documentation entry and references
A valid llms.txt header exists at https://developer.salesforce.com/llms.txt, but it lists few or no link sections (1 links, 1 sections).
These are recorded points before the total is normalized to 100.
Public documentation; llms files optional
An index, full text and modular files offer different routes to documentation. Useful content and working references matter more than the number of formats.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Machine-readable facts
No machine-readable pricing endpoint found (HTML pricing pages do not qualify).
These are recorded points before the total is normalized to 100.
Facts relevant to the product; pricing only when there is a price to disclose
Structured facts can help agents interpret a page. Markup volume and the number of schema types alone do not establish accuracy, consistency or task success. This check has no external governing spec; its weight is product judgment.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Complete and usable operation contracts
No published structured-data contract found (no typed spec response schemas).
These are recorded points before the total is normalized to 100.
Detected interface; pagination only for collections, async only for long-running jobs, batch only for multi-item operations
Usable schemas and operation patterns can reduce ambiguity for clients. More endpoints or constraints alone do not establish that an operation is easier to use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No data export or bulk API documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Detected interface; pagination only for collections, async only for long-running jobs, batch only for multi-item operations
Usable schemas and operation patterns can reduce ambiguity for clients. More endpoints or constraints alone do not establish that an operation is easier to use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Usable supported interface
No API endpoint found at common paths (only HTML pages or 404s).
These are recorded points before the total is normalized to 100.
Interface-enabled product; no requirement to implement every protocol
REST, GraphQL, MCP, SDKs and CLIs offer alternative or complementary access paths. The useful choice depends on the task and client; no single format serves every workflow.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No OpenAPI/Swagger specification found.
These are recorded points before the total is normalized to 100.
Interface-enabled product; no requirement to implement every protocol
REST, GraphQL, MCP, SDKs and CLIs offer alternative or complementary access paths. The useful choice depends on the task and client; no single format serves every workflow.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
SDK libraries page at https://status.salesforce.com/docs/sdks: 0 GitHub repos, 0 registry links, 0 install commands (0 pointers).
These are recorded points before the total is normalized to 100.
Interface-enabled product; no requirement to implement every protocol
REST, GraphQL, MCP, SDKs and CLIs offer alternative or complementary access paths. The useful choice depends on the task and client; no single format serves every workflow.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
MCP discovery evidence
No MCP server found at the standard locations an agent would check.
These are recorded points before the total is normalized to 100.
MCP surface
An MCP descriptor helps clients locate a service. This additional observation does not earn separate points for evidence already represented by the scored MCP check.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Payment capabilities
No HTTP 402 response or machine payment protocol headers detected.
Useful context, outside the readiness score. Adoption, payment support and retrieval cost are not readiness quality by themselves.
Payment-enabled business model
Payment support describes what the business offers. It must not make a research publication or free public service appear less ready.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Usable least-privilege authentication
No programmatic authentication documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Protected operations; anonymous access is valid when intended
Discovery, documentation and credential lifecycle jointly support a usable authorization flow. A public read-only service need not require OAuth.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No authentication documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Protected operations; anonymous access is valid when intended
Discovery, documentation and credential lifecycle jointly support a usable authorization flow. A public read-only service need not require OAuth.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No credential management documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Protected operations; anonymous access is valid when intended
Discovery, documentation and credential lifecycle jointly support a usable authorization flow. A public read-only service need not require OAuth.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Safe integration environment
No sandbox or test environment documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Operations whose side effects or onboarding require a safe test environment
A sandbox helps validate consequential integrations; it is not necessary for every public content site or read-only API.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Actionable limits
No rate limit documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
An interface with quotas or throttling
Published limits and response headers help clients pace requests and recover from throttling. They describe related aspects of the same service constraint.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Observable outcomes and recovery
No webhook or event documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Detected interface; idempotency for repeatable writes, webhooks only for event-driven workflows
Observable state and actionable errors help recovery. A status page or error schema does not prove successful repair.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No error documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Detected interface; idempotency for repeatable writes, webhooks only for event-driven workflows
Observable state and actionable errors help recovery. A status page or error schema does not prove successful repair.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No retry or idempotency documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Detected interface; idempotency for repeatable writes, webhooks only for event-driven workflows
Observable state and actionable errors help recovery. A status page or error schema does not prove successful repair.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Health/status endpoint found at https://status.salesforce.com/health (HTTP 200).
These are recorded points before the total is normalized to 100.
Detected interface; idempotency for repeatable writes, webhooks only for event-driven workflows
Observable state and actionable errors help recovery. A status page or error schema does not prove successful repair.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Change and compatibility information
Versioning is mentioned at https://developer.salesforce.com/docs, but not on a page dedicated to documenting it. (source: docs)
These are recorded points before the total is normalized to 100.
Maintained interface or evolving product
Version identifiers and change records help clients manage compatibility as an interface evolves.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
A changelog is published at https://www.salesforce.com/products/innovation/releases/ with multiple recent dated entries, indicating it is actively maintained.
These are recorded points before the total is normalized to 100.
Maintained interface or evolving product
Version identifiers and change records help clients manage compatibility as an interface evolves.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.