Using OpenRouter credits
Move earned credits onto your own protocol-funded OpenRouter key and use it in compatible AI apps.
On this page
Your own key, funded by the protocolFrom earned credits to inferenceLimits and accountingFunding and disabled keysKeep your API key private01Your own key, funded by the protocol
Each holder gets one dedicated OpenRouter API key, created the first time you use credits on OpenRouter and kept after that. Its spending limit is the total of the credits you have added. The key draws from the protocol's funded OpenRouter account. It is not a deposit into your personal OpenRouter account, and it is not an OpenRouter subscription.
Use the key in software that supports OpenRouter. Available models, model prices, and provider policies are determined by OpenRouter and the selected providers. The hosted GPU fleet earns the revenue that supports benefits; your OpenRouter request is not necessarily executed on that fleet.
02From earned credits to inference
Connect your wallet and prove ownership in Rewards.
Create your key. It starts with a zero spending limit, and you can reveal it again at any time. It works whatever you choose to do with payouts.
Load credits: any amount of your available balance from $0.01. If you choose Refill my key, each hourly credit is also added automatically as it arrives. Each addition raises the same key's limit by that amount.
Reveal the key securely and add it to your compatible AI app. Requests use the key's remaining limit as provider usage is reported.
03Limits and accounting
Additions are whole cents from $0.01, with no cap on how much a key can hold beyond a $1,000,000 sanity bound. The limit is a lifetime total, not a monthly budget that resets. Rewards shows your available credits, the key's limit, what it has used, and what remains on it.
Credits added to your key are spent at that moment: they stay on the key, can only be used on OpenRouter, and cannot be sold back for USDG. Your cost is capped at what you added; if OpenRouter bills beyond the key's limit, the protocol bears the difference.
One credit dollar represents a dollar of eligible inference usage. There is no additional protocol model-usage fee in this route. Different models consume that value at different rates; it is not a fixed number of prompts or tokens.
04Funding and disabled keys
An addition waits until the protocol's OpenRouter account holds enough to cover every holder's unspent key limits plus the new credits. Until then your credits stay available and nothing is lost; automatic additions retry on their own. The protocol's provider balance is maintained separately from the onchain backing of holder credits.
Rotate your key if it may have leaked or you want a fresh one. The old key stops working immediately and is never switched back on; its unspent amount, rounded up to the cent, moves to a new key that you reveal and copy into your apps. Usage the old key reports after rotation is covered by the protocol. You can rotate once every ten minutes and up to five times a day.
A key turned off for safety is never switched back on either. Its credits are not returned as available balance, but you can rotate to move what is left onto a new key. Check the Rewards page for your key's status.
05Keep your API key private
Anyone with your key can consume its remaining limit. Keep it out of public repositories, screenshots, and shared client applications. The service stores holder keys encrypted; the protocol's management key is never issued to holders.
Requests sent directly to OpenRouter are subject to that service's and the selected model provider's data policies. ComputeWorks does not need your wallet seed phrase or private key.