Docs › Dashboard › Dashboard Overview

Dashboard Overview

The FourA Dashboard is where you manage API keys and proxy users, run test requests, monitor performance, handle billing, and configure your account. This page walks through the main Overview screen and the sidebar sections.

Accessing the Dashboard

Sign in at foura.ai/dashboard. You need a FourA account: sign up here if you don't have one.

Two Products, One Set of Pages

Overview, Metrics, and Activity each open on a Product switch with two choices:

Product What it counts Unit
API The requests you send to /api/single, /api/proxy, /api/browser, and /api/auto Requests and credits
Proxy The tunnels your own tools open through proxy.foura.ai Tunnels and bytes

A tunnel carries whatever your client sends through it, and what happens inside a CONNECT is your own encrypted traffic. So the Proxy views count tunnels and bytes and never requests or credits. Read Proxy Port for the product itself.

The switch is always on one of the two, it's remembered between visits, and it's in the address as #overview/proxy, #metrics/proxy, or #activity/proxy. Paste one of those links and the page opens on that product.

Don't confuse the Proxy product with the Proxy Finder endpoint chip. Proxy Finder is POST /api/proxy/, one of the API's four endpoints. The Proxy product is the proxy port.

Overview Page, API Product

The landing page after sign-in shows your headline numbers for the period you pick.

Before Your First Request

Until your first request arrives, the API view shows sample data, with a Sample tag on each panel and chart, under a This is sample data. banner with two steps: Create API key, whose new key opens with a test command, and Open Playground to send a request. On a phone or tablet the steps point you to the Playground, because a phone can't run the command. Your first real request replaces the sample data for good.

The Proxy view has its own No traffic yet. banner with Create proxy user and Open Proxy, shown until one of your proxy users carries traffic. Closing either banner hides both.

Summary Cards

Five panels across the top, and a sixth when Auto ran something in the period:

Panel What it shows
Concurrency Requests running at the same time right now, plus the average and max for the period
Requests Total calls, then Single, Proxy, Browser, and Auto, each with its share of the total underneath. An Auto call counts once, under Auto.
Auto attempts Shown only when Auto ran something in the period. The Single, Proxy, and Browser requests Auto made behind your Auto calls, with the attempts per Auto call. They never count as requests or in the success rate, and their credits are inside Auto's credits. They do count against your Single, Proxy, and Browser rate and concurrency limits.
Credits Billed credits as the value, spent credits underneath, for the total and for each product, Auto included
Bytes Data transferred: In is what you sent, Out is what came back, and Premium is the part of that traffic that went through a premium exit, whether or not that exit delivered the page. Premium sits inside the two totals and is never added to them.
Response Time Average, min, and max across the period

Billed and spent are different numbers. Only a successful request is billed, so billed is what you pay for. Spent is every outcome, because a failed request still consumes a proxy or a browser. Reading one under the other's name is how the same account ends up looking like two different accounts on two pages. See Request Outcomes for which outcomes bill.

The Requests and Credits panels label the four endpoints Single, Proxy, Browser, and Auto. The Endpoints filter row above them calls Proxy Proxy Finder, which is the same thing: POST /api/proxy/.

The four don't always add up to the total. A small number of calls carry none of them, and they're counted in the total and in no endpoint.

Timeline Charts

Below the panels, six timeline charts plot request volume, credit spend, outcome breakdown, response time, bandwidth, and concurrency. Every chart has a toggle in its header that swaps the plot for the underlying table.

Overview Page, Proxy Product

Switch Product to Proxy and the same page answers in tunnels. Four panels:

Panel What it shows
Tunnels at Once Tunnels open at the same moment. Current covers the last few seconds and refreshes every five; Avg and Max cover the period. Your plan limits this across all your proxy users together.
Tunnels Success and Failed, each with its share of the total. Failed is every other outcome, and the Outcome row says which.
Traffic In is what your tools sent, Out is what came back, and Premium is the part that left through the premium network, counted inside the totals rather than added to them.
Setup Time Avg, Min, and Max wait before a tunnel was handed over, on successful tunnels only. It's the wait before your first byte, not the speed of the site behind the tunnel.

Five timeline charts sit below them: Tunnel Timeline, Outcome Timeline, Setup Time Timeline, Traffic Timeline, and Tunnels at Once Timeline. Each one takes the same chart or table toggle as the API charts.

Three panels dim while an Outcome pill is on, and the reason is in each case that the number doesn't exist for that outcome. Tunnels at Once dims under any outcome. Setup Time and Traffic dim under a failure outcome and carry a Success only badge, because a failed tunnel was never handed over and carried nothing.

Period and Detail

Period is how far back you're looking. Eight pills plus Custom:

Pill Window
30M Last 30 minutes
3H Last 3 hours
12H Last 12 hours
24H Last 24 hours
7D Last 7 days
30D Last 30 days
90D Last 90 days
1Y Last 12 months

Custom opens a dialog with four presets, This month, Last month, Last 6 months, and All time, plus a From and To date pair. A date range runs to the end of the day you picked, never past this moment.

Detail is how wide each bar is: per minute, every 5 minutes, every 30 minutes, hourly, every 6 hours, daily, weekly, or monthly. It defaults to Auto, which picks the coarsest step that still puts at least fifteen bars on the chart, so a year reads as a shape instead of 365 hairs. The Auto option names the step it chose.

Period and Detail apply to both products.

Detail steps that reach further back than FourA keeps that resolution are greyed out rather than hidden:

Resolution How far back it goes
Per-request 7 days
5-minute 30 days
Hourly 12 months
Daily The whole history

Pick a period older than a level allows and the finer options grey out. Auto never picks one of them, so a chart is never empty because the data was aggregated away.

Filters

Filters stack and combine, and Period and Detail sit alongside them.

Filter Product What it does
Product both API or Proxy
Endpoints API Scope to one endpoint: Single, Proxy Finder, Browser, or Auto. An Auto call counts once, under Auto; the Single, Proxy and Browser requests its ladder made behind it are shown by name in the Auto attempts panel, never as requests of their own.
Outcome both Isolate one category. The API offers all seven; the Proxy product offers the five a tunnel can end in.
Owner both Everything, Personal, or one of your organizations. Appears only when you belong to at least one.
Key API Restrict to a single API key
Proxy user Proxy Restrict to a single proxy user

The Concurrency panel and chart on the API side don't take the Endpoints or Outcome filter. Both dim while either is on, and the chart says so in its header.

The Owner Filter

The Owner dropdown answers "whose traffic am I looking at". It offers Everything, Personal, and one entry per organization you belong to, and the same control on Metrics, Activity, API Keys, and Proxy follows your choice, so the pages never disagree.

Usage & Limits and Billing deliberately don't take it. They answer "what bills to me", which for you is your personal keys and proxy users plus those of organizations you own. See Organizations.

Eleven sections in four groups: Dashboard, Tools, Access, and Account.

Dashboard: Overview, Metrics, Activity

The three pages that answer "what happened". All three carry the Product switch.

Overview is the page above, and always the starting point after sign-in.

Metrics holds the Usage panel: a breakdown grouped by API key, client IP, or domain on the API side, and by proxy user, target, exit country, client IP, or outcome on the Proxy side, with cards for the whole period above a paged table. See the Metrics guide.

Activity is a live feed of the last hour. On the API side each row is one request: method, target domain, status, outcome, duration, transfer size, and credits. On the Proxy side each row is one tunnel: proxy user, target, exit, outcome, setup, duration, bytes, and client IP. See the Activity Log.

Tools: Playground, Extension, Docs

Test live requests against your real API key without writing any code. Pick Auto, Single, Proxy, or Browser, set a URL, tweak flags and timeouts, and hit Send. Save common configurations as presets, replay any of your last 20 runs from History.

Usage counts against the key's quota, the same way a production call would. See the Playground guide.

Extension, marked Beta, is where you download the FourA Chrome extension. Its popup sends Chrome through one of your proxy users, and its FourA tab in DevTools turns any request a page makes into a ready API call. See Chrome Extension.

Docs opens this documentation in a new tab, so the dashboard page you're on stays put.

Access: API Keys, Proxy

API Keys is where you create, view, and manage the keys your applications use to call the API. Keys use the pk_live_ prefix. See Managing API Keys.

Proxy is where you create proxy users and copy a connection string for any client that accepts a proxy URL. Tunnels and traffic through the port count against your plan, the same as the API. See Proxy Users and the Proxy Port reference.

Account: Organizations, Usage & Limits, Billing, Settings

Organizations share API keys and proxy users with colleagues under one owner. Add people by email, set their role, and hand the organization over when it needs to change hands. Usage on an organization's credential counts against the organization owner's plan. See Organizations.

Usage & Limits shows your plan, what you've used this billing period, and every limit you're measured against, with a per-key, per-endpoint, and per-proxy-user breakdown. See Usage & Limits.

Billing manages your subscription, buys more credits or traffic, keeps payment methods and invoices, and shows this period's credits, traffic, and premium traffic against your plan. See Billing & Subscriptions.

Settings holds your display name, password, active sessions, and connected sign-in providers. Email changes aren't available in the dashboard: contact support.

Tips

  • Use the Playground before writing code. If you don't know which engine a new site needs, start with Auto and let it pick.
  • Compare billed against spent on the Credits card. An endpoint where the two are far apart is failing often, and the attempt report says why.
  • On the Proxy product, a block of Rate Limited in the Outcome Timeline is your plan's number, not the target refusing you. The Outcome view on Metrics names which one.
  • Keep your API keys and proxy users secure. Disable either immediately if you suspect it's been exposed.

Next Steps

Last updated: October 7, 2026
Creating a Task →