Browse documentation
Treasury, graphs and live activity
Provider credit
The treasury reads GET https://openrouter.ai/api/v1/credits with a server-only OpenRouter credential that can read account credits. It validates finite, non-negative total credits and usage, then displays available account credit as the non-negative difference. The accounting gateway conservatively rounds available capacity down to integer USD millionths.
Use a dedicated OpenRouter account. Its aggregate totals can include activity outside Trident if the same account is used elsewhere. The chart is not a blockchain treasury audit, bank balance, token backing or redemption promise. OpenRouter figures remain subject to provider reporting delays and adjustments.
The configured account's aggregate balance is published by default; set PUBLIC_TREASURY_ENABLED=false to hide it. No management or inference secret is sent to the browser. When disabled, both the public current balance and public history are hidden. When unconfigured or unavailable, the page displays an unavailable state rather than an invented zero.
Ledger balances
TRIDENT holders draw directly from available provider credit. Separate legacy allocations, if any, remain reserved for those accounts. Reserved credit is held for pending or unresolved inference. Pending deposit valuations are conservative estimates awaiting conversion, provider funding and activation. These categories are separate from the provider account credit; adding them together would double count funds.
The primary holder flow does not ask for a deposit or allocate a separate community budget. No automatic conversion of token trading fees into provider credit is claimed.
Chart provenance
| Chart | Source | Observation policy |
|---|---|---|
| Provider credit history | Authenticated OpenRouter credits response | Last observation in each five-minute bucket, up to 90 days retained; chart displays 288 latest points |
| Model tariff bars | Public OpenRouter model catalogue | Current published USD per million input/output tokens |
| Model price history | Observed catalogue responses | First observation per model per hour; 90 days retained, 90 latest points displayed |
| API request / cost charts | Local shared accounting ledger | Actual records grouped by request day in UTC; up to 30 observed days |
| Featured token price | Confirmed RPC or separately labelled Pons indexer | Real observations only; different source histories remain separate |
No curve is generated from random numbers. One observed point is shown as one point, not invented history. Missing days and intervals are not padded with synthetic values. A visual line connects recorded observations; exact observations are available below the chart. Pons-indexed retrieval time does not establish when its underlying market data was last updated.
Wallet and activity counts
Active wallets means unique chain-and-wallet identities with an authenticated, unexpired session and a heartbeat in the last five minutes. The browser sends a heartbeat only while its document is visible. A connection without a verified signature is not counted. Different chain identities can belong to the same person; these are not unique human counts.
Wallets signed in is the number of stored chain-and-wallet identities. Active API keys excludes revoked keys. Public activity shows completed API requests. It does not expose wallet addresses, prompts, API key prefixes or provider generation identifiers. Zero activity is a valid initial state.
No personal founder information or biography is required for these pages. Wallet authentication and public blockchain activity are pseudonymous, not a guarantee of anonymity.