Latest updates and improvements to FourA
Your Dashboard's Usage table has a new Routes view: see your requests split across Single, Proxy Finder, Browser and Auto, per API key, client IP or domain. For Auto calls it shows what ran behind each one and which step answered, so you can tell where your credits go.
Auto now accepts exitClass, as Proxy Finder does: premium lets a page the standard pool can't reach open in a browser through a premium exit, counted against your plan's premium traffic, and standard keeps it off them. meta.exitClass and the X-FourA-Exit-Class header name the class that delivered. The Playground and MCP foura_auto have it too.
The API, the proxy port, the MCP server, sign-in and the site now also run on standby servers. If the main servers stop answering, traffic moves over automatically, with nothing to change on your side.
The prices FAQ now spells out how we count a gigabyte: 1,073,741,824 bytes, with API traffic measured on the decoded page and proxy port traffic measured as it crosses the tunnel. Your Dashboard shows the same definition next to your traffic figures. Full method →
Every run of our web scraping benchmark is now public. The script, the page list and every result live in fouradata/web-scraping-benchmark (code MIT, data CC BY 4.0), so you can run the same pages yourself and check our numbers. See the latest run
When an allowance reaches 95%, you get an email with the day it runs out at this period's pace, set against your reset date, and the one action that raises it. The 100% email now says how many days remain until the reset and, on plans with overage, what the rest is billed at.
On a paid plan sold by credits, the proxy port has its own included gigabytes, and you can now buy more from the Proxy port card on your Billing page. The port's usage emails offer the same top-up.
When your bank wants a renewal or a due payment confirmed, the Billing page shows it and a Confirm payment button finishes it with your saved card.
When a downgrade or a change of billing interval waits for the end of your period, the Billing page says which plan you move to and when. A Keep button calls it off and leaves you where you are.
A beta Chrome extension sends your browser through one of your proxy users and shows the address sites see. Its DevTools tab turns any request a page made into a curl, Python, Node or MCP call. It isn't in the Chrome Web Store yet: install it from the Dashboard's new Tools section, in developer mode.
The main site's menu now groups Products, Tools and Resources. The API page walks through the four endpoints and the parameters you control, and the proxy port page covers its two networks, country targeting in the username, sticky and rotating sessions, and how it's billed.
FourA MCP 0.7.0 adds exitClass to foura_proxy: set it to premium and a request moves to a premium exit only when the standard pool can't deliver. A rotation that doesn't get through returns an attemptReport, and a refusal by your own plan keeps its plan_limit_* code. MCP server →
Overview, Metrics and Activity now switch between API and Proxy, and remember your choice. On Proxy you see your tunnels in the same outcomes as your API requests, how many are open right now, setup time and traffic, broken down by proxy user, target, exit country or client IP.
An organization can now own a proxy user, so your company's jobs don't hang on one person's account. Any member can rename it and read its password. Owners and admins rotate, disable, delete or change its saved targeting, and only the owner can move it out of the organization.
Plan & Usage now carries a card for bandwidth and one for premium traffic beside credits, each showing what you've used against what your plan includes plus anything you've bought. When a top-up is on sale, the Buy button sits on the card it tops up.
