Emails when someone joins your organization
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.
Latest updates and improvements to FourA
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.
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.
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.
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.
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.
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.