Changelog

Some sites refuse a first request and hand you a session in the same response. Single, Proxy, Auto and Browser now send it straight back on the same exit, so the page arrives on your first call instead of costing you a retry.

Ask Browser for a URL with #reviews on the end and the page comes back at normal speed. If anchored links were coming back as timeouts on you, that's gone.

When a site keeps its challenge up, Browser now answers with the vendor, how many presses it made and whether clearance was granted, so you can move to a different proxy right away. A page that does clear reports defenseSolved: true on the call that cleared it.

Update your billing details after an invoice has gone out and the Invoices table now offers Update details on it, for as long as that invoice sits in its issue month. The dialog names each field that changes, and the number, the dates and the amounts stay exactly where they are.

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.

Set timeout_ms up to 120 seconds on a Browser request and it runs for that whole budget, so a slow target gets the time you gave it and you read the engine's own verdict.

Browser now solves Cloudflare's checkbox challenge on concurrent requests to the same page, and a press only counts once the challenge is really gone. Three requests at once clear in 5 to 9 seconds.

Playground now renders the response from your target, including on sites that set large cookies, and API endpoints always answer in JSON.

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.

If your target redirected to a different URL path, Browser used to return 'No response received' even though the page arrived. That's fixed; the request follows the navigation wherever it lands. eBay, redirect-heavy shops, and anything with a 3xx to a challenge page all work now.

Responses now report akamai and ebay-splashui where they used to report nothing (or wrongly attribute the block to Cloudflare). If your code branches on defense.vendor to pick a retry strategy, those two names show up correctly now.

Activity now fits a 14" MacBook without sideways scrolling, and every column keeps its value. The detail panel is a tabbed pane (Request, Response headers, Response body), so the answer is at the top instead of 900px down. Tooltips follow your pointer and read out the full URL.

The method column now reads the verb from your request body (GET, POST, PUT, etc.), instead of always saying POST because that's what our API layer took. Playground calls also record the browser IP of the person who clicked Send, so a shared account can tell who ran what.

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.