Usage, quota and background work

Usage records work that ran; quota describes how much new work a provider accepts. They are different measures. Era sells no AI: everything runs on your own subscriptions and API keys, and Era measures it.

One place: Settings › Usage

Usage is shown in one place, the same on the web and in Era Desktop. Pick the period at the top: last 24 hours, 7 days, 30 days or this month.

• Subscriptions — one line per member and plan (Claude Code, Codex, Antigravity): the 5-hour and weekly use as the CLI or its provider reported it, when each window resets, when it was last read, and the calls and tokens Era ran on it. Antigravity reports no 5-hour or weekly window, so those cells stay empty. A subscription costs nothing per call.
• API keys — per key: calls, input tokens (including prompt-cache reads and writes), output tokens and the cost at the provider's list price; then the same by member, by feature (Era chat, workflows, agents, memory learning…) and by model.
• Plan and This workspace — seats, modules, storage and background jobs against the plan.

Every number is summed from the same record of each model call, so the page, the budgets and the reports agree. A missing window does not mean unlimited quota. The cost is computed from the provider's list price; the provider account shows what you were billed.

Who sees what

Members with AI management see every member's lines. Everyone else sees only their own subscriptions and the calls they made. Budgets (Settings › AI › Budgets) cap spending; where it went is on the usage page.

Waiting work

Brain and other background jobs need an available subscription or API connection. Check the desktop connection when local work is needed. Read the stopping reason and inspect connection, quota, source access and job permissions separately.

Permissions

Reading usage does not authorize connection changes or organization plan management. Relevant settings management permission is required.

Choose a source · Provider billing