Usage & Limits
The Usage & Limits page in the dashboard shows your plan, what you've used this billing period, and every limit you're measured against.
Where to Find It
Sign in to the dashboard and open Usage & Limits in the sidebar. Four tabs: Overview, API keys, Proxy users, and Limits & Features.
Overview Tab
- Your plan and billing period: one card with the plan's name, what it includes in a line (credits a month on a plan sold by credits, gigabytes a month on one sold by traffic), and the exact start and end dates of the window you're in with a bar showing how far through it you are. Paid plans reset on your billing date each month. Annual plans get monthly cycles anchored to activation. The Free plan anchors to your signup date.
- Credits this period: five stats side by side. Billed, Spent, Included, Remaining, and Overage. Only successful requests are billed and count against your plan. Spent is the total resource use including failed requests, which we never charge for. A usage bar under the stats colors amber at 80% and red at or over the included allowance. The panel isn't there at all on a plan sold by traffic, which doesn't bill credits. See How Your Plan Is Metered.
- Traffic this period: four cards, Total, API, Proxy port, and Premium, for everything the account moved this billing period, in and out together. Premium is part of the total, never extra to it. Where your plan caps standard traffic, a bar shows your use against that cap, and where it includes premium traffic, a second bar does the same for premium.
- Per-endpoint breakdown: a card each for Single, Proxy Finder, and Browser shows this period's Requests and Traffic, Billed credits on a plan sold by credits, and live In flight now and Rate last min (Browser: Today) next to your plan's numbers. An endpoint your plan excludes reads Not in your plan with a link to upgrade. An Auto card shows your Auto calls (Requests, Traffic, Billed credits) and Attempts by engine. Auto has no limits of its own; its attempts count against the Single, Proxy Finder, and Browser limits.
- Proxy Port: a panel under the three endpoint cards, because the port is a different product with a different unit. Four cards: Tunnels, Traffic through the port, At once, and Openings per minute. A plan that doesn't include the port reads Not in your plan with a link to Billing.
Three things are missing from the Proxy Port panel on purpose. There are no credits, because a tunnel has no request to charge one to. There's no live in-flight figure. And there's no request count at all: what happens inside a CONNECT is your own encrypted traffic, so a request count here would be a number you could never reconcile against your own logs.
Where the traffic ceiling is shared with the API, the panel says shared with the API next to it rather than quietly showing the other product's number.
API Keys Tab
A sortable table of every key that answers to your plan: Key, Status, Billed credits, Spent credits, Requests, Traffic, Premium, Share, and Last used, with a search box. Keys of organizations you own count against your plan too. Deleting a key never deletes its usage history.
This page ignores the dashboard's Owner filter on purpose. It answers "what bills to me", which is your personal keys and proxy users plus those of organizations you own. A member of somebody else's organization never sees the owner's quota. See Organizations.
Proxy Users Tab
What each proxy user moved this billing period.
| Column | What it shows |
|---|---|
| Proxy user | The name, its username underneath, and the owning organization when there is one |
| Status | Active or disabled |
| Tunnels | Tunnels the port answered for this credential |
| Traffic | Standard traffic it carried |
| Premium | The part that left through the premium network, or none |
| Share | This credential's share of your port traffic |
| Last used | When it last carried traffic |
A credential that moved nothing is still listed. "Issued and unused" is a different fact from "doesn't exist", and it's the one support gets asked about. No column counts requests, for the same reason the Proxy Port panel has none.
Limits & Features Tab
- Plan limits: one row per limit with your current value, what's included, and the status. Status reads OK, Near (80% or more), At limit, or Over. At limit is red where your next request is refused (credits, traffic, browser a day, rate, concurrency), and amber on API keys and team members, where only the next one added is stopped.
| Row | What it counts |
|---|---|
| API keys | Active keys you answer for, split into personal and organization |
| Team members | The largest organization you own, its owner included. An organization you only belong to counts against its owner, not you. |
| Organizations you own | How many you own, and whether your plan covers having one at all |
| Credits (this period) | Billed credits against what's available: what the plan includes plus any credits you bought, shown apart (75,000 (50,000 incl + 25,000 bought)) |
| Standard traffic | The API and the proxy port together, minus premium, against your plan's cap plus bought traffic. Reads Unlimited with no cap. |
| Premium traffic | Premium-network traffic with its share of all traffic, against the premium traffic your plan includes plus any you bought. Running out reads spent, never over: requests keep working on the standard pool and the response says exitClass: standard. A plan with none included reads top-up only. |
| Per endpoint | Requests per minute, concurrency, and browser requests per day for Single, Proxy Finder, and Browser, each with its live counter next to the plan's number. An endpoint your plan excludes reads Not in plan. |
- Plan features: the capabilities included in your plan, such as geo targeting (
exitCountries) and premium exits (exitClass). Features not in your plan show as excluded so you can see what an upgrade would add.
The numbers in this tab are the ones the API holds you to. A refusal from any of them arrives with an X-FourA-Limit header naming the row: see Rate Limits.
Freshness
Numbers on this page come from the billing pipeline, and the page refreshes them every 30 seconds while it's open. If a request finished a moment ago, give the page one refresh to catch up. Live counters for concurrency, per-minute rate, and browser-per-day sit next to your caps and update in near real time.
Related
- Billing & Subscriptions: Manage your plan, buy more credits or traffic, payment methods, and invoices
- How Your Plan Is Metered: Credits, traffic, and which ceiling applies to you
- Proxy Port: Tunnels at once, openings a minute, and what a refusal looks like
- Metrics: Timelines, outcome breakdown, and per-key charts
- Activity Log: The last 200 requests per key with payloads
- Organizations: Members, roles, and who the usage bills to
- Rate Limits: What triggers rate-limit responses