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 credit 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 usage tariff is 1.5 times the underlying cost of our build agent’s turns (its model and container time) and of AI inside your apps. Other metered infrastructure, such as in-app agent containers, agent tool calls, workflows and processors, is charged at twice its underlying cost. Applicable provider funding fees are included before the tariff. Previously admitted operations and their recorded charge retries keep their original prices. A pricing-policy change does not add wallet funds or clear owner limits.
In-app AI has a spending ceiling per UTC calendar month, shared by a wallet’s apps: $25 on Pro and $8 on Go, with separate provider-cost and request ceilings. Builds and private previews are charged at 0.5 US cents a minute, at most $0.10 a build. Lower owner limits and Pause still apply. See the current limits before sizing an automated workload. Publishing and hosting are not charged to the wallet.
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.