switch402

ZenRows Credits Explained (2026): Why One Request Costs 1, 5, 10 or 25 Credits

ZenRows plans are sold in monthly credits, and one request is not always one credit. Per ZenRows' pricing page (checked Nov 2, 2026), a standard page costs 1 credit, JavaScript rendering 5, premium proxies 10 and both together 25, so the same page can cost 1, 5, 10 or 25 credits. Plans start at $19 a month (Build, 45,000 credits, monthly billing), credits refresh monthly with no rollover, and failed requests are never charged. Here is what each request type costs, and how switch402 differs: you pay only for the pages you actually fetch.

  • A standard page is 1 credit

    Per ZenRows' pricing page, one credit is a standard successful page. JavaScript rendering costs 5 credits, premium proxies 10, and both together 25. With Adaptive Stealth Mode (mode=auto), ZenRows starts with the lightest setup and bills only the setup that worked.

  • Bandwidth and browser time

    Residential bandwidth draws a flat 25,000 credits per GB, and the Browser product bills bandwidth plus 5 credits per minute of session time. Every product draws from the same credit balance.

  • Credits refresh monthly

    Plan credits refresh each month with no rollover. On a paid plan you can buy top-ups up to ten times per billing period; unused top-up credits roll into the next period once, then expire. The Free plan has no top-ups.

  • Failed requests are free

    ZenRows says it never charges failed requests. A 404 or 410 response counts as a successful result and is charged.

ZenRows credits per request and what Build ($19, 45,000 credits) covers, as of Nov 2, 2026

ZenRows request typeCredits per requestRequests Build covers per month
Standard page145,000
With JavaScript rendering59,000
With premium proxies104,500
JavaScript rendering and premium proxies251,800
Residential bandwidth25,000 per GBAbout 1.8 GB
Browser session5 per minute, plus bandwidth9,000 minutes

Plan sizes with monthly billing: Build $19 (45,000 credits), $29 (80,000) or $39 (120,000); Launch $69 (250,000), $99 (500,000) or $129 (700,000); Growth $199 (1,200,000), $279 (2,000,000) or $399 (3,000,000); Scale $549 (5,000,000) up to $2,999 (45,000,000). Annual billing gives two months free (Build from $16 a month). The plan price is the same whatever share you use, so what you pay per request is the plan price divided by the requests you actually make that month. Honestly: if you use most of your credits, ZenRows costs less per page than switch402; on Build, switch402 at $0.008 a page costs less only up to 2,374 pages a month. switch402 has no credits or multipliers: $0.008 per successful page on /v1/scrape and $0.003 on /v1/scrape/lite, and a month with no calls costs $0.

Sources, checked Nov 2, 2026: zenrows.com/pricing. Prices can change; check the source before you decide.

Example: 1,000 pages with JavaScript rendering use 5,000 of Build's 45,000 credits, and the plan still costs $19, about $0.019 per page used. The same 1,000 pages on switch402 cost $8 ($3 on lite), and a month with no calls costs $0.

Code example

Before: ZenRows, a JavaScript-rendered request (5 credits, curl)

curl "https://api.zenrows.com/v1/?apikey=$ZENROWS_API_KEY&url=https%3A%2F%2Fexample.com&js_render=true"
# add premium_proxy=true and the same request costs 25 credits

After: switch402, one flat price 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() // $0.008, charged only on success

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.
How much does ZenRows cost?
As of Nov 2, 2026, per zenrows.com/pricing with monthly billing: Build $19 to $39 (45,000 to 120,000 credits), Launch $69 to $129 (250,000 to 700,000), Growth $199 to $399 (1,200,000 to 3,000,000) and Scale $549 to $2,999 (5,000,000 to 45,000,000); Enterprise is custom. Annual billing gives two months free. The Free plan is 5,000 credits a month with no card.
How many credits does a ZenRows request use?
Per its pricing page: 1 credit for a standard page, 5 with JavaScript rendering, 10 with premium proxies and 25 with both. Residential bandwidth is 25,000 credits per GB, and Browser sessions cost 5 credits a minute plus bandwidth.
Do ZenRows credits roll over?
Plan credits refresh monthly with no rollover. Top-up credits, bought on a paid plan up to ten times per period, roll into the next period once and then expire.
Does ZenRows charge failed requests?
No, per its pricing page failed requests are never charged; a 404 or 410 counts as a result and is charged. switch402 also charges only on success.
Is ZenRows cheaper than switch402?
At steady volume, yes. Build covers 45,000 standard pages for $19, so if you use most of it a page costs well under switch402's $0.008. switch402 costs less when you use fewer pages than the plan price divided by $0.008 (up to 2,374 pages a month on Build) or when your volume is uneven, since a month with no calls costs $0. ZenRows also offers JavaScript rendering, premium and residential proxies, a browser, crawling and extraction, which switch402 does not sell as options.
Where do these numbers come from?
ZenRows' pricing page (plans, credits per request, rollover, top-ups and failed-request policy), fetched Nov 2, 2026, plus switch402's live payment terms. Prices can change; check the source before you decide.

Next steps