Skip to content

Netnut alternative for web scraping: a simpler API option

If proxy setup and unpredictable usage charges are slowing your scraping work, this page compares a query-based API approach with a bandwidth-based proxy model.

OUTPUT FORMATSHTMLJSONMarkdown

It explains the billing distinction, the main browser features, and the plan controls to check before you switch.

Billing: queries and successful requests, not bytes

The two models count usage differently, and that difference drives most of the cost risk. A bandwidth-metered service tallies the data that moves through it, so a request that fails still consumes budget. A query-metered API instead counts the requests you make, and the page states that only successful requests are charged, with no bandwidth ceiling to monitor. For planning, that means you forecast successful calls rather than total traffic: estimate how many pages you need, then multiply by the credit cost of the features each call uses. Failed attempts do not silently inflate the estimate. A practical way to size the budget: list the pages you need, tag each one with the features it requires (plain fetch, JavaScript rendering, premium proxies), and total the credits per bucket before comparing against a bandwidth quote.

A like-for-like comparison snapshot

In a dated unverified comparison captured for this page, a 10,000-request monthly example was shown with Chrome headless enabled. The alternative side listed 1 credit per request, 100k+ IPs and unlimited bandwidth, while the Netnut side listed 0.3 MB per request, 40k IPs and $0.5/GB, with a $50 figure shown for Netnut and a contact-us figure for the alternative. Treat those rival figures as a snapshot to re-check, not as a current quote. Use the checklist below to compare like with like.

Decision checklist

Before switching, check: 1) Whether you pay per successful request or per byte. 2) How many credits a request costs with JavaScript rendering and with premium proxies. 3) Whether credits expire monthly without rollover. 4) Your concurrent-request limit. 5) Whether geotargeting, screenshots, extraction rules, dedicated APIs, priority support, account management, and team management are included on your tier. 6) Whether prices exclude VAT and whether cancellation is allowed at any time.

Simpler setup through a REST API

The workflow is short: hand over a URL to a real-time REST API and let the service handle fetching and delivery. The proxy decisions that usually sit in front of a scrape — which region to exit from, which proxy class to use, and which IPs to allow — are handled inside the request rather than in a separate control panel. Teams that must keep using conventional proxies can switch to a proxy mode that presents the API like any other proxy provider. Smart routing is described as selecting suitable proxies to support a 98% performance rate.

Browser handling without your own fleet

Rendering is the provider's job, so you avoid running headless browsers yourself — no containers to babysit and no memory leaks to chase. Browsers are described as keeping a low profile to reduce CAPTCHAs. When a page needs interaction, you can run custom JavaScript inside the browser for endless scrolling, button clicks, or closing popups. Budget for it: the plan-control notes state that a successful request with JavaScript rendering costs 5 credits, and premium proxies cost 10 or 25 credits depending on JavaScript rendering. So a 1,000-call job that needs rendering and premium proxies could consume 25,000 credits, while the same job on plain requests would cost 1,000. Decide per target site whether rendering is actually required: static HTML pages rarely need it, and reserving the 5-credit path for pages that build content client-side keeps the monthly total predictable.

Documentation, samples, and support

Documentation is presented as a quick start, with a knowledge base covering frequent use cases and code samples. Samples are listed for Java, Python, Go, PHP, curl, and JavaScript. Support is described via live chat and email, with priority email support, a dedicated account manager, and team management appearing on higher tiers in the plan list.

Plans: credits, concurrency, and tiered extras

Plans are organised by monthly API credits and concurrent requests, with JavaScript rendering, rotating and premium proxies, geotargeting, screenshots and extraction rules, and dedicated scraping APIs listed as included across the tiers shown. Priority email support, a dedicated account manager, and team management appear only on higher tiers. Before committing, verify the current pricing, inclusions, and starting price directly with the provider, since published figures can change. If you need more monthly credits or higher concurrency, the page directs readers to talk to a product expert. A free API credit trial is described on the page; check the provider's current offer terms before relying on it.

Customer feedback

Customer example worksheet

Record a customer example you can verify. Leave unknown fields blank until you have supporting evidence.

FieldYour details
Customer and permission to use the example________
Problem and starting point________
Configuration or actions________
Measurement period________
Outcome and supporting evidence________
Approval to publish________
Plan control map
ControlWhat it tells youWhy it matters
API creditsValid for one month, no rollover; requests start at 1 credit eachMonthly budget depends on successful requests, not total attempts
Concurrent requestsHow many requests can be sent at the same timeSets throughput ceiling for parallel scraping
JavaScript rendering5 credits per successful request with JS rendering enabledRendering multiplies credit use versus plain requests
Premium proxies10 or 25 credits depending on JS renderingPremium routing is the most expensive credit multiplier
Geotargeting200+ countries and territories; 40+ on classic proxiesCheck coverage for your target markets
Screenshots and extractionFull-page screenshots; structured data via CSS or XPath rulesDetermines whether extra tooling is needed
Dedicated scraping APIsGoogle, Fast Search, Amazon, Walmart, ChatGPT, Gemini, YouTube, Employee SearchPre-built endpoints may replace custom parsing
Team managementInvite users and assign custom credit/concurrency quotasRelevant only on higher tiers

Credit costs and expiry are from plan-control notes; confirm current values with the provider before relying on them.

Frequently asked questions

How is usage billed?

Billing is described as monthly, based on the number of queries made, with unlimited bandwidth rather than a per-byte charge. The page also states that only successful requests are charged, unlike a model where failed responses still count toward usage.

Do I need to configure proxies manually?

The workflow is a single API request supplying a URL, without separate setup for proxy areas, proxy type, or IP whitelisting. A proxy mode is also described for teams that prefer to work through regular proxies.

What browser and routing features are included?

Features described include smart routing to select suitable proxies, JavaScript rendering handled by the provider, low-profile browser behaviour intended to reduce CAPTCHAs, and custom JavaScript execution for actions such as scrolling, clicking, or closing popups.

What documentation and support are available?

Documentation, a knowledge base with code samples, and support by live chat or email are described. Code samples are listed for Java, Python, Go, PHP, curl, and JavaScript.

How should I choose between plans?

Plan details vary by API credits, concurrent requests, and included features. Credits are described as valid for one month without rollover, starting at 1 credit per request, with higher costs for JavaScript rendering and premium proxies. Confirm the provider's current plan details and pricing before choosing.