Shared OpenRouter treasury

TRIDENT holders use one provider-funded treasury. Users do not deposit funds, create a budget or register a token to use it. The operator funds the dedicated OpenRouter account. When more verified credits arrive there, the gateway can use them without allocating each model or holder a separate balance.

What the app verifies

The server reads /api/v1/credits, validates purchased credits and usage, and computes the remaining account balance. It uses OPENROUTER_MANAGEMENT_KEY when provided, otherwise the configured inference key if OpenRouter accepts its credit-read permission. A key's spending limit is not used as a substitute for account credits.

The treasury page publishes real aggregate account credits by default for this project. PUBLIC_TREASURY_ENABLED=false hides those figures. No credential, key label or provider account identifier is returned.

Reservations and billing

Accounting uses integer millionths of a US dollar. The gateway obtains a recent provider balance and, in an atomic transaction, subtracts pending reservations, recent settlements not covered by the observation, and any separately allocated legacy balances. A new request must fit the remaining capacity and configured limits.

The internal TRIDENT access-policy row has no fabricated funded balance. Provider credits are the funding authority. Settlement records the actual cost without adding refund credit to a second ledger. Unknown costs remain held. Concurrent server instances serialize accounting writes.

Creator fees

Creator fees may finance provider top-ups. The operator must claim proceeds, perform any necessary conversion and fund OpenRouter through the provider's supported payment methods. This repository does not hold a treasury private key, automatically claim fees or automatically buy provider credits. Trade volume, market price and onchain fee accrual are not treated as spendable OpenRouter credit.

Fair use and exhaustion

The default request ceiling is $1 and the global daily ceiling is $100. The default wallet rate is 20 requests per minute. These are operator protections on a finite treasury, not a promised per-user financial entitlement. More keys or a larger holding do not bypass the same wallet and global limits.

If credits run out or the provider cannot confirm capacity, new paid requests stop. The operator can replenish OpenRouter or explicitly pause inference with COMMUNITY_COMPUTE_ENABLED=false. Legacy receipt/allocation records remain readable for reconciliation, but that deposit workflow is not the public TRIDENT access flow.