Scout meters usage in credits. Plans have a fixed, published number of credits, never “unlimited.”
Plans
| Plan | Price | Credits | Notes |
|---|
| Free | $0 | 5,000 one-time | Public free tier, the acquisition hook. |
| Beta | $0 | 10,000 / 30 days | Existing beta cohort allowance. |
| Monthly | $12/mo | 50,000 / month | The hero plan. Resets each billing cycle, hard-stops at the cap. |
| Pay-go packs | 10/25 / $100 | 10,000 / 30,000 / 150,000 | One-time, never expire. Secondary to Monthly. |
What a credit buys
| Action | Cost |
|---|
| Scrape one page, crawl one page, or one product/record | 1 credit |
| Screenshot | 3 credits |
| Browser render | 5 credits |
| Browser minute | 10 credits |
| Company dossier (representative crawl, varies by site size) | ≈ 200 credits |
A useful way to think about the Monthly plan’s 50,000 credits: roughly 20,000 pages, or 10,000 product records, or 100 dossiers, or any mix of the three.
Checking your balance
curl "$SCOUT_HOSTED_BASE_URL/v1/hosted/me" \
-H "Authorization: Bearer $SCOUT_HOSTED_API_KEY"
The response includes balance.standard_credits_remaining, balance.browser_credits_remaining, and your plan’s limits (max pages per run, and so on). See Account for the full usage and purchase history endpoints.
Standard actions (scrape, crawl page, map URL, product record, destination push) draw from the same standard-credit pool. Screenshots and browser-rendered work draw from a separate browser-credit pool.