Scout in development · launch 1 Dec 2026. Try it live · docs

Pricing

Credits & Tiers

Scout bills each API call in credits: a fixed base cost per endpoint, plus named extras only when you opt into options or longer timeouts.

Predictable base pricing

Base cost first — add-ons only when you opt in

Every Scout endpoint has a fixed base cost. Additional credits apply only to selected options (for example full-page capture or HAR), larger workloads, or execution timeouts beyond the included runtime. Estimate with POST /v1/estimate, cap a call with billing.maxCredits, and review the billing breakdown on every response — including reserved vs refunded credits after settle. Pay-as-you-go overage can use a euro spend limit so you are never surprised.

  • Base screenshot: 8 credits (viewport)
  • Full-page: +2 · HAR: +2
  • Runtime settles to actual duration (≤ reserved timeout)
  • API errors & unused crawl pages: full / partial refund

Plans

Pick a credit budget and see what it actually buys.

Plan credits are your recurring monthly budget. Packs sit on top, do not expire, and PAYG only starts after prepaid credits run out.

Selected

Basic
10,000 credits / period · 120 RPM

Equivalents

How far does a plan go?

Pick a plan. The cards show how many typical Scout runs that budget covers.

Basic

Screenshot (full-page)

Full-page capture including the base cost

1,000
Screenshots

Cost per run: 10 credits

Basic

A11y snapshot

Structured accessibility facts

3,333
A11y checks

Cost per run: 3 credits

Basic

Assert (4 rules)

Release gates with 4 assertions

1,666
Assert calls

Cost per run: 6 credits

Basic

Journey (5 steps)

Multi-step browser flows

500
Journeys

Cost per run: 20 credits

Basic

Extract

DOM / content extracts as JSON

3,333
Extract calls

Cost per run: 3 credits

Costs per endpoint

Endpoint costs without guesswork

Cost follows the output. A screenshot costs more than an extract; a journey costs more than a single assert call.

RouteCredits
health, usage, estimate, devices, domains*, templates*, job poll0
POST /v1/dns, /v1/robots1
extract, inspect, visibility, tech, files3
POST /v1/assert3 + 1 per assert after the first (max 25)
cookies, console, assets, json-ld, canonical, sitemap, images, resources, a11y-snapshot, forms, links, opengraph (no screenshot)3
POST /v1/pdf/extract, /v1/checks/network, /v1/diff/headers4
security, a11y, performance, sandbox5
screenshot / screenshot/json8 + options
screenshot/viewports8 x viewports
screenshot/diff, opengraph+screenshot, diff/dom8–10
journey10 + 2/step (+15 evaluate; debug screenshots; timeout)
crawl15 + 2× processed pages
jobssum of nested requests

Credit packs

Extra credits without changing plan

Packs are prepaid top-ups. They sit on top of the plan wallet and roll over across periods.

1,000 credits
€5 · €0.005 / credit
pack_1k
5,000 credits
€22 · €0.0044 / credit
pack_5k
25,000 credits
€100 · €0.004 / credit
pack_25k

Pay as you go

Overage only if you turn it on

With PAYG off, Scout returns 402 CREDITS_EXHAUSTED when prepaid credits run out.

With PAYG on, further usage is billed as overage. Rate limits stay separate.

Use this for monitoring, agent runs, or journeys that should not stop mid-flow.

Understand credits, then top up the wallet

Use GET /v1/usage for exact consumption. Manage tiers, packs, and PAYG in the Scout console.