Prices checked November 16–18, 2026.
A scraping API is cheaper per request. A managed service is usually cheaper per usable product record, once you count the developer time needed to turn API responses into clean product data. The API comes out ahead when you have developers, very large volumes and a few big sites that the vendor already parses for you. For a team collecting data from a handful or a few dozen competitor stores, the managed route is often several times cheaper in total.
This guide is for teams that have already decided not to build data collection from scratch and are choosing between the two ways to buy it. If you are still deciding whether to build in-house at all, start there. Below we break down how each model charges, the costs that do not show up on pricing pages, and two ecommerce scenarios with the full monthly math, so you can see how web scraping pricing works out in practice.
Disclosure: ShopScraping is a managed service with API delivery. We show where a scraping API is the better choice, and we list every assumption behind our numbers so you can replace them with your own.
Scraping API vs Managed Service at a Glance
Scraping API | Managed service | |
|---|---|---|
What you buy | Access to pages: proxies, rendering, unblocking | Finished product records on a schedule |
Who writes and fixes parsers | Your developers (except for sites the vendor parses) | The service |
Billing unit | Requests, credits, successful results or records | Products, websites and collection frequency |
How predictable the bill is | Varies with site difficulty, rendering and retries | Fixed plan price |
Typical entry price | About $20–50/mo plus usage | About $20–30/mo for small scopes |
Who checks data quality | Your team | The service |
Time to first dataset | Days to weeks, depending on the number of stores | Minutes to days |
Best for | Engineering teams, very large volumes, a few big sites | Teams without spare developer time, many different stores |
The table compares models, not vendors. For named products in each category, with prices and limits, see our ecommerce scraping tools compared by name.
Access API vs Data Delivery: What You Actually Pay For
Both models can involve an API, which is where much of the confusion starts. The word means two different things here.
A scraping API is an access API. You send it a URL; it fetches the page through its proxy network, renders JavaScript if needed, gets past bot protection and returns the result. For a short list of popular sites, some vendors also return parsed JSON. For everything else you get HTML, and turning it into a price, a stock status or a GTIN is your job. This is what most people mean by a web scraping API.
A managed service delivers data. You tell it which stores, which fields and how often; it runs the collection, adapts when a store changes its layout and sends you finished records. Some providers deliver over an API too, but that API returns ready product data, not pages. This is what "web scraping as a service" means in practice.
ShopScraping works the second way. You paste a store, category, brand or product URL, and fields are detected automatically, so you receive normalized product fields such as price, sale price, stock status, SKU, EAN and GTIN, specifications, images and ratings. Delivery comes through API, CSV, Excel or JSON, plus import-ready files for Shopify and WooCommerce. API delivery is included on every plan.
The difference matters for cost. With an access API you pay for attempts to reach a page. With a data service you pay for the product records you end up with. If you need a refresher on the mechanics underneath both, see how ecommerce scraping works.
How Scraping APIs Charge
Scraping API pricing is hard to compare because every vendor counts a different unit. These are the five common models, with one example each:
Billing unit | How it works | Example | What makes it grow |
|---|---|---|---|
Per request or credit | Each request uses credits; extra features can use more | Scrape.do: $29/mo for 250,000 credits; only successful requests are charged | Rendering, premium proxies, pagination |
Per successful result | You pay only for results that come back | Oxylabs Web Scraper API: Micro plan $49/mo; $1.00 per 1,000 results for ordinary store domains, $1.50 with JavaScript rendering | Ordinary stores cost more than Amazon |
Per record from pre-built scrapers | Parsed records from sites the vendor supports | Bright Data Scraper APIs: from $0.75 per 1,000 records ($1.00 list price) | Works only on the supported list |
By site difficulty and rendering | The rate depends on how hard the site is and whether a browser is needed | Zyte API: $0.13–1.27 per 1,000 HTTP requests; $1.01–16.08 per 1,000 browser-rendered requests | Browser rendering costs roughly 8–13 times more |
Compute and usage | You pay for platform usage plus the price of each scraper | Apify: from $19/mo, plus compute units and per-Actor prices | Hard to predict in advance |
Two patterns matter most. First, the headline rate assumes an easy site; protected stores and JavaScript-heavy pages move you into a higher band. Second, real-time e-commerce scraping API pricing grows linearly with frequency: collecting the same catalog daily instead of weekly costs about seven times more in requests.
These are the billing models for collecting data. Price trackers charge in other ways, per URL or per channel; we cover how price monitoring tools charge separately.
How Managed Ecommerce Data Services Charge
A managed web scraping service usually charges by scope rather than by request. Three models are common:
Subscription by products, websites and frequency. You pick a plan that fits your number of stores and products, and the price depends on how often you collect.
Per website, per refresh. ScrapeHero's Business plan, for example, starts at $199 per website per month plus a one-time setup fee.
Project contracts. Large or unusual projects are quoted individually, often with setup fees.
Here is how this looks for managed ecommerce data collection with ShopScraping:
Plan | Limits | Monthly | Weekly | Daily |
|---|---|---|---|---|
Starter | 3 websites, 5,000 products | $20/mo | $30/mo | $60/mo |
Standard | 5 websites, 30,000 products | $75/mo | $115/mo | $225/mo |
Professional | 15 websites, 100,000 products | $150/mo | $225/mo | $450/mo |
One-off (no subscription) | 1 website per order | $10 for the first 500 products; $20 for 5,000 products | — | — |
Each product variant, such as a size or a color, counts as one product toward the plan limit. Product variants, marketplace seller data, highly protected websites, image downloading and custom data transformations are available on request. Prices exclude VAT; see ShopScraping plans for current terms.
The Hidden Costs of a Scraping API
Most guides to the cost of web scraping stop at the pricing page. With an API, the larger part of the bill is usually work your team does around it. Here is where it goes and how to estimate each item.
1. Parsing. Outside the vendor's list of supported sites, the API returns raw pages. A developer writes extraction rules for each store: where the price is, which element holds the sale price, how stock status is shown, where the SKU and GTIN live. Estimate: hours per store multiplied by the number of stores.
2. Rendering and protection. Many stores load prices and stock with JavaScript or sit behind bot protection. Those requests fall into the expensive bands in the table above. Estimate: test your three hardest stores before you commit, and price them at the rendered rate.
3. Requests that are not products. To collect a category, you also fetch listing pages, follow pagination, retry failures and sometimes request each variant separately. You pay for requests, not for products. Estimate: add 5–20% to your product count, more if variants need their own requests.
4. Maintenance. Stores change templates, run A/B tests and redesign for seasonal sales. A broken parser often does not crash; it keeps running and returns empty or wrong fields. This kind of silent failure is one of the main reasons why stores fight scrapers and why scraping got harder. Estimate: hours per store per month.
5. Quality checks. Someone has to compare the output with live pages regularly, or bad data reaches your pricing decisions. Estimate: a few hours a month.
6. Scheduling, storage and reruns. Runs need to be scheduled, monitored and repeated when they fail, and the results need a place to live. Estimate: small if you already run data pipelines, significant if you do not.
7. Matching products across stores. Linking a competitor's listing to your own SKU stays on your side in both models, and it is the hardest part of comparing prices (see product matching). The difference is that a managed service hands you normalized fields to match on; with an API, normalizing currencies, units and identifiers is your work too.
The Hidden Costs of a Managed Service
A managed service has its own trade-offs, and you should weigh them as carefully:
Plan limits. You pay for a number of websites and products. With ShopScraping that is 3, 5 or 15 websites, depending on the plan.
Variants use up the limit. A catalog of 5,000 models in four sizes each counts as 20,000 products.
Frequency costs more. On ShopScraping's Standard and Professional plans, daily collection costs three times as much as monthly.
Some things are on request. Variants, marketplace seller data and highly protected websites are set up on request rather than by default.
Less control. You cannot change the extraction logic yourself; new fields and stores go through the provider.
Analysis is still yours. ShopScraping delivers data, not a dashboard: there are no alerts or run-to-run comparisons, and product matching happens on your side.
When a store changes its layout, ShopScraping fixes the extraction. That is the core of what you pay for.
Total Cost of Ownership: 2 Ecommerce Scenarios
So how much does web scraping cost once everything is included? Here is the math for two common ecommerce setups.
Our assumptions. Replace these with your own numbers:
Developer rate: $60–100 per hour.
Setting up one store: 4–12 hours, spread over 12 months.
Maintaining one store: 1–4 hours a month.
Quality checks: 2–4 hours a month in total.
Prices: public pricing pages on the dates above.
The formula:
Scraping API monthly cost = usage fee + (setup hours ÷ 12 + maintenance hours + QA hours) × hourly rate
Managed service monthly cost = plan price
Your own analysis time is the same in both models, so we leave it out.
Scenario A: 3 competitor stores, 5,000 products, weekly
A small pricing or category team, or one of many small sellers looking for an affordable ecommerce scraping API. That is about 21,700 product records a month.
Scraping API route | Managed service route | |
|---|---|---|
Usage or plan fee | $16–50/mo | $30/mo |
Setup | 1–3 hours/mo | None |
Maintenance and QA | 5–16 hours/mo | None for collection |
Estimated monthly total | About $375–1,950/mo | $30/mo |
At this size, the price of the API barely matters: developer time is 90% or more of the cost. If one snapshot a month is enough, the managed side drops to $20 for the Starter plan, or $20 per store for a one-off collection of 5,000 products. If you only care about prices, see price scraping on a schedule. For a line-by-line comparison of ten tools in this same scenario, see our per-tool cost table.
One caveat: if your competitors sell many sizes and colors, the 5,000-product limit fills faster, because each variant counts as a product.
Scenario B: 5 competitor stores, 30,000 products, daily
A growing retailer that reprices daily. That is about 900,000 product records a month.
Scraping API route | Managed service route | |
|---|---|---|
Usage or plan fee | $675–1,350/mo | $225/mo |
Setup | 2–5 hours/mo | None |
Maintenance and QA | 7–24 hours/mo | None for collection |
Estimated monthly total | About $1,200–4,250/mo | $225/mo |
At daily frequency the gap is no longer only about developer time: the usage fee alone is three to six times the managed plan. And if the stores need a real browser, difficulty-based pricing can climb much higher; at Zyte's published rendered rates, the same 900,000 requests would cost $909–14,472 a month. Weekly collection on Standard costs $115 a month. If the stores have many variants, 30,000 products may not be enough, and the next step is Professional at $450 a month for daily collection.
These estimates are based on public pricing on November 16–18, 2026 and the assumptions above. Real costs depend on the target sites, rendering needs, volume discounts and your team's rates.
Which One Fits Your Team?
Choose a scraping API if:
you have developers and an existing data pipeline;
you collect hundreds of thousands to millions of pages, so volume discounts apply;
most of your data comes from one or two large sites that the vendor already parses;
you need collection several times a day, or extraction logic no service offers.
Choose a managed service if:
nobody on your team has time to build and maintain parsers;
you collect from many stores built on different platforms;
daily, weekly or monthly collection is enough;
you want normalized product fields and a bill you can predict.
There is also a middle option: a managed service that delivers over API. The data flows into your systems the same way it would from a scraping API, but without parsers to maintain. Teams usually choose this when they have developers who would rather work on the product than on scrapers.
6 Pricing Questions to Ask Before You Commit
Ask these before you sign, whichever model you choose:
What is the billing unit: a request, a successful result, a record or a product?
Do failed and retried requests count?
How much more do browser rendering and protected sites cost?
Are category and pagination pages included, or billed separately?
What happens when you hit the limit: the job stops, you pay overage, or you move up a plan?
What will twice the volume cost?
FAQ
- How much does web scraping cost?
It depends on the model. Scraping APIs cost from a few dollars to hundreds of dollars a month in usage, plus the developer time to parse and maintain each site. Managed services start at around $20–30 a month for small scopes and go up to custom contracts. A one-off collection of 5,000 products from one store costs $20 with ShopScraping. See the two scenarios above for full monthly totals.
- Is a scraping API cheaper than a managed service?
Per request, yes. Per usable product record, usually not, once you count developer time, at least for small and medium scopes. An API can be cheaper at very large volumes on a few sites that the vendor already parses, if you have a team to run the pipeline.
- What is a managed web scraping service?
A managed web scraping service runs the whole collection for you. You choose the stores, fields and schedule; the service collects the data, handles blocks and layout changes, checks the output and delivers finished records by file or API.
- Do scraping APIs charge for failed requests?
It depends on the vendor. Some charge only for successful requests or results; Scrape.do and Oxylabs both say so on their pricing pages. Others count every attempt. Check this before you compare headline prices.
- Do product variants count toward the limit?
With ShopScraping, yes: each variant, such as a size or a color, counts as one product. With a scraping API, each variant often needs its own request, so variants raise the bill there too.
- Can I get data from a managed service by API?
Yes, with many providers. ShopScraping includes API delivery on every plan, alongside CSV, Excel, JSON and import-ready Shopify and WooCommerce files.
- How much does real-time ecommerce scraping cost?
Collection frequency multiplies the cost: daily is about 30 runs a month, hourly about 720. With an API, multiply your monthly requests by the frequency and use the formula above. ShopScraping offers daily, weekly and monthly schedules; other frequencies are available on request.
Check the Managed Side of the Math
Want to see what the managed route gives you on your own competitors? Run a free demo on any product URL, then compare the plan price with your API estimate. When you are ready, start collecting data from $20 a month.