Docs · v1.4

Build with Scovant.

Run scans, simulations, and showcase from the dashboard — or drive it all from your pipeline: the REST API, CI/CD trigger, webhooks, and the MCP interface are live today. Entries marked “Soon” are on the roadmap.

Quickstart · 4 of 8

Scans.

A scan crawls your site and evaluates more than 30 compatibility rules across 7 categories.

Trigger a scan

POST /api/scans

Body: { "site_id": "<uuid>", "targets": [{ "type": "url", "url": "https://example.com" }] }

POST /api/scans also accepts an scvt_ API token (Authorization: Bearer scvt_...), scoped to the token's workspace.

Returns { "id": "...", "status": "queued" } immediately.

Scans cost 1 credit — the same workspace balance used for simulations and Fix Plans. When the balance is insufficient the endpoint returns 402 with the available credit packs and no scan is created. Enterprise workspaces don't spend credits on scans. If a scan gets stuck in the pipeline, Scovant automatically sweeps it to failed and refunds the credit.

Scan lifecycle

pending → queued → running → scoring → completed | failed | partial

Scoring categories and weights:

  • Discoverability (robots.txt, sitemap, canonical tags)
  • Structured data (JSON-LD schemas)
  • Consistency (price display vs structured data, conflicting or duplicate entities)
  • Actionability (works without JavaScript, deep links, MCP/agent-interface discovery)
  • Trust (returns policy, shipping info, citation/OpenGraph meta)
  • UCP (Universal Commerce Protocol profile, checkout, signing keys)
  • Citability (content sites only — how readily AI search engines can quote your pages)