Cloud Agent usage and billing

Understand the durable boundaries between compute, Wallet, Clawdi AI usage, and external provider usage.

Cloud Agent costs can come from two separate activities: running the remote compute and using a model service. Keep those boundaries separate when choosing a plan or investigating a charge.

Billing concepts

Surface	Scope	What it represents
Compute	Per Cloud Agent	Resources and funding for that Agent’s remote runtime.
Wallet	Account-wide	One balance used for Clawdi AI and for compute when Wallet funding is offered and selected.
Usage	Account-wide reporting window	Clawdi AI spend and requests, including model and daily breakdowns when available.
External AI Provider	Provider account	Model usage made with a saved or in-Agent provider configuration.
Billing portal	Account payment account	Supported card payment methods, invoices, and subscription billing details.

The Usage page reports Clawdi AI activity for its displayed reporting window. Wallet balance is not reset with that reporting window. For an external AI Provider, use that provider’s own usage and billing surfaces as the source of truth.

Review current compute offers

Compute resources, prices, included capacity, billing terms, payment methods, and availability can change. For exact current information, use:

• The Compute section of the Cloud Agent deployment wizard for a new Agent.
• The Compute plan section in an existing Cloud Agent’s Settings.
• Settings > Compute in the dashboard for current plan information.

These product surfaces show the exact amount and confirmation before a paid action. This documentation intentionally does not reproduce a price or promise that a particular plan or payment method is available to every account.

Use Wallet safely

Open Settings > Wallet to review the current balance, top up, inspect activity, and manage auto-reload when available. When a paid compute action uses Wallet, confirm the exact debit and balance-after amount shown in its fresh quote.

If the balance changes, a quote expires, or the product reports a shortfall, top up as needed and request a new quote. Do not confirm an old amount after the product asks for a fresh quote.

Understand stop, delete, and subscriptions

• Stop pauses the remote runtime; it does not itself cancel a paid compute subscription.
• Compute plan and subscription controls live in each Cloud Agent’s Settings and can depend on current Agent and subscription state.
• Delete permanently removes the Agent. When the deletion dialog offers a separate subscription choice, review it explicitly; do not assume Agent deletion always selects the desired subscription outcome.
• A plan change can be immediate, scheduled, or still awaiting confirmation as shown in the dashboard. Do not submit a second plan change while the first is unresolved.

For billing-related deployment failures, first check the Agent status and Wallet activity. Top up only through the dashboard, obtain a fresh quote, and then use the remediation presented by the failed action. See Cloud Agent troubleshooting.