Highlights
Which of your domains really need a browser? The Dashboard now answers that per API key, client IP and domain, in a new Routes view on the Usage table. Auto also learned to reach for a premium exit when you allow it, and it stops early on pages a site has removed.
What's New
Auto can escalate to a premium exit
Auto now accepts exitClass, the same field Proxy Finder takes. With premium, a page the standard pool can't reach opens in a browser through a premium exit, and that traffic counts against your plan's premium allowance. With standard, Auto stays off premium exits. Leave the field out and Auto behaves as before.
When you name a class, meta.exitClass and the X-FourA-Exit-Class header say which one delivered. Running out isn't an error: once your plan's premium traffic is spent for the period, the call carries on in the standard pool and says standard. On a plan without premium exits, premium gets a 403 with X-FourA-Limit: plan_limit_premium before any work starts.
import requests
r = requests.post(
"https://api.foura.ai/api/auto",
headers={"X-API-Key": "pk_live_..."},
json={"url": "https://example.com/article", "exitClass": "premium"},
)
print(r.headers.get("X-FourA-Exit-Class")) # "premium" or "standard"
session = r.json().get("session") # proxy, cookies, userAgent
Auto is still the path finder, not the production route. Once it has found a route, replay its session (proxy, cookies and user agent) on /api/browser when the page needs rendering, or on /api/single when it doesn't. On a premium exit through Browser, add the new lean: true. It leaves out images, fonts, media and requests to advertising, analytics, consent and social services, while the page, its own scripts and anything a verification step needs still load. Every parameter is in the endpoint reference.
The Dashboard Playground shows the field for Auto, and the MCP server takes it on foura_auto.
See what Auto ran, domain by domain
The Routes view splits each key, client IP or domain three ways: your requests per route (Single, Proxy Finder, Browser, Auto), the attempts Auto made behind its calls (failed ones included), and the step that answered each Auto call.
It opens sorted by the browsers Auto ran, so the domains that need one most sit at the top. Those attempts never count in your requests or success rate. They do count against your plan's rate and concurrency limits, which is one more reason to move a domain off Auto once its route is known. The Metrics docs explain every column.
Removed pages, and pauses that are yours alone
When the page you ask for is gone, Auto now ends the call with the site's 404 or 410 once two exits bring the same answer. Put the status in your validate rule ("validate": {"status": {"accept": [200, 404]}}) and the first exit's answer comes back as a success.
The short pause Auto takes on a site that keeps failing (target temporarily unservable) now counts only your own calls, and a removed page never counts toward it. So another account's trouble with a site can't pause yours. The same goes for first visits: when several calls start on a site with no session yet, only your own calls wait for the one building it.
Two smaller ones. When a site rate-limits one exit, Proxy Finder rests that exit for that site alone, for the wait its Retry-After names, and keeps it for every other site. And when the exit behind a stored Auto session stops answering while another one delivers, the session moves to the exit that delivered, so session.proxy names a working one.
Browser waits for pages that check first
Some sites answer a first visit with a device check that runs in the page and then reloads it. Browser now waits for that reload and returns the page it leads to. If the check doesn't let the browser in, you get the check page after the wait.
Send several Browser requests at once and any that arrive while every browser is busy wait up to 10 seconds for a free one. Auto's browser steps queue the same way.
Exit checks on files
With returnBuffer: true, Single and Proxy Finder now check an image or PDF download the way they check a page. If an exit answers with its own page instead of your file, Single reports a failed attempt and Proxy Finder moves on to another exit. An exit behind a company network gateway, which answers everything with its own login page, now counts as a failed attempt on Single, Proxy Finder and Auto.
Dashboard, sign-in and MCP
- The Proxy users table and the API keys tab on Limits fit a 13-inch laptop. With a mouse, hover a header with a dotted underline to read what its column counts. A table with more to the right shows a shaded edge at every width, dark theme included.
- The Dashboard follows the theme you picked on foura.ai, the blog, the docs or the updates portal, from the first paint.
- In Settings, the name field keeps what you type even if you start the moment the page opens, and a saved name stays saved. When a name can't be used, sign-up and Settings say so under the field.
- Sign-in lets your browser remember the email you use, Enter works on both steps, and on an iPhone the fields no longer zoom the page.
- The MCP server is at 0.8.1. Besides
exitClassonfoura_auto, its tool descriptions now pointfoura_singleandfoura_browseratfoura_autoas a source of premium exits.
Under the Hood
When we roll out a new version of the proxy port, your open tunnels now get three minutes to finish, up from one. A tunnel still open at the end is closed properly and gives its concurrency slot back at once. And a rollout that doesn't change the port leaves your tunnels alone.
The domains at the top of Routes are the ones Auto has already worked out. The cheapest thing you can do with them is stop asking Auto.