0% 5h quota used · resets in 2h subscription read 3h ago · 522 runs on the books · live · 08/09/2026 12:04 CEST

What is left to spend

Anthropic sells a quota that refills; DeepSeek sells credit that runs out. Every figure is a reading with an age.

Subscription quota

read 3h ago from _global:pr-review
5-hour window 0%
0%ceiling 100%
resets in 2h, at 08/09/2026 14:00
7-day window 23%
23%ceiling 100%
resets in 1d, at 09/09/2026 16:00

Prepaid credit

polled hourly, one request per provider
deepseek $99.40
read 4m ago
The balance the provider reported, and what the ledger has drawn against it since
ProviderReportedReadRuns sinceDrawn sinceEstimate now
deepseek$99.4008/09/2026 12:00 (4m ago)0$0$99.40

Estimate now is arithmetic, not a reading: the reported balance minus cost_real_usd for every run the ledger has recorded against that provider since. It is shown beside the reported figure rather than instead of it because the two disagree for a known reason — the provider settles late. tools/bin/price-watch measured DeepSeek's balance still moving hours after the run that moved it, which is also why price-watch reconcile settles the previous day and never the current one.

Where these numbers come from

Subscription windows
The rate_limit_event Claude Code emits on its stream, which carries what the API returned in its anthropic-ratelimit-unified-* response headers. Recorded by orchestrator/src/quota.js when a run ends. No request is made to read it — it rides in on requests the run was making anyway, so the meter cannot be rate-limited and cannot fail separately from the run.
Prepaid balances
One GET per provider per hour, to the balance_url its rate table declares (orchestrator/src/rates/*.json). A failed poll keeps the previous figure and records why it could not be confirmed.
Whose account
The container authenticates as Country OS's own Anthropic account, not the one anyone uses interactively. These windows are this system's runway and nobody else's.

What this page cannot see

The subscription reading only moves when a run finishes, so between runs it is either current or past its reset — there is no third state, because each window resets at a fixed instant rather than decaying. Tokens spent by a run that died before its first response are invisible to both halves of this page. And nothing here can be refreshed by loading it: this console reads files and asks nobody anything.