Docs65 bps$200 floorChain 4663
Open the terminal
Take payment/Compute credit

Compute credit

Convert a marker onto the compute rail, lock a vendor and a model, then mint an owed_ key. The key is that vendor’s real contract. Usage burns the remaining cents.

Mint a key

  1. Convert at least $1.00 of owed balance to the compute rail.
  2. Open Settle, pick compute, then lock a vendor and a model.
  3. Enter an amount. The spend cap equals that amount. A $1.00 key can spend at most $1.00.
  4. Copy the key. It is displayed exactly once.

Redeeming locks the vendor for that key. Tokens past the cap are rejected upstream of the model, so you cannot accidentally run a bill. The desk’s own OpenAI, Anthropic, Google, and other credentials stay on the server — you never see them and never paste them.

Vendors and models

VendorModels you can lock
Anthropicclaude-opus-4-6claude-sonnet-4-6claude-haiku-4-5
OpenAIgpt-5.2gpt-5.2-minio4
Googlegemini-3.0-progemini-3.0-flash
DeepSeekdeepseek-v4deepseek-reasoner
xAIgrok-5grok-5-mini
Mistralmistral-large-3codestral-2
Metallama-5-405bllama-5-70b
Coherecommand-a-2command-r-plus
Perplexitysonar-pro-2sonar-reasoning
Moonshotkimi-k3kimi-k3-turbo

Shown once

The full owed_ key is shown once, at mint. After that the desk stores only a prefix and a hash — enough to meter and to revoke, not enough to reconstruct. Leave the page without copying it and the credit is not lost: you mint a new key from whatever is left on the rail. The old plaintext is simply gone.

There is no “show key again” button and no support flow that can recover one. That is a deliberate design choice, not a missing feature.

Revoke

Revoke a key from the key list. The gateway rejects that prefix on the very next request. Unused cap on a revoked key does not come back as owed balance — revoking is a security action, not a refund.

Metering

  • Requests are priced on the vendor’s published token rates.
  • Every request rounds up to the nearest cent.
  • A request that would exceed the remaining cap is refused with 402 before it reaches the model.
  • The key list shows cap, spent, remaining, request count, and last use for every key.

Point the official SDK at this origin — see API reference. Or stay on the desk and use compute chat.