Versioned methodology · 1.0.0

How Santos measures Agent Readiness

A passive, evidence-based assessment of whether agents can discover, understand, select, invoke, and—when applicable—transact with a public website or service.

Classification before scoring

Santos classifies a target as a general website, documentation site, API provider, MCP provider, or agent-commerce provider. API, MCP, and commerce categories can be marked not applicable. Their absence does not lower the score of a site that does not claim to expose callable services.

Category weights

CategoryWeightObserved evidence
Discovery & documentation20%llms.txt, interface links, machine-readable docs, and crawlability
Structured identity & context15%parseable JSON-LD, provider identity, WebAPI and Offer data, and claim consistency
API readiness20%OpenAPI discovery, validity, operations, schemas, access, and capability manifests
MCP readiness25%advertising, registry evidence, transport, tools, outputs, authorization, and safety
Operational trust10%HTTPS, contact, terms, privacy, errors, limits, and accurate claims
Agent commerce10%applicability, pricing discovery, unsigned challenges, idempotency, settlement, and receipts

Pass, fail, unknown, or not applicable

Only executed pass and fail findings contribute to a category subscore. Unknown evidence remains visible and reduces tested coverage. Not-applicable checks are excluded from the denominator.

Weighted, deterministic scoring

Each check has a published internal weight. Category scores reflect the passed weight among executed checks. The overall readiness score combines applicable category scores using the weights above; no language model changes pass/fail or numeric scores.

Evidence and confidence

Findings identify the exact public interface and normalized evidence used. Confidence communicates evidence strength. Recommended actions are ranked from failed checks by impact and expected effort.

Website Intelligence presentation

The four Website Intelligence dimensions synthesize completed SEO, accessibility, performance, security, and Agent Readiness categories. Callable is shown as not applicable when API, MCP, and commerce surfaces do not apply. Historical API scores remain unchanged.

Safety and limitations

  • Public HTTP and HTTPS surfaces only; private and metadata networks are blocked.
  • No authentication to or payment of the audited target.
  • No form submission, target business-tool invocation, or target code execution.
  • llms.txt is treated as a proposal and registry evidence as optional preview infrastructure.
  • OpenAPI analysis is structural and bounded; remote schemas are not recursively executed.
  • The result is technical evidence, not certification or a guarantee of AI answer visibility.