Highlights #
Was that the site saying no, or your plan? Every request your plan refuses now answers in one header, and Auto and the Playground read that answer too. The proxy port learned to remember targeting on the key, and Browser rendering plus CAPTCHA solving come with every plan, Free included.
What's New #
A refusal that names who refused
When one of your plan's limits turns a request away, the response carries an X-FourA-Limit header saying which one: plan_limit_credits, plan_limit_rate, plan_limit_browser_daily and four others. The body repeats the code under reason, beside the number you're held to. Our shared platform limits never set that header, so its presence alone tells you the refusal is about your account, not about FourA being busy.
import requests
r = requests.post(
"https://api.foura.ai/api/single",
headers={"X-API-Key": "pk_live_..."},
json={"url": "https://example.com/data"},
)
limit = r.headers.get("X-FourA-Limit")
if limit:
print("my plan stopped this:", limit, r.json()["error"])
Every limit on your account now comes from the plan you're on, and Usage & Limits lists each one next to where you stand this period. The rate limits reference has all seven codes and which ones a short wait clears.
Auto reads the same code and acts on it. A limit that shuts one rung (the day's browser allowance, say) leaves the rest of the ladder working, and the exits it already tried aren't blamed for a refusal your plan issued. A limit that means the account itself is out, like credits, bandwidth or a product your plan doesn't include, stops the ladder at once and hands you the refusal rather than trying every other route first. None of this changes what Auto is for: let it find the rung that works, then replay the session it returns on /api/single or /api/browser and point your volume there.
The Playground puts it in words. A line above the response says what carried the page: a session we already had for that host, a plain request, a rotating proxy or a real browser, plus whether a challenge was solved, which attempt got through and what it cost. When your plan stopped the request, the line opens with "Stopped by your plan, not by the site" and names the limit.
The proxy port, in beta
The proxy port lets any client that takes a proxy URL send its traffic through our exits, with no API call involved. It's a beta: traffic through it isn't billed yet, it carries no uptime commitment, and option names can still change.
This week it got clearer about what you're choosing: the shared network, which is our own exits and comes with your plan, or the residential network, home addresses drawn from your plan's premium traffic. Falling back to residential when the shared network can't carry a request is a separate switch, and it starts unticked. A box we tick for you would be us deciding to spend your allowance.
Targeting lives on the credential now. Save a country, region, city or device on a proxy user and every connection made with it answers that way. So the connection string shrinks to the bare credential plus whatever differs. But the username still wins for that one connection, and any takes a saved value back: -city-any asks for the whole country from a key that remembers one city.
Running a browser profile per address? Set how many sticky addresses you want and the page lists one line each, with its own session name. New names hands you a fresh set when a target has soured on the old one, and the lines come as a URL or as host:port:user:pass, the shape most proxy managers import. The proxy port docs have the whole username grammar.
Defended pages, on every plan
Browser rendering and CAPTCHA solving are part of every plan, Free included, and only the limits differ. Free and Developer carry some premium exit traffic as well, so you can watch a defended page come back on your own URL before you pay anything.
Premium exits on Proxy Finder stopped caring which site you point them at. Send exitClass: premium for any target and your plan's premium traffic (and what's left of it) is the only thing that decides.
Billing that follows your details
The company, VAT number and country you save under Billing Details are what we print on your invoice and what decides your VAT treatment, at checkout and on every renewal. Type something different into the payment form and it overrides that one field for that one payment.
If we've set you up on a plan as part of a signed deal, Plan & Usage now offers it back with a Confirm button: pick monthly or annual, add a card, and you pay the full period up front, nothing prorated.
Two new cards sit beside credits on Plan & Usage, one for bandwidth and one for premium traffic, each showing what you've used against what your plan includes plus anything you bought. When a top-up for that kind is on sale, the Buy button is on the card it raises. The billing guide walks through both.
Under the Hood #
Your per-minute rate limit counts exactly the traffic you sent in that minute, right up to the turn of the next one. Dashboard tables fit a laptop screen, and on a phone the wide ones scroll sideways inside their own frame. Blog tables scroll the same way on narrow screens. And your organization page lists pending invitations the moment it opens.
A refusal you can read is one you can plan around. Next time a job stops, one header tells you whether to wait a second, wait for midnight UTC, or go and look at your plan.