Developer billing and usage
Use billing:read for protected reads under /v1/billing: /wallet, /ledger, /limits, /usage, and /invoices. /pricing is public. Check the selected workspace when an operation accepts workspace_id.
Read before automating
Section titled “Read before automating”Use /limits to inspect active allowance and usage. Wallet values such as balance_micros, monthly_credit_micros, and available_micros are expressed in millionths of a dollar. Treat credits and cash balance according to the returned fields rather than adding every field together blindly.
The current pricing service and the account view determine rates and credits. Old universal per-edit or per-publish prices are not a current contract. Building, model activity, and running services can have different usage behavior.
The October 2, 2026 rollout introduces a usage tariff of twice the underlying provider or infrastructure cost as usage policies are upgraded. Applicable provider funding fees are included before the tariff. Previously admitted operations and their recorded charge retries retain their original prices. A pricing-policy change does not add wallet funds or clear owner limits.
Upgraded Pro wallets use a $25 in-app AI spending ceiling per UTC calendar month, shared by their apps, with separate provider-cost and request ceilings. Lower owner limits and Pause still apply. Wallets awaiting the upgrade retain their previous cumulative limits. See the current limits and transition before sizing an automated workload. Hosting usage arrives after activity occurs, so its spending limit is not an immediate dollar ceiling.
Billing mutations
Section titled “Billing mutations”The registered routes include /topup, /subscribe, and /payment-method; they require billing:write for keys. These can affect charges or account settings. Use the account’s billing flow unless you have verified the current request fields and confirmation behavior for your integration.
Do not assume every write supports a universal idempotency contract. Cash top-up flows have their own request-key requirements. Inspect current behavior before retrying a charge after an ambiguous response.