Scout

Tiers & credits

Self-serve Free, Basic, and Pro. One wallet per Macrocontent account — all API keys share the same credits.

Plans

Tier	Price	Credits / period	Rate limit	`evaluate`
Free	€0	500	~30/min	no
Basic	€29/mo	10 000	~120/min	no
Pro	€99/mo	50 000	~250/min	yes

Wallet scope

Credits and tier live on the Macrocontent account, not per key. Creating more keys does not multiply free credits.

Credits and rate limits are different budgets

Credits limit how much work you can buy; rate limits limit how fast you can send requests (~30 / ~120 / ~250 per minute by tier). Batch job designers should plan for both: empty wallet → 402; too many parallel calls → 429 (retryable). Also documented under Authentication.

Period rollover

Billing periods are rolling ~30 days. Rules:

Plan credits — unused included credits expire at period end (they do not stack).
Pack credits — purchased top-ups never expire and carry into the next period.
New period balance = fresh plan allowance + remaining pack credits.
PAYG overage counter resets each period.

Pay as you go

Default off. Toggle in Scout console → Plans & credits (or My Account → Scout).

PAYG off + empty prepaid (plan + packs) → 402 CREDITS_EXHAUSTED
PAYG on → usage beyond prepaid is tracked as overage
€ spend limit (optional) — set a max euro overage per period; the console shows the ≈ credit equivalent (€0.005/credit). Exceeding the limit rejects the request before the browser runs (PAYG_SPEND_LIMIT_EXCEEDED)
429 remains rate-limit only — not used for empty credits

Predictable add-ons

Each endpoint has a fixed base cost. Additional credits apply only when you enable options or raise timeouts above the included runtime. Before a call:

POST /v1/estimate — same shape as the real request; returns estimatedCredits, maximumCredits, and items[]
billing.maxCredits on the request body — hard per-call cap; overshoot → billing_limit_exceeded (no browser run)
Response field billing (and X-Scout-Credits-* headers) — full breakdown after the call
Console Usage — request history with the same breakdown

Scout-internal retries, worker crashes, and API errors without a usable result are fully refunded after the run. Successful crawls are settled to processed pages only (unused reserved page credits refunded). Extended runtime is settled to actual duration, never above a reserved timeout addon.

Credit packs (catalog)

Pack	Credits	Price
pack_1k	1 000	€5
pack_5k	5 000	€22
pack_25k	25 000	€100

Packs are prepaid top-ups (independent of PAYG). Buy them in My Account → Scout → Plans & credits via Stripe Checkout. Optional Dashboard Price IDs: STRIPE_SCOUT_PRICE_PACK_* (otherwise inline price_data).

Checkout & webhooks

Paid tiers: Stripe Checkout mode=subscription
Packs: Checkout mode=payment
Manage card / cancel: Stripe Customer Portal from the same Account page
Entitlements apply via /webhooks/stripe (metadata.product=scout) — not success URL alone

Endpoint costs

Route	Credits
`health, usage, estimate, devices, domains, templates, job poll`	0
`POST /v1/dns, /v1/robots`	1
`extract, inspect, visibility, tech, files`	3
`POST /v1/assert`	3 + 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/headers`	4
`security, a11y, performance, sandbox`	5
`screenshot / screenshot/json`	8 + fullpage(+2) + HAR(+2) + timeout
`screenshot/viewports`	8 × viewports (+ HAR / timeout)
`screenshot/diff, opengraph+screenshot, diff/dom`	8–10
`journey`	10 + 2/step (+15 evaluate; debug; timeout)
`crawl`	15 + 2×processed pages (reserve then settle)
`jobs`	sum of nested requests