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 · 6 of 8

Simulations.

Simulations run a browser-based journey on your site — either a fixed script or a real AI agent acting autonomously.

Trigger a simulation (dashboard or API token)

POST /api/simulations
Authorization: Bearer scvt_...
{ "site_id": "<uuid>", "scenario_type": "agent_commerce",
  "start_url": "https://example.com", "agents": ["claude"] }

The start_url must be on the site's registered domain (subdomains included) — an off-domain URL is rejected with 400 {"error": "start_url_outside_site"} and no run is created.

Supported agents: a growing multi-agent catalog — Claude, Nova, Llama, and more — all via AWS Bedrock cross-region inference profiles.

Simulations are credit-gated — script and AI-agent runs alike, one credit per run. Requesting agents: ["claude","nova"] consumes two credits. When the balance is insufficient the endpoint returns 402 with the available credit packs and no run is created. Credits are purchased via Paddle (packs of 10/25/60/150) and never expire; Enterprise workspaces don't spend credits on script simulations.

CI-triggered simulations (POST /api/ci/trigger with run_simulation=true) consume credits the same way.

Simulation lifecycle: pending → queued → running → completed | failed

Results include per-step traces you can replay in the dashboard.