Guides
Billing and budgets
Understand balance, usage, credits, subscriptions, and project budgets.
Overview
uouo cloud calculates cost from model pricing, input tokens, output tokens, and provider-specific routing. The console is the source of truth for logs, usage, and billing views.
Where to look
| Page | Use |
|---|---|
| `/app/credits` | Balance, top-ups, credits, and payment status. |
| `/app/subscription` | Subscription plan and quota status. |
| `/app/usage` | Usage trends, token totals, model mix, and saved views. |
| `/app/logs` | Request-level cost, latency, status, and model. |
| `/app/projects` | Project budgets, keys, members, and audit trail. |
Pay-as-you-go
For pay-as-you-go usage, requests deduct from the account balance according to model and provider pricing. The exact cost can vary by route, model, token count, and provider configuration.
Subscriptions
Subscriptions can provide fixed quota windows such as 5-hour, daily, weekly, and monthly limits. If a subscription quota is exhausted, the deployment may reject requests or fall back to balance depending on account settings.
Credits
Credits are a separate product balance used for eligible features such as credit-only subscription SKUs. Credits cannot be exchanged for USD.
Budgets
Use projects to isolate workloads and set budget policies. For production, create separate projects for dev, staging, and production so unexpected traffic is easier to find.
Troubleshooting cost spikes
- Filter `/app/logs` by model and key.
- Check token counts for long prompts and outputs.
- Look for retries or client loops.
- Review provider and model changes.
- Add or lower project budgets for risky workloads.