Skip to main content
Zenrows offers transparent, credit-based pricing for every technical level and scraping volume. Every plan includes all four Zenrows primitives: Fetch, Extract, Batch, and Browser Sessions, over all four interfaces: API, SDK, CLI, and MCP. Nothing is segmented by product or interface: what scales with your plan is your monthly credit allowance, concurrency, and support level.

​
How Pricing Works

​
Shared Credit Balance

Each plan gives you a monthly credit allowance that you spend across every Zenrows product from one shared balance. There’s no separate limit per product.

​
Pay Only for Success

You’re charged only for successful requests. Failed or retried requests don’t consume your balance. HTTP 404 and 410 responses count as successful because the request completed correctly and returned valid data.

​
Cost Multipliers for Fetch

Different features multiply your base credit cost depending on the infrastructure required:
These credit weights are fixed and never change. A JavaScript-rendered request always costs 5 credits, a protected request always costs 25, on every plan. What changes between plans is how many credits you get each month, not what anything costs to run.

​
Residential Proxies and Browser Sessions

Residential Proxies, used standalone, meter at a flat 25,000 credits per GB on every plan. Browser Sessions bill on bandwidth (the same 25,000 credits/GB) plus a flat 5 credits per minute of session time. Everything runs off the same shared balance.
Rule of thumb: 1 GB = 25,000 credits = 1,000 protected pages.

​
Plan Comparison

GB max = the maximum Residential Proxies/Browser Sessions bandwidth if you spent your entire monthly allowance on it alone (credits ÷ 25,000).
Every higher rung gives you more credits for your money. The credit weights themselves never change (see Cost Multipliers for Fetch above). A standard request is always 1 credit and a protected request is always 25, on every plan. What changes as you move up is how many credits you have to spend, not what anything costs to run.
Enterprise plans offer custom credit pricing beyond Scale S3. Contact our sales team if your usage exceeds 12.5M credits/month.

​
Top-Up Packs

Sized so one pack comfortably covers a shortfall and two packs are enough to make an upgrade the better deal. Up to 4 top-ups per billing period; unused top-up credits roll into the next period.
Free doesn’t include top-ups. If you run out of credits on Free, wait for the next monthly refresh or upgrade to a paid plan.

​
Concurrency, Support, and Rollover

Concurrency and support scale by tier, not by rung: moving up a rung within a tier buys more monthly credits, moving to a new tier buys more capability.
Concurrent requests = how many pages you can scrape simultaneously. Higher concurrency enables faster data extraction. Rollover = unused monthly plan credits carry into the next billing period, once.

​
Credit Calculation Examples

​
Fetch and Extract

  • Available requests = Plan credits ÷ credits per request (1 for standard, 5 for JavaScript rendering, 10 for Premium Proxies, 25 for protected)
  • Extract runs through the same Fetch client and draws credits the same way: add extract=auto to a request and it draws exactly what the underlying Fetch call would.

​
Batch

  • Billed identically to Fetch: per successful task, using the same credit weights.

​
Browser Sessions

  • Total credits = (GB used × 25,000) + (session minutes × 5)

​
Residential Proxies (Legacy)

  • Total credits = GB used × 25,000
Remember: you pay only for successful requests across all products.

​
Choose Your Plan

  1. Estimate your monthly volume: how many standard vs. protected pages will you scrape?
  2. Add Browser Sessions or standalone Residential Proxies usage: estimate the GB and session minutes you’ll need.
  3. Match your total against the plan table above, with some buffer room for growth.

​
Managing Your Subscription

Access all subscription changes from your Plans or Billing pages.

​
Top-Ups

You’ll receive usage alerts at 80% and 95% of your limit, if enabled from your Notifications settings. Top-ups let you add credits without changing plans. See the pack prices for your rung in the Top-Up Packs table above.
  • Limit: up to 4 top-ups per billing period
  • Rollover: unused top-up credits roll into the next period
Set automatic top-ups to trigger at your chosen threshold (like 95%). To avoid surprises, enable invoice notifications in your Notification Settings.

​
Upgrading Your Plan

When you upgrade your plan, the change takes effect immediately. Here’s what happens to your credits and limits:
  • When it applies: Immediately after purchase
  • Credit carry-over: Any unused credits from your current plan, including base plan credits, top-ups, and any admin-granted credits, automatically carry over to your new plan. This carried-over amount is added on top of your new plan’s allowance as bonus credits, giving you extra usage from day one.
  • Top-up limits reset: The carried-over bonus credits don’t count against your new plan’s top-up purchase limit. You start the new billing period fresh and can purchase top-ups as usual.
Example: If you’re on Launch L1 (250,000 credits/month) with 90,000 unused credits and upgrade to Launch L3 (700,000 credits/month), your new billing period starts with 700,000 + 90,000 = 790,000 available credits.

​
Downgrading Your Plan

  • When it applies: At the end of your current billing cycle
  • During transition: You keep your current limits until renewal

​
Cancelling Your Subscription

1

How to cancel

  1. Go to Billing
  2. Click Cancel Subscription
  3. Select your reason for cancelling (your feedback helps us improve!)
  4. Confirm to complete the cancellation
2

After cancellation

  1. You keep access until your billing cycle ends
  2. You can use your remaining credits during this time
  3. No additional charges will occur
For complete terms and conditions, visit our Terms & Conditions page.

​
Frequently Asked Questions (FAQ)

Each plan includes a monthly allowance of credits, so you’re not counting dollars per call. One credit is a standard successful page. Harder work draws more from the same balance: JavaScript rendering costs 5 credits, Premium Proxies 10, and both together (protected) 25. Residential Proxies, used standalone, draw 25,000 credits per GB. Browser Sessions bill on bandwidth plus session time: 5 credits per minute, all in credits. Every plan runs off one balance.
No. Your plan’s credit allowance applies to all products from one shared balance, not allocated separately to each one. For example, on Launch L1 (250,000 credits/month), you could spend 150,000 credits on Fetch and 100,000 on Browser Sessions in the same month.
We accept credit cards (Visa, MasterCard, American Express, etc.), Apple Pay, Google Pay and PayPal. Wire transfer is accepted for Enterprise customers. We don’t accept crypto or debit cards at the moment.
Never. You only spend credits on successful requests. 404 Not Found and 410 Gone responses count as successful results.
Yes. Paying yearly gives you two months free (pay for 10, get 12) and your full year’s credit allowance up front, as a single balance you draw down anytime over the year rather than monthly grants. Enterprise is priced on committed volume.
We warn you before you reach it. On a paid plan, you can add extra credits (top-ups) any time to keep running, up to four times per billing period, and unused top-up credits roll into the next period. On Free, there are no top-ups: wait for the next monthly refresh or upgrade. Either way, no lost data or configuration.
Yes. Upgrades take effect immediately, billing adjusted accordingly, with unused credits carried over as bonus credits on your new plan. Downgrades take effect at the end of the current billing cycle. No penalties, no hidden fees.
Concurrency is how many requests run at the same time. The limit scales with your plan tier (see the Concurrency, Support, and Rollover table above), so larger plans run more jobs in parallel. See our concurrency guide for implementation details.
Same primitives, same API. Set the protection level (or let Adaptive Stealth Mode, mode=auto, choose it for you) and Zenrows routes through the right stack (residential network, fingerprinting, retries), so your code doesn’t change between an open page and a hard-protected one.
Not as a standalone option today. The Free plan (5,000 credits/month, no card required) covers light, ongoing use without a subscription.
Custom plans are available for usage beyond Scale S3 ($999/month, 12.5M credits/month). See the Enterprise row in the Plan Comparison table above. We don’t offer the option to purchase additional concurrency separately or to subscribe to a plan for just one product at a lower price: every plan includes all four products and all four interfaces, with limits determined by your selected plan.
No, pausing or delaying your subscription isn’t currently available. You can keep your subscription active or cancel it at any time. If you cancel, you keep access to all services until the end of your current billing cycle. Unused days or credits don’t roll over if you reactivate a cancelled subscription later.
You can view and download your subscription invoices on your Billing page.
It’s not currently possible to update information on past invoices. To ensure your future invoices have the correct details, keep your profile information up to date in your Account Settings and your payment methods on the Billing page. Changes apply to your next invoice onward.
Yes. The Agent Toolkit ships an MCP server, a CLI, and SDKs that connect to Claude Code, Cursor, Codex, Windsurf, Gemini CLI, and any MCP-compatible client. Every primitive is exposed as a tool, so agents call them natively with auth and usage visibility built in. This is included on every plan, not a separate add-on.
Yes, on Enterprise: an SLA on uptime and success rate, SOC 2 and ISO 27001 compliance, SSO/SAML, dedicated account management, a solutions engineer, and quarterly business reviews (QBRs).