DEVELOPER DOCUMENTATION

Authentication & keys

Your account manages keys. Your API key authenticates inference.

Bearer authentication

Authorization: Bearer YOUR_GPU_ROUTER_KEY

Create, list, and revoke keys in your workspace. Prepaid keys use your signed-in account. Wallet-managed earned-credit keys use a signature scoped to the gateway, network, action, and nonce.

Keep keys private

Use a server environment variable in production. The playground keeps keys in browser session storage, scoped to the gateway origin. Changing networks never sends another gateway’s key.

Compute Credits

Prepaid inference checks your available balance and API-key allowance; it does not require staking. Earned credits have separate eligibility requirements. The router reserves an estimate before dispatch, then settles the final bill and releases the unused amount. Reserved credits are already excluded from your available balance.