Protocol
How credits are made, priced and spent.
One program on Solana and one gateway. Every number on this page is read from the program as it stands.
The budget is funded
Each period, the funder reports the protocol's AI budget to the program. That many credits stream to stakers, second by second, until the period ends.
Stakers earn credits
A stake earns its share only for the time it is staked, so joining right before a funding earns nothing extra. Credits are minted when the staker claims.
The book prices them
Stakers list credits at the discount they choose. Asks fill cheapest first, in arrival order within a price. Sellers collect USDC whenever they want.
Activation pays for models
Activating burns credits into a wallet's API balance. Buying from the book can activate in the same transaction. The gateway then spends that balance at each provider's own price.
Parameters, live
Fees and limits are plain admin settings on the program. They read zero until they are set.
Addresses
Not deployed yet. The addresses appear here at launch.
The gateway
A wallet's balance is what its activations credited, less what its requests cost or still hold. Before a request goes out, the worst case it could cost is held in one atomic step; when the answer is back, it is settled at the provider's own reported cost and the rest is released.
Activations are read from the program's own signed events, so nothing but the program can credit a balance. Requests are relayed as sent. OpenRouter is pinned to zero-data-retention endpoints and asked for the exact cost; Chutes requests run on Bittensor subnet 64. Prompts and answers are never stored, only billing metadata.
Keys
An API key is the wallet's public key and its signature of a fixed message that names the cluster and a key number. The gateway checks the signature on every request. Signing a higher number replaces the lower ones once it is used.