All pages

Docs · AI features

Cred wallet

Availability: macOS (Settings → Account) · cloud workspace, which bills its minutes against the same credits.

The Account tab in Settings (⌘, → Account) is TRMNLY's hosted billing layer. Sign in once and it shows your credit balance, which pays for cloud workspace time and for agent turns on TRMNLY's own model keys. The wallet uses cred.diy under the hood.

Two ways to run a model, per model:

  • Your API key — the request goes straight from your Mac to the provider on a key you added (Settings → API Keys). Credits are never touched; an empty or signed-out wallet never blocks such a turn.
  • TRMNLY credits — the request goes through trmnly.dev, which calls the provider on TRMNLY's key and takes the turn's cost from your balance. No provider account needed. Available for Claude Opus 5.5, Sonnet 5.5 and Haiku 5.5, and GPT-5 and GPT-5 mini; the list and the rates come from trmnly.dev, so they can change without an update.

Pick in the model menu's Pay with section. With no choice made, a model runs on your own key when you have one and on credits otherwise — so a freshly paired Mac with no keys works at once. Choosing credits on an unpaired Mac refuses the turn and asks you to pair; it never quietly falls back to your key.

Sign-in and storage

There is no separate wallet login any more. The wallet resolves whoever this machine is paired to on trmnly.dev, so a GitHub-only account — which has no password to type — reaches the balance the server already tracks for it.

  • Pair the machine once (Settings → AI Agent → Remote Control on macOS, trmnly account login elsewhere). See Account & GitHub.
  • The device token is stored in the macOS Keychain. On Linux and Windows it is an owner-readable (0600) file under $XDG_STATE_HOME/trmnly — a libsecret backend is a seam in AccessKeySecrets, not something that ships today.
  • No plaintext copy on disk. Settings export omits it; a new machine pairs again.
  • Forget in Settings → Account stops showing the balance here. It does not unpair the machine — that lives in Settings → AI Agent → Remote Control.

Spending

What the wallet does depends on its state:

State What happens
notConfigured Build has no Cred backend secrets — nothing is metered. Dev builds.
signedOut The agent runs on your API keys; models set to credits are refused until you pair.
signedIn Shows the balance. Turns on your own keys are never charged; turns on TRMNLY credits are.

What a credits turn costs. Each model has its own rate: the provider's list price with a margin, converted at the pay-as-you-go credit price. Input, output, cache reads and cache writes are priced separately, rounded up once per turn, never below one credit. As a guide, 10,000 input and 2,000 output tokens on Opus 5.5 is about 15 credits; the same on Haiku 5.5 is one. The balance pill moves as the reply streams (a prediction from the same rates) and re-reads the settled figure when the turn ends.

Images. image_generate on credits is priced per image from OpenAI's list price with the same margin: 2 / 8 / 31 credits for a low / medium / high square, 3 / 12 / 45 for wide or tall. Your own OpenAI key is never charged.

Running out. A credits turn is refused before it is sent when the balance is empty or below a small per-model reserve, with the purchase sheet offered; a reply already streaming finishes. Your own keys keep working. At most four credits replies run at once per account.

Metering is server-side. trmnly.dev counts the tokens as they stream back through it and debits from that — nothing the app reports is trusted for a credits turn. Conversation content passes through trmnly.dev to reach the provider and is not stored there.

Purchase flow

Open Settings → Account, then Buy Credits. The sheet lists pricing tiers fetched from the backend; picking one opens a hosted Stripe checkout in your browser (not Apple IAP) and deep-links back to TRMNLY when it completes. Refunds and disputes route through cred.diy.

How it relates to API keys

  • API keys (Settings → API Keys) — your Anthropic / OpenAI / Google credentials. A model on your key goes straight from your Mac to the provider; the wallet is not in the request path and cannot block it.
  • Cred wallet (Settings → Account) — the balance that pays for models on TRMNLY credits (and for cloud workspace time). For those turns trmnly.dev is the request path, and an empty balance does block the next one.

In a dev build without Cred backend configuration (CredConfig resolves notConfigured), the wallet UI explains it's unconfigured and nothing is metered — useful when running TRMNLY built from source.

Privacy footprint

  • Cred's billing backend only sees per-turn credit amounts and the model id. On your own key, conversation content never leaves your Mac except to the provider. On TRMNLY credits it passes through trmnly.dev to the provider and is not kept there; your own API keys never leave your Mac either way.
  • Signing out clears the local Keychain entry but doesn't delete your account or balance — sign back in from any Mac to resume.