CH·02CLI reference

gpu billing deposit

Add funds to your account balance by card or stablecoin

Add funds to your account balance by card or stablecoin

Synopsis

Pick the funding method with --card or --crypto. Exactly one is required: the method is explicit so that adding a method never changes what an existing command does.

gpu billing deposit --card --amount <usd> [--payment-method <pm_id>] [--checkout] [--yes] [flags]
gpu billing deposit --crypto --chain <network> --asset <token> --amount <usd> [flags]

By card (--card)

Two paths, chosen for you:

  • Saved card, right in the terminal. If your organization has a saved card
and your API key holds the payments:write scope, the command shows the charge (amount, card brand and last 4 digits), asks you to confirm, and charges it. The balance is credited a few seconds later and the command waits until it is. If your bank asks for 3-D Secure, the command prints a link (and opens it) so you can finish in the browser; it keeps waiting meanwhile.
  • Stripe Checkout, in the browser. With no saved card yet, a key without
payments:write, or --checkout, the command opens the same Stripe Checkout page as the dashboard's "Add credits" and waits for the payment. Paying there saves the card, so the next top-up can stay in the terminal.

Rules worth knowing:

  • Admins only, like the dashboard's card payments. The minimum is $5.00.
  • Who can charge a saved card. The key gpu login issues to an org admin
(full_access) can. Member keys (standard) and read_only keys cannot, and neither can a member holding any key: the server also checks that the key's owner is an admin. Custom keys need the scope map {"payments":"write"} (add "billing":"read" so the same key can watch the deposit land). Without it, --card still works, through Checkout.
  • Limits. Through the CLI/API, one card top-up is at most $10,000, and
saved-card charges are at most $25,000 per organization in any 24 hours. Over a limit, nothing is charged and the error says how much is left; add larger amounts in the dashboard. Declined or canceled charges do not count, and a charge left waiting for 3-D Secure stops counting after an hour. Checkout from the CLI has the per-charge limit but does not count toward the 24-hour one (you pay on Stripe's page).
  • It can be switched off. If saved-card charging from the terminal is
turned off (an operator kill switch), --card says so and opens Checkout.
  • Nothing is charged without a yes. The prompt accepts only y or yes.
A non-interactive run needs --yes, and so does --output json (the prompt would corrupt the JSON). --checkout needs no --yes: you confirm on Stripe's page.
  • Retries never double-charge. Each invocation sends one idempotency key,
reused if the command has to retry after a dropped connection, so a retry replays the first attempt. Running the command again is a new top-up.
  • Deposit match. A card top-up from the terminal earns any running
deposit-match promotion exactly like a card deposit on the website, including the card hold before matched credit is released. The final status shows what the promotion decided.
  • Card numbers are never shown or stored by the CLI, only brand and last 4.

By stablecoin (--crypto)

Creates a deposit and prints the address to send to and the exact token amount to send. Send that amount, of that asset, on that network, and nothing else.

Three things are worth reading twice before you hit send in your wallet:

  • The network is not a suggestion. The address accepts the named asset on
the named network only. USDC sent to a Base address over Ethereum, or over Arbitrum, is not detected and generally cannot be recovered. The command prints a one-line network warning under the table for exactly this reason.
  • The address belongs to this deposit. Each deposit gets its own address.
Sending to an address from an earlier deposit does not credit automatically — it becomes a support ticket.
  • Send the exact amount. Your balance is credited with the value that
actually settles, so a wallet that deducts the network fee from the amount sent will land you slightly short. Short deposits are still credited, at what arrived; see the guide.

The minimum deposit is $5.00 by default — the deployment may set a different floor, and an under-minimum create is rejected with an error naming the current one. Any member of the org may add funds — this is not admin-gated.

Examples

# $50 by card: charges your saved card after a confirmation, or opens Checkout
gpu billing deposit --card --amount 50

# Same, approved up front, machine-readable (returns without waiting)
gpu billing deposit --card --amount 50 --yes --output json

# Pay in the browser even though a card is saved
gpu billing deposit --card --amount 50 --checkout

# Charge a specific saved card
gpu billing deposit --card --amount 100 --payment-method pm_1Pxyz

# $50 of USDC on Base
gpu billing deposit --crypto --chain base --asset usdc --amount 50

# $250 of USDT on Ethereum, machine-readable
gpu billing deposit --crypto --chain ethereum --asset usdt --amount 250 --output json

# Pull just the address and amount out for a wallet CLI
gpu billing deposit --crypto --chain base --asset usdc --amount 50 \
  --output json | jq -r '"\(.pay_amount) to \(.pay_address) on \(.chain)"'

Options

      --amount float            Amount to deposit in USD (minimum $5.00; the server enforces the live floor)
      --asset string            --crypto: stablecoin to send: usdc|usdt
      --card                    Fund by card: charge a saved card, or pay with Stripe Checkout
      --chain string            --crypto: network to send on: ethereum|base|arbitrum|polygon|solana
      --checkout                --card: pay in the browser with Stripe Checkout even if a card is saved
      --crypto                  Fund with a stablecoin deposit
  -h, --help                    help for deposit
      --no-browser              --card: print the Checkout / 3-D Secure link without opening a browser
      --no-wait                 --card: return right away instead of waiting for the deposit to be credited
      --payment-method string   --card: saved card to charge (pm_...); default is the card auto-pay uses
      --timeout duration        --card: how long to wait for the deposit to be credited (default 15m0s)
  -y, --yes                     --card: approve the saved-card charge without a prompt (required with --output json)

Not every network/asset pair is enabled on every deployment. An unavailable pair returns a validation error naming the chain/asset combination as unsupported rather than silently issuing an address you cannot use.

Output (--card)

FieldMeaning
deposit_idStripe PaymentIntent (pi_...) or Checkout Session (cs_...) id. Use it with gpu billing deposits get .
methodsaved_card or checkout.
statussucceeded, processing, requires_action (open action_url), or awaiting_payment (open checkout_url).
amount_centsThe amount charged or to be paid, in cents.
card_brand / card_last4The saved card charged. Never a card number.

Output (--crypto)

FieldMeaning
deposit_idUse it with gpu billing deposits get .
statusLifecycle state — starts at created, ends at credited.
pay_addressWhere to send. Unique to this deposit.
pay_amountThe exact token amount, as a decimal string (never a float — the precision matters).
chain / assetThe network and token this address accepts. Nothing else.
amount_usd_centsWhat you asked to deposit, in cents. Not what settled.
credited_centsWhat actually landed on your balance. Absent until credited.
expires_atAfter this, do not send to pay_address — create a new deposit.

Options inherited from parent commands

      --api-base string   API base URL (override with GPUAI_API_BASE env) (default "https://api.gpu.ai/v1")
      --debug             Enable debug logging to stderr
  -o, --output string     Output format: table|json (default table on TTY, json otherwise)

SEE ALSO

← The gpu CLI