Changelog

Single and Proxy Finder now verify that a response actually came from the site you asked for. When a corporate network filter answers instead of your target, the request moves on to another route rather than handing you that page.

Your account can run 100 requests at once across Single, Proxy Finder and Browser. Past that you get a 429 with an X-FourA-Limit header naming which ceiling you hit, a machine-readable reason in the body, and a Retry-After saying when to try again.

Anyone added to an organization now gets an email naming it, who added them, and what their role can do. Owners hear about every new member too, since the organization's keys bill against their plan.

Add anyone to your organization by email from the Organizations page. If they already have a FourA account they join right away, and if they don't we email them an invitation and they're in the moment they sign in.

The Requests card on your Dashboard now breaks the total into Single, Proxy and Browser, each with its share of the traffic in the period you're looking at. Shares follow your filters, so narrowing to one product reads 100%.

Your Overview and Metrics charts now take any period from 30 minutes to a year, plus custom ranges: a calendar month, the last six months, all time, or an exact pair of dates. Detail follows the period by itself, and you can set it by hand from per minute to monthly.

The Playground's carry button now offers the browser profile from the last response, next to the User-Agent and proxy ID. When your request goes out under a different profile than the one you typed, carrying it replays the version that worked, and it turns Web Unblocker on so the profile applies in full.

Any member of your organization can rename a key it owns. Regenerating, disabling or deleting one stays with the owner and admins, since those stop every colleague using it, and only the owner can move a key out of the organization.

Overview, Detailed Metrics, Recent Activity and API Keys now share one Owner filter: Everything, just your personal keys, or a single organization. Usage & Limits and Billing stay personal, so what you're billed for never mixes with a colleague's traffic.

Your organization now has its own page in the Dashboard. Add a colleague by email, change their role, remove them, or leave an organization yourself, and every action tells you who ends up paying before you confirm it. The teams you belong to are listed there too.

Your Overview credits card now shows billed credits as the main number with spent underneath, for the total and for Single, Proxy Finder and Browser. You're only billed for successful requests, so the gap between the two is the work you didn't pay for.

Any member of an organization can now create API keys it owns, and move an existing personal key into it. Usage on those keys bills the organization owner's plan, so a developer doesn't need a personal key to work on company jobs.

A Proxy Finder task that runs out of tries now returns attemptReport: how many exits never answered, how many a defense refused and which vendors, and how many fetched the real page but didn't match your validate.data rule. There's a plain summary line too.

When a site turns down the profile Proxy Finder sent, it now tries a different one on a retry it was already going to make, so the task makes no extra requests. Pin profile yourself and it stays untouched; if you don't, a success names the one that worked.

Imperva injects its script into healthy pages as well as its block pages. Auto now tells the two apart, so an Imperva-fronted site comes back without paying for a browser: one attempt, 10 credits, about six seconds.