Changelog

Billing details now has a Company representative field. Bulgarian invoices print it in the recipient box as MOL, so the line comes out carrying your representative's name.

Plenty of sites serve their entry page to anyone and gate the deep ones. Auto now takes the session that entry page hands out and asks for the deep URL carrying it, and tells you it did with a warmup rung in the response.

eBay's protected pages redirect visitors to an Argon2 proof-of-work challenge. Single now solves it in one call and returns the real listing at 2 credits, down from around 360 through the fallback path. If you've been paying full price on eBay, that's over.

FourA MCP 0.6.0 lets an agent choose which browser a request presents. foura_single and foura_proxy accept browser, os, version, or an exact profile id from the public catalogue at GET /api/profiles. They travel inside the request that already goes upstream, so there is no extra call. Leave them out and the request presents the latest Google Chrome, exactly as before. A combination the catalogue cannot present comes back as an error listing what is available, so a request is never sent as a browser you did not choose.

Both tools now return defense when the target ran a bot check. defense.solved: false means the body may be a challenge page rather than the content you asked for, which is the signal to retry with a different browser or escalate, instead of parsing a block page as data.

One correction in the same release: the unblocker description said its default was off. It has always been on, so requests already carried a full browser header set. The published schema now matches the behaviour.

The profile parameter tells the unblocker which browser to look like on /api/single and /api/proxy. Pass an exact profile id (like firefox147 or chrome146), or let browser + os + version resolve to the newest matching combination. GET /api/profiles returns the current catalogue (79 profiles across five browser families), so you don't hardcode a list that goes stale. The Dashboard playground exposes the same picker as three cascading selects.

If an admin assigns you a custom plan, it now shows up in Billing / Plan as 'Your custom plan: {name} ({price})' with a button to subscribe. Before this, the assignment sat invisible until someone told you it existed.

SiteGround fronts a large chunk of small WordPress and WooCommerce shops, so its Robot Challenge Screen is a class of targets, not one site. With unblocker: true, Single now solves it in-process and returns the real page. Before this, you had to bring up Browser for that class of target, which meant paying for a browser session and the wait. The clearance cookie comes back in the response, so a replay stays cheap.

SiteGround puts a 'Robot Challenge Screen' in front of a lot of small WordPress and WooCommerce shops; there's nothing to click, it's a SHA-1 proof of work. Single now clears it in one call and returns the real page, at 2 credits instead of a 30-credit browser session. It's the first non-Cloudflare defense Single handles on its own.

Every plan limit now sits next to what you've actually used this billing period. Credits split into billed (successful requests only) and spent (everything you consumed), with a per-key breakdown and live counters for concurrency and rate. Open it from the sidebar in your Dashboard.

The Dashboard has a new Billing details tab for your standing invoice profile: company, VAT with live verification, and address. Organizations now lives on its own page as a sortable table you can create from and rename. Every API key has an owner (personal or an organization), and you can transfer a key between them without losing its metrics.

If we've built you a custom plan, it now shows up as its own tab when you change plans. And if you don't have a subscription yet, that same picker takes you straight to checkout. No more email-and-wait to move onto your plan.

FourA MCP 0.5.0 adds strict country-scoped selection to foura_proxy. Pass exitCountries with the target-visible countries you need, and a scoped success returns exitCountry plus the reusable proxy ID for foura_browser. If the pool has no match, no_eligible_proxy preserves your scope instead of falling back to another country.

Pass exitCountries: ["CZ", "GB"] to /api/proxy to keep the exit inside the list you provide, and the response reports which country actually served the request so follow-up calls can pin the same geography. If the pool has no match, the call fails with no_eligible_proxy instead of falling back to a different country. Try it without any code in the Playground.

The Overview page now shows a Credits panel with your total credits used plus a per-product breakdown (Single, Proxy, Browser). Big numbers stay compact (like 29.7M) and hovering reveals the exact value. Respects your active filters and time range.

There's now a dedicated home for the FourA MCP Server at foura.ai/mcp. Pick your client (Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, or the hosted remote server), copy the config, or install with one click through the Add-to-Cursor and Install-in-VS-Code deeplinks. Four tools ship with it: foura_auto, foura_single, foura_proxy, and foura_browser.