Usage, Transactions, and Budgets
Read GPU and Serverless usage, understand settlement, and set account budget safeguards.
Usage versus transactions
Usage records explain consumption. Transaction history records wallet credits, holds, captures, releases, and charges. They answer different questions and should be reviewed together.
Serverless settlement
A serverless request may reserve an estimated amount before it runs and settle from reported usage after delivery. An eligible pre-delivery failure releases its reservation.
Budgets
Create daily or monthly budget controls in the dashboard. Budgets are safeguards, not a substitute for reviewing active resources and API-key use.
Investigate anomalies
Check active instances, recent API usage, and transactions before opening a support conversation. Do not delete audit evidence while investigating.
Published · Updated