ScrapingBee vs ZenRows Pricing (2026): Plain, JavaScript and Premium Requests per 1,000
Short answer: ScrapingBee and ZenRows charge the same credits per request type: 1 for a plain page, 5 with JavaScript rendering, 10 with premium proxies and 25 with both. So the plan price per credit decides. Per scrapingbee.com/pricing and zenrows.com/pricing (checked Nov 8, 2026, monthly billing), ScrapingBee Hobby is $19 for 75,000 credits and ZenRows' entry plan is $19 for 45,000, so ScrapingBee costs less per request when the plan is fully used. ZenRows has the larger free tier (5,000 credits every month, no card; ScrapingBee gives 1,000 free credits at signup), and only ScrapingBee sells a 75-credit stealth proxy tier. switch402 has no plan: $0.008 per successful page ($8 per 1,000, or $3 on lite), which is more than either plan at full use and less only at low or uneven volume.
See also: ScrapingBee credits explained · ZenRows credits explained · ScraperAPI vs ScrapingBee pricing
- Same credit multipliers
Both bill 1 credit for a plain request, 5 with JavaScript rendering, 10 with premium proxies and 25 with JavaScript plus premium proxies. ScrapingBee renders JavaScript by default, so a request costs 5 credits unless you send render_js=false; ScrapingBee stealth proxies cost 75.
- Different credit prices
ScrapingBee: Hobby $19 for 75,000 credits, Freelance $49 for 250,000, Startup $99 for 1,000,000, Business $249 for 3,000,000. ZenRows (entry step of each plan, monthly): $19 for 45,000, $69 for 250,000, $199 for 1,200,000 and $549 for 5,000,000; annual billing is pay 10 months, get 12.
- Free tiers and unused credits
ZenRows Free is 5,000 credits a month with no card. ScrapingBee gives 1,000 free credits at signup. Plan credits on both last one month and do not roll over; ZenRows top-up credits on paid plans roll over once.
- What gets charged
ScrapingBee charges successful requests; Auto-Mode bills only the tier that worked (1, 5, 10, 25 or 75) and max_cost caps it. ZenRows never charges failed requests but counts 404 and 410 responses as results; residential bandwidth is 25,000 credits per GB and its Browser product 5 credits a minute.
Cost per 1,000 successful requests if every plan credit is used (monthly billing, Nov 8, 2026)
| Request type (credits) | ScrapingBee Hobby $19 / 75K | ScrapingBee Startup $99 / 1M | ZenRows $19 / 45K | ZenRows $69 / 250K | ZenRows $199 / 1.2M |
|---|---|---|---|---|---|
| Plain page (1) | $0.25 | $0.10 | $0.42 | $0.28 | $0.17 |
| JavaScript rendering (5) | $1.27 | $0.50 | $2.11 | $1.38 | $0.83 |
| Premium proxies, no JavaScript (10) | $2.53 | $0.99 | $4.22 | $2.76 | $1.66 |
| Premium proxies + JavaScript (25) | $6.33 | $2.48 | $10.56 | $6.90 | $4.15 |
| Stealth proxy (75, ScrapingBee only) | $19.00 | $7.43 | Not offered | Not offered | Not offered |
These rates assume every credit in the plan is used that month. Use fewer and the real rate rises, because the plan price is fixed: 1,000 plain requests still cost $19 on either entry plan. switch402 is $8 per 1,000 pages on /v1/scrape and $3 on /v1/scrape/lite, whatever the page, but it has no premium, stealth or anti-bot proxy tier, so it only compares with the plain and JavaScript rows. Break-even vs switch402's $0.008: either $19 plan at 2,375 requests a month, whatever the tier. Below that, or in months a plan sits unused, switch402 costs less; above it, a filled plan costs less.
Sources, checked Nov 8, 2026: scrapingbee.com/pricing, scrapingbee.com/documentation, zenrows.com/pricing. Prices can change; check the source before you decide.
Example: 3,000 JavaScript-rendered pages in a month. ScrapingBee Hobby covers 15,000 such requests and ZenRows $19 covers 9,000, so both cost $19 (about $0.0063 per page used). switch402 costs $24 ($9 on lite, which returns markdown). At 1,000 pages ZenRows Free (5,000 credits = 1,000 JavaScript pages) costs $0.
Code example
ScrapingBee: 1-credit request with JavaScript off (curl)
curl "https://app.scrapingbee.com/api/v1?url=https%3A%2F%2Fexample.com&render_js=false" \
-H "Authorization: Bearer $SCRAPINGBEE_API_KEY"
# leave out render_js=false and the same call costs 5 creditsZenRows: standard request, 1 credit (curl)
curl "https://api.zenrows.com/v1/?apikey=$ZENROWS_API_KEY&url=https%3A%2F%2Fexample.com"
# js_render=true 5 credits, premium_proxy=true 10, both 25switch402: flat $0.008 per successful page (JavaScript)
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPaymentFromConfig } from '@x402/fetch'
import { ExactEvmScheme } from '@x402/evm'
import { privateKeyToAccount } from 'viem/accounts'
const account = privateKeyToAccount(process.env.AGENT_KEY)
const fetchWithPayment = wrapFetchWithPaymentFromConfig(fetch, {
schemes: [{ network: 'eip155:8453', client: new ExactEvmScheme(account) }],
})
const res = await fetchWithPayment('https://api.switch402.com/v1/scrape', {
method: 'POST',
headers: { 'Content-Type': 'application/json', 'User-Agent': 'my-agent/1.0' },
body: JSON.stringify({ url: 'https://example.com' }),
})
const { markdown } = await res.json()FAQ
- Is switch402 live?
- Yes. POST https://api.switch402.com/v1/scrape with {"url": "..."} returns the page as markdown for $0.008 USDC on Base per call, paid over x402 and charged only on success. A lower-cost endpoint, /v1/scrape/lite, is $0.003 per call.
- Is ScrapingBee cheaper than ZenRows?
- Per credit on the entry plans, yes: $19 buys 75,000 ScrapingBee credits vs 45,000 on ZenRows, and the credit cost per request type is the same. At $99, ScrapingBee Startup's 1,000,000 credits also cost less per credit than ZenRows' $69 (250,000) or $199 (1,200,000) steps. ZenRows' free tier is larger and recurring (5,000 credits a month vs 1,000 at ScrapingBee signup).
- Do the credit multipliers differ?
- Not for the four shared tiers: plain 1, JavaScript 5, premium proxies 10, JavaScript plus premium 25 on both. ScrapingBee adds a stealth proxy tier at 75 credits and renders JavaScript by default. ZenRows bills residential bandwidth at 25,000 credits per GB and its Browser product at 5 credits a minute.
- Do unused credits roll over?
- Plan credits do not roll over on either. ScrapingBee credits are valid for one month. ZenRows plan credits refresh monthly; top-up credits bought on a paid plan roll into the next period once, then expire.
- When does switch402 cost less?
- Below about 2,375 requests a month against either $19 plan, or in any month you would pay a plan and barely use it. Above that, a filled plan costs less per request than $0.008. switch402 has no premium or stealth proxies, so it is not a substitute for sites that need them; its trade is no signup, API key, plan or unused credits.
- Where do these numbers come from?
- ScrapingBee's pricing page and API documentation (plans, credit costs, Auto-Mode, stealth proxies) and ZenRows' pricing page (plans, credit costs, free tier, top-ups), all fetched Nov 8, 2026, plus switch402's live payment terms. Prices can change; check the sources before you decide.
Next steps
- API docs and migration snippets
- Pricing calculators
- Firecrawl pricing calculator
- ScrapingBee pricing calculator
- ZenRows pricing calculator
- Use cases
- Firecrawl alternatives, priced
- Firecrawl vs Exa pricing
- Scraping API pricing compared
- Firecrawl credits expired?
- Pay-as-you-go scraping API
- ScrapingBee credits explained
- Firecrawl pricing explained
- ScraperAPI credits explained
- ZenRows credits explained
- Tavily credits explained
- Firecrawl vs Jina Reader pricing
- Diffbot pricing explained
- Jina Reader pricing explained
- Scrapfly credits explained
- Scraping API without an API key
- Pay for MCP tool calls (x402)
- x402 gas fees and USDC on Base
- Credits vs pay per call
- SerpAPI credits explained
- Exa vs Tavily pricing
- Firecrawl vs Tavily pricing
- SerpAPI vs Tavily pricing
- Apify credits explained
- ScraperAPI vs ScrapingBee pricing
- Firecrawl vs ScraperAPI pricing
- Bright Data credits explained
- ScreenshotOne pricing explained
- Tavily alternatives, priced
- ScraperAPI alternatives, priced
- Exa pricing explained
- ScrapingBee alternatives, priced
- SerpAPI alternatives, priced