Developer integration · JSON over HTTP
Turn any public URL into structured website intelligence
Santos exposes versioned, machine-payable HTTP interfaces for fast triage, Agent Readiness, and browser-rendered evidence. No account or traditional API key is required; paid requests use x402 on Base.
Read a real report first
Every domain below was audited with the production engine — same scores, same evidence, same prioritized fixes you would be buying. The Quick API costs 0.015 USDC per successful audit, and the complete Agent Readiness audit costs 0.075 USDC per successful audit.
What the assessment covers
Safe Fetch
GET /v1/fetch · synchronous · 0.002 USDC per successful SSRF-guarded raw fetch.
Content Extraction
POST /v1/extract · synchronous · 0.005 USDC per successful page-to-Markdown extraction.
Structured Extraction
POST /v1/extract/structured · synchronous · 0.08 USDC per successful schema-conforming extraction.
Feed Parser
GET /v1/feed · synchronous · 0.003 USDC per successful RSS, Atom, or JSON Feed parse.
Link Map
GET /v1/links · synchronous · 0.003 USDC per successful tagged link map.
Summarizer
POST /v1/summarize · synchronous · 0.033 USDC per successful Claude page brief.
Quick Intelligence
GET /api/audit · synchronous · 0.015 USDC per successful audit.
Batch Audit
POST /api/audit/batch · synchronous · 0.50 USDC flat for up to 50 URLs.
Agent Readiness
GET /api/agent-readiness · synchronous · 0.075 USDC per successful audit.
Screenshot & PDF
GET /v1/screenshot · synchronous · 0.01 USDC per successful browser render.
Deep Intelligence
POST /v1/audits · asynchronous · 0.225 USDC per bounded compute reservation.
Choose the smallest honest scope
Use GET /api/audit for lightweight single-page signals, GET /api/agent-readiness for bounded agent-interface discovery, and POST /v1/audits when rendered browser evidence and downloadable artifacts justify an asynchronous job.
Stable integration surfaces
The OpenAPI 3.1 document describes typed inputs, responses, errors, and payment behavior. The capability manifest helps an agent select a tier, while the MCP endpoint provides discovery and a canonical paid handoff.
Designed for safe automation
Public targets are restricted to HTTP and HTTPS with private networks blocked. Quick audits settle only after a successful response. Deep jobs support idempotency and use per-job access tokens for report retrieval.
Interface example
curl 'https://api.santosautomation.com/api/audit?url=https%3A%2F%2Fexample.com'
# Decode PAYMENT-REQUIRED, sign the quoted x402 terms, then retry.
# See /openapi.json for schemas and examples.Frequently asked questions
What is the difference between Quick and Deep audits?
Quick audits use bounded fetch-and-parse checks. Deep audits use a real browser for rendered accessibility, lab performance, network, console, screenshot, and passive security evidence.
Is Agent Readiness the same as SEO?
No. SEO mainly addresses search discovery and ranking. Agent Readiness also examines structured meaning, callable interfaces, machine-readable documentation, and operational trust.