Developer Docs

Two products. Two references.

The Scanner measures your site; the Answer Gateway reads every site. Pick your reference below — integrations, discovery files, and payment details are shared.

For site owners

Scanner

Measure your site.

Scan any URL across 58 agent-readiness checks and get a scored report with prioritized fixes.

curl "https://botvisibility.com/api/scan?url=https://stripe.com&format=json"
  • GET/POST /api/scan + async jobs
  • MCP server · CLI · WordPress · webhooks
  • 5 scans/day to evaluate · $0.10/scan over x402
Scanner reference →
For agent builders

Answer Gateway

Read every site.

POST a url and a question; get a verified, excerpt-cited answer with a token-economics receipt — it cannot hallucinate.

curl -X POST https://botvisibility.com/api/answer -d '{"url":"…","question":"…"}'
  • Five terminal states, one response shape
  • Receipt on every call — tokens and dollars
  • 5 questions/day to evaluate · $0.01/answer over x402
Answer Gateway reference →

Integrations & surfaces

Every way to run the same 58-check scan and the Answer Gateway, beyond raw REST:

MCP Server— 11 tools over Streamable HTTP for any MCP client.
CLI— npx botvisibility <url> — terminal and CI.
x402 Payments— Agents buy scans and answers in USDC, no account.
How Agents Pay— Step-by-step x402 purchase guide.
WordPress Plugin— Scan + one-click fixes inside wp-admin.
Claude Managed Agent— Deployable auditor for URLs and repos.
ChatGPT App— Scan from inside ChatGPT.
Python SDK— pip install botvisibility.
Badge— SVG score badge for your README.
Webhooks— Scheduled re-scans with signed change alerts.

Discovery files

Machine-readable manifests agents can fetch to discover these APIs:

FAQ

What is BotVisibility?

Two products for the agent-readable web. The Scanner measures any URL across 58 checks and 5 levels — Discoverable, Usable, Optimized, Indexable, and Agent-Native. The Answer Gateway reads any site for an agent and returns grounded, excerpt-verified answers.

How do agents call the APIs?

Scans: GET /api/scan?url=…&format=json (five per day, then HTTP 402). Answers: POST /api/answer with {url, question}. There is also an MCP server at /api/mcp and a CLI (npx botvisibility example.com).

How does authentication work?

Public access needs no key on either product. Scans: an anonymous OAuth 2.0 client-credentials token (scan:read) or X-API-Key raises the allowance. Answers: a bvag_ Bearer key (daily quota or prepaid credits).

How do agents pay for scans?

Over the daily allowance (five scans), the API returns HTTP 402 pointing at the pay.sh gateway, where an agent settles $0.10 USDC per scan on Solana via the x402 protocol, then receives the full report.

How do agents pay for answers?

The Answer Gateway works the same way: five answered questions a day on POST /api/answer, then HTTP 402 with x402 requirements — $0.01 USDC per answered question at the pay.sh gateway, or $5.00 once for a prepaid key with 1,000 answers. Only `answered` responses ever bill; not_found and the other terminal states are always free.