Latest updates and improvements to FourA
Send several Browser requests to the same site at once and any that arrive while every slot is busy now wait up to 10 seconds for one to open. Auto's browser steps queue the same way, so concurrent bursts to the same page get served in turn.
When a site rate-limits one of the proxies behind your request, Auto now rests that proxy for that site alone and keeps using it everywhere else. A single site under pressure no longer holds up your requests to it, and Auto keeps looking for a working path instead of waiting.
When several calls start on a site Auto has no session for, one of them builds it and the others wait to reuse it. That wait now happens only among your own calls, never on another customer's call.
When a site answers with DataDome's device check, Browser now waits for the check to finish and the page to reload itself, and returns the page it leads to. If the check does not let the browser through, Browser returns the check page after the wait.
When Amazon answers with its one-button "Continue shopping" page, Single and Browser now press the button on the same exit and return the product page. Proxy Finder and Auto calls get the same.
When a site turns away every exit Auto tries, Browser included, the call now ends after a few attempts. On a site Proxy Finder has served before, Auto asks Proxy Finder for the page first, and that search costs nothing if it comes back empty.
When a site answers with an AWS WAF challenge page, Browser now waits for the page to reload itself and returns what it leads to. Auto hands such pages to Browser on the same exit, so the call ends with the site's content.
On a phone or a narrow window, the Playground now scrolls the response into view as soon as it arrives. You see the result of Send without scrolling past the request options.
If you pass your own proxy URL to Single or Browser and its hostname doesn't resolve, the answer is now status 0 with an error naming the host, the same as for a target. A proxy on a private address still gets the 400 refusal.
An invoice we issue by hand for your account now shows up in Invoices beside the automatic ones. It's addressed from your Billing details and gets the same VAT treatment as every other invoice.
In the Usage table on Metrics, the Domain and Client IP views now rank every row in the period before splitting it into pages. Sort by any column and page one holds the real top entries.
A Single, Browser, Proxy Finder or Auto request whose target is api.foura.ai or eu.api.foura.ai now gets a 400 at once, before anything is fetched or charged. The error names the likely cause: a link taken from a page and resolved against the API URL instead of the page's own.
Requests to plain-HTTP sites through Proxy Finder now open a direct connection to the site first, the same way HTTPS always has. A proxy that answers with a page of its own instead of passing the site's along is skipped, and your request moves on to the next one.
If your invoice carries your EU country's VAT, it's the rate in force on the day of the sale. We keep the rates current from the European Commission's published figures, so a change announced in advance applies from its first day.
A sign-up started on foura.ai now ends in your Dashboard, where Overview shows the steps to a first result: create an API key, then send a request from a terminal or the Playground. On a phone they start in the Playground, and the proxy port gets its own steps built around a proxy user.
