Optional crawl fields
On fetch and render requests, include_metadata, include_links, and include_media each add 1 credit when selected.markdown_variant=readability adds 0 credits.
Example: a fetch with metadata costs 2 base + 1 = 3 credits.
Pricing
Know what each web request costs.
Start with 5,000 one-time credits on the Free plan. Fetch, render, search, and screenshots spend different amounts, so choose the operation that matches the page and output you need.
Credit rules
Base costs by operation
These are the published starting costs. Optional fields and qualifying render cache hits affect crawl request totals.
| Operation | Base cost | What it returns |
|---|---|---|
| Page search | 2 credits per returned result | Links to candidate public pages |
| Render request | 10 credits base | Markdown after browser rendering |
| Fetch request | 2 credits base | Markdown from the page's initial HTML |
| Viewport screenshot | 20 credits | PNG of the visible viewport |
| Full-page screenshot | 50 credits | PNG of the scrollable page |
Your authenticated GET /v1/account/usage response exposes current crawl, screenshot, and search credit rules. Read the API documentation.
What changes the total
Fields and cache rules
The request you send determines the total shown in credits_used.
Render cache hits
A fresh render starts at 10 credits. With accept_cache=true, a valid render cache hit has a 1-credit base cost. Optional fields can still add credits.
Fetch does not read from or write to the render cache.
Screenshots are separate requests
A viewport screenshot costs 20 credits; a full-page screenshot costs 50. Screenshot responses contain a PNG URL and storage fields. Fetch or render separately for Markdown.
5,000-credit example
How far can the starting credits go?
Each example spends the whole Free plan's one-time grant on one operation at its base cost. They are alternatives, not a combined allowance.
These base-cost illustrations exclude optional fields and render cache hits. Actual usage also depends on the number of results returned by search and the requests your workflow sends.
Plans
Choose a monthly credit and throughput level
The Free plan has a one-time credit grant. Paid plans include the monthly credits and limits shown below.
Free
$0/mo
For early validation with one-time credits, 30 fetch requests per minute, and 1 browser concurrency slot.
- 5,000 one-time credits
- $0 / cr
- Fetch 30 req / min
- Browser 1 concurrent
Agent Lite
$5/mo
For low-frequency AI agents and occasional automations that need 15,000 monthly credits.
- 15,000 credits / mo
- $0.000333 / cr
- Fetch 60 req / min
- Browser 2 concurrent
- Low-frequency AI agent usage
- Persistent top-ups available separately
Builder
$20/mo
For builders shipping serious crawler workflows with higher limits and better unit economics.
- 80,000 credits / mo
- $0.000250 / cr
- Fetch 180 req / min
- Browser 3 concurrent
- Best upgrade after repeated Agent Lite usage
Growth
$80/mo
For teams scaling production scraping with better unit economics.
- 960,000 credits / mo
- $0.0000833 / cr
- Fetch 480 req / min
- Browser 8 concurrent
Scale
$200/mo
For high-volume pipelines with pricing aligned to large ongoing usage.
- 3,000,000 credits / mo
- $0.0000667 / cr
- Fetch 1,200 req / min
- Browser 20 concurrent
Need terms for higher volume or a custom operational requirement? Contactsupport@anycrawler.com.