Latest updates and improvements to FourA
Pick a new period on Overview while the cards are still loading, and they now show that period's numbers, Auto attempts included. The period dialog also opens on the period you're viewing.
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.
Auto now hands back a JSON page in data as text, whichever route fetched it, so the same parsing code works on every call.
Send faster than your plan's per-minute limit and requests up to that limit still go through, since refused ones don't count toward the minute. Retry-After gives the seconds until the next one passes, and refusals arriving at over twice the limit get a 30-second pause. New proxy port connections are counted the same way.
The API, the proxy port, the MCP server, sign-in and the site now also run on standby servers. If the main servers stop answering, traffic moves over automatically, with nothing to change on your side.
FourA MCP 0.7.3 publishes tool schemas that validate under both JSON Schema draft-07 and 2020-12, so clients with a strict 2020-12 validator list and call all four tools. What a call accepts hasn't changed. Update @fouradata/mcp, or connect to the hosted server, which already runs 0.7.3.
The prices FAQ now spells out how we count a gigabyte: 1,073,741,824 bytes, with API traffic measured on the decoded page and proxy port traffic measured as it crosses the tunnel. Your Dashboard shows the same definition next to your traffic figures. Full method →
A request refused because it hits a limit on your own plan doesn't add to your traffic total. Responses from the target site still count, since that traffic was carried.
Traffic figures on your Dashboard now read in gigabytes wherever a gigabyte limit sits beside them, so a number and its ceiling always compare directly. Anything under a gigabyte still shows in MB, and large figures drop decimals that add nothing.
Every top-up on your Billing page now has its own line: what you bought, what's been used from it and what's left. Usage draws from the top-up that expires first, and the usage card lists your included traffic and your top-ups separately.
When an Auto call hits a limit on your plan, Activity now shows it as Rate Limited, and the response carries the same X-FourA-Limit header a direct call returns. You can tell which limit you reached at a glance.
