Rotating Proxy

API credits are the internal billing units used to measure how much load your requests generate. Every plan comes with a fixed number of credits, and every outgoing request deducts a certain amount based on how complex the target webpage is.

A simple request that loads only HTML or JSON typically costs 1 credit. Requests that trigger multiple parallel assets — such as scripts, images, CSS files, fonts, APIs, and tracking requests — consume more credits. Each asset counts as a separate downstream request.

These numbers are approximate and vary per website:

• 1 credit — simple API-style request, no browser, no JS
• 2–3 credits — no-JS browser request (basic DOM, no rendering)
• ≈10 credits — full headless browser with JS rendering, typical DC proxy load
• 10–15+ credits — heavy pages with many scripts, trackers, ads, analytics, or large asset bundles

Different websites have different DOM structures, JS bundles, and asset chains. One site may load only a few files; another may trigger 30+ downstream requests per page.

How to calculate your real consumption? You can easily estimate credit usage before committing to a plan:

• Open the page you want to scrape.
• Check how many parallel requests it makes using a tool like RequestMap
• The number of loaded assets ≈ number of credits per page load.

This gives you an accurate prediction of how many API credits your workflow will consume. Any request that reaches our infrastructure consumes credits — including responses like 404, 429, 503, or timeouts. Even though the target site returned an error, we still processed and routed the request.

The paid 48-hour option is available for non-rotating proxy products. Choose a standard term for rotating proxies.

Rotating proxies give you a new IP on every request, making it far harder for websites to block or rate-limit you. Combined with realistic headers and user-agents, they help bypass WAFs and CAPTCHA challenges while keeping your scraping sessions stable. Add unlimited bandwidth, unlimited concurrency, and a worldwide IP pool — and you get an enterprise-grade scraping API at a fraction of the market price.

You connect to a single FineProxy gateway — one domain and one port. When your application sends a request, the gateway selects an IP from the pool of ~100,000 addresses and forwards the request through it. The next request gets a different IP automatically. You don't manage any proxy lists or rotation logic — the gateway handles everything.

Every HTTP request that reaches our infrastructure consumes credits — including requests that return errors such as 404 or 503. A single page load may generate multiple downstream requests (scripts, images, fonts), and each of those counts individually.

Your plan is valid for 30 days or until you use all API credits — whichever happens first. Unused credits do not carry over to the next billing cycle.

Yes. In your dashboard, each active plan has a dedicated page showing your API credit usage, request history, and consumption patterns.

You can lower usage by reducing the number of assets loaded during each request. Techniques include:

• using accept-encoding: gzip, deflate, br to shrink payload size
• avoiding headless browser rendering unless necessary
• disabling images, fonts, and heavy JS where possible
• using simpler request modes for API endpoints

In general, fewer parallel assets = fewer consumed credits.

Currently, our rotating proxies assign a new IP on every request. There's no sticky session option — each request goes through a different address. This works perfectly for scraping tasks where each page load is independent. For workflows that need the same IP across multiple steps — logging into a site, completing a checkout — we recommend our static dedicated proxies or ISP proxies.

When providers claim "10 million IPs," that usually counts every IP that has ever passed through their network — not what's active right now. Our 100K addresses are all datacenter IPv4, all live, all under our direct control. More importantly, they're exclusive to our service. Nobody else is using them, so they stay clean. A focused pool of fresh, unshared IPs outperforms a massive pool of recycled, flagged addresses every time.

There isn't one. FineProxy's rotating proxies come with unlimited traffic. You're not charged per gigabyte and there's no throttling at high volumes. For operations generating terabytes of traffic monthly, this is a fundamentally different cost structure compared to residential proxies that charge per GB.

Datacenter IPs face stricter checks on sites behind enterprise anti-bot solutions. For those, residential or ISP proxies generally perform better. Our rotating datacenter pool works well for the broad middle of the web — the majority of sites that don't invest in top-tier bot detection. For the toughest targets, pair our rotating pool with smart rate limiting and proper headers, or switch to ISP proxies for critical pages.

Point your HTTP client at the FineProxy gateway endpoint (domain:port). In Python Requests — one proxies parameter. In Scrapy — one middleware setting. Any language or tool that supports HTTP proxies works the same way. No SDK required, no proxy list files, no rotation code on your end.

Collecting publicly available data is legal in most jurisdictions. The 2022 US appeals court ruling in hiQ Labs v. LinkedIn affirmed that scraping public data doesn't violate the Computer Fraud and Abuse Act. That said, respecting robots.txt and rate limits is good practice — and it also reduces blocking, which is in your own interest. The proxy itself is a standard networking tool; legality depends on what you do with it.