Web scraping API cost calculatorCalculators

What scraping your pages costs, per provider and per page you get back.

Type how many pages you scrape a month. See each provider's price per scrape, success rate, cost per successful scrape, monthly total and median (p50) time, from real looot runs in the last 30 days. A site that blocks scrapers counts as a failed call.

Cost to you

Free

Free with no account. The math runs in your browser on looot's own run data from the last 30 days.

30-day runs
data
none
API calls
none
account

Use it now

Use the Web scraping API cost calculator here

It runs in your browser. Nothing you type is sent anywhere, there is no signup and no limit.

Run it from your agent

Copy one prompt, give it to your agent.

Fill in the placeholder, paste it, and the agent runs the same job with current data on your looot account and shows the cost.

  • You give it: how many pages you have, and whether that is every month.
  • Billed per call, nothing while your agent is idle.
  • The agent shows the price before it calls.
Prompt: Web scraping API cost calculator
Use looot to price web.scrape.markdown for [number] pages. 1. Set up https://looot.ai/skill.md. 2. Search the catalog for job web.scrape.markdown and inspect each provider's price per call. 3. Divide each price by its 30-day success rate. 4. Return one table: provider, price, success rate, cost per success and the total for my count, cheapest per success first.

Give this to your agent
Setup command
set up looot - https://looot.ai/skill.md

What comes back

What your agent gets from web scraping api cost

Field names as the providers return them. The exact set varies by endpoint, and your agent reads it from the catalog.

  • price per scrape for each provider
  • success rate and cost per successful scrape
  • total for your pages, per month and per year when you pick monthly
  • median time and run count from looot's last 30 days

Use it for

What people do with web scraping api cost

  • Budget a crawl

    Type the pages your crawler or agent reads each month and see the bill per provider, per month and per year.

  • Price in the blocked pages

    A site that blocks scrapers fails the call. The table ranks by cost per successful scrape, so those failed calls are in the price of every page you get back.

  • Pick on speed

    An agent that reads a page waits on the provider. The figure above the table names the provider with the lowest median (p50) time.

  • Hand it to your agent

    Run web.scrape.markdown from your agent with fallback on. looot picks a provider that can answer and tries the next on a miss.

Set up once

Three steps. Your agent does the rest.

Keep going

FAQ

Questions about web scraping api cost

It is the price per scrape divided by the success rate. A provider that answers 8 calls in 10 costs 1.25 times its price for each answered scrape, because you pay for the failed calls too.

From every web.scrape.markdown call made through looot in the last 30 days, the same data as the benchmark page for this job. Prices are what looot charges per call from a prepaid balance. The page prints the date it read them.

A provider needs 20 calls in the last 30 days to be ranked, the same floor as the benchmark pages. Below that, a few calls move the success rate too much to compare.

The share of calls the provider answered without an error. An empty answer counts as an answer. It does not check that the data is right, and calls that failed on looot's side are left out.

Yes, free with no account. The math runs in your browser and makes no API call. The numbers come from looot's public catalog, read at most once an hour.

Connect the looot MCP server and run endpointId "job:web.scrape.markdown" with fallback on. looot picks a provider that can answer now and tries the next on a miss. You see the price before each call and pay from a prepaid balance.

The first row of the table is the cheapest per successful scrape on looot's own runs in the last 30 days. On 2026-11-11 that was Jina AI, over 25,007 calls. The lowest price per scrape is not always the cheapest per page: a provider that fails more often costs more for each page it returns.

Yes. When the provider cannot fetch the page because the site blocks it (a 403, a captcha or a bot wall) and returns an error, the call counts as a failed run in the success rate, the same as a timeout. Only failures on looot's own side are left out. If a provider returns the block page itself as text, that call counts as an answer, because looot does not check what the page says. The rate mixes every site scraped through looot, so a list of sites that block bots will fail more often than the table shows.

The one with the lowest median (p50) time in the table: half of its calls on looot in the last 30 days answered faster than that. On 2026-11-11 that was Keenable, at 489 ms over only 26 calls, while Jina AI had a median of 4.9 s over 25,007 calls. The page quotes p50, not p95. looot does not publish a 95th percentile yet, so a fast median says nothing about a provider's slowest pages.

No. Website to markdown scrapes one page for you now, through looot. This calculator prices a number of pages with each provider before you run them, and reads the same web.scrape.markdown job.

Updated

For agents
tool
Web scraping API cost calculator
category
Calculators
input
How many pages you have, and whether that is every month
output
price per scrape for each provider, success rate and cost per successful scrape, total for your pages, per month and per year when you pick monthly, median time and run count from looot's last 30 days
price
per call, read live from the catalog on the web page
web tool
runs in the visitor's browser, no API call, free with no account
schedule
on demand
setup
https://looot.ai/skill.md
llms.txt
https://looot.ai/llms.txt
updated
2026-11-11

Run web scraping api cost from your own agent.

Start your workspace, top up, and paste the prompt into the agent you already use. It runs the job with live data and shows the cost first.