What costs credits
Scraping
A scrape costs 1 credit for each URL that is processed successfully. Send three URLs in one request and all three succeed, and that is 3 credits. The size of the page does not change the price. If you ask for AI extraction, the tokens it uses are added on top. Extraction runs when you set aprompt or a schema, or set output to "json". About 4 characters of page content count as 1 token, and roughly 3,300 input tokens or 400 output tokens come to 1 credit. Token credits are added up for the whole job and rounded up once, so a short page with a short answer usually adds a single credit.
If Spidra solves a CAPTCHA on the way, that adds 5 credits per solve. A page with no challenge costs nothing extra. See CAPTCHA solver.
Documents such as PDFs, Word and Excel files are charged like pages. A scanned document that needs AI to transcribe it also uses tokens.
Batch scraping
Each URL in a batch is charged as its own scrape. Failed URLs cost nothing and the rest are charged normally, so a batch of 50 where 45 succeed costs for 45.Browser actions
Browser actions don’t change the price of a scrape. A URL with actions costs 1 credit, however many steps it runs. A few things add to that:- forEach in
navigatemode adds 1 credit for each item page it opens. Items that fail are free. - forEach pagination adds 1 credit for each further results page it opens.
- The AI behind some actions is billed by tokens, like AI extraction: finding an element you described in plain English (such as
"the Next page link"), finding the items of a forEach, and running a forEachitemPrompt. These tokens are added to the job’s own and rounded up once. Steps that use CSS selectors or XPath use no AI.
itemPrompt, and the result’s warnings say so.
Crawling
A crawl costs 1 credit for every page it returns, plus tokens if you give it atransformInstruction or a schema. Token credits are added up across all pages and rounded up once.
To find the pages you asked for, a crawl often reads other pages first, such as a category page that lists products or a section page that links to articles. Those pages are not returned and are not charged. A crawl of 3 book pages that starts from a category page costs 3 credits plus tokens, not 4.
Re-running extraction on pages you already crawled is cheaper, because it only charges for tokens and not for the pages again. See Extract from a crawl.
Parse
Parse costs 1 credit per page parsed, whether the page was read from its own text or with AI. Word, Excel and other non-PDF formats count one page per 3,000 characters of output, at least one. Extracting fields with a prompt or schema adds AI token credits. Pages that can’t be read, and documents that fail, are free. AdryRun request shows the pages and credits before you parse.
Mapping
Map costs 1 credit per call, whatever the number of URLs it returns. A map that finds no URLs costs nothing.Search
Search costs 1 credit per 10 results, per source, rounded up. A source that returns nothing costs nothing.
If you also ask Search to fetch the content of each result with
scrapeOptions, every page fetched adds 1 credit. Fetching content for 5 results from a 10 result search costs 1 for the search plus 5 for the pages, so 6 in total.
Templates and monitors
A template run costs what the same job costs with the tool behind it, usually 1 credit per page read. The template page and Estimate a template run show the number before you run. Runs whose site can’t be read fail without charging. A monitor check costs what one run of its sources costs. The monitor form and Estimate a monitor show the credits per month before you save. A check skipped because you’re out of credits costs nothing.What is always free
- Browser steps. Clicks, typing, scrolling and waiting never cost credits on their own. Only forEach pages and the AI some actions use are charged, as described above.
- Failed jobs. If a scrape, batch item or crawl cannot deliver anything, you are not charged. That includes a page that stays behind a bot-protection challenge after Spidra has tried to get past it, a page that answers with an HTTP error such as 400, 401, 403, 429 or a server error, and a page that is still blank after a CAPTCHA was solved. None of these are charged, and the CAPTCHA solve is not charged either.
- Reading things. Checking a job’s status, listing logs and reading your usage cost nothing.
Proxy bandwidth
Stealth Mode routes a request through a residential proxy. It does not cost extra credits. Instead it uses your proxy bandwidth, a separate allowance measured in MB of data downloaded. A typical page uses around 2 MB. Pages heavy with images, video or ads can use 20 MB or more, because the browser downloads everything on the page and not just the text. Each plan includes an amount (50 MB on Free up to 5 GB on Pro, see Plans and Pricing). If you need more, buy a bandwidth top-up.Credits are held while a job runs
When you submit a job, Spidra holds the most it could cost and returns whatever is not needed when the job finishes. While a job is running, the held credits already count toward your balance. If your balance cannot cover the hold, the request is rejected with a403 before anything runs.
When you run out
Once your plan credits are used up, Spidra uses any top-up credits you have. With none left, new jobs fail with a403 and the message “You have exceeded your monthly credit limit”. You have three options:
- On a paid plan, buy a top-up and carry on straight away.
- Upgrade your plan.
- On a paid plan, wait for your credits to reset at the next billing cycle. The Free plan’s credits do not reset.
Check your balance
- Dashboard: the Usage page shows your credits and proxy bandwidth, with a daily chart. There is also a Credit Usage meter at the bottom of the sidebar.
- API:
GET /accountreturns what you have left, andGET /usage-statsshows usage over time. - Per job: every scrape and search in your logs lists the exact credits it used.
Plans and Pricing
What each plan includes
Top-ups
Add credits or bandwidth on top of your plan

