PROTOCOL / FUNDING & ACTIVITY

Every credit has a story.

Inspect real provider credit, authenticated wallets and actual usage.

OPENROUTER / AVAILABLE CREDITAWAITING CONFIGURATION
—

Connect the dedicated OpenRouter account to publish its real credit balance.

Credits purchased—Account usage—
How this balance is verified
Shared treasury ledger
Available to new holder requests
—
Recorded holder API cost
—
Separate legacy allocations
—
Held for in-flight / review requests
—

TRIDENT holder requests draw directly from available account credits. Separate legacy allocations are excluded from spendable shared capacity.

Provider credit history

No observations yet. The chart starts with the first recorded data point.

Observed from OpenRouter’s credits endpoint. At most one point per five-minute interval; historical observations may be shown even if the latest refresh failed.

Active signed-in wallets—Authenticated heartbeat within 5 minutes
Wallets signed in—Unique chain-and-wallet identities
Active API keys—Issued keys that have not been revoked
Gateway requests

No observations yet. The chart starts with the first recorded data point.

Settled API usage

No observations yet. The chart starts with the first recorded data point.

Live activity
Reading the ledger…

Activity is loaded directly from this deployment.

Refreshes every 15 seconds while visible and after a playground request. Public activity excludes wallet addresses, prompts and API keys.

Service configuration
Holder inference
Checking…

Holder access uses the shared provider account. No token registration or deposit is required. Availability depends on eligibility, provider credits and fair-use limits.