| summary | v0 Platform API billing and rate-limit usage from an API key. | ||
|---|---|---|---|
| read_when |
|
Enable v0 in Settings → Providers and enter an existing v0 Platform API key, or set V0_API_KEY for the CLI. The optional Scope field accepts a project ID or slug; the CLI equivalent is V0_SCOPE. Config stores these as apiKey and workspaceID for provider v0. Open Dashboard opens the account's billing settings.
The bundled JavaScript provider reads GET https://api.v0.dev/v1/user/billing and GET https://api.v0.dev/v1/rate-limits. Both requests use the same encoded scope, when configured. CodexBar's host attaches the bearer credential and restricts requests to https://api.v0.dev; the plugin needs no browser cookies or native networking adapter.
The Billing window shows the used share of the reported token-billing balance or legacy allowance. Token billing also shows the reported On-demand balance separately when available, including zero; it does not add that balance or its credit blocks to the Billing allowance or assign them the billing-cycle reset. The Rate limit window shows the reported request quota. Unknown remaining amounts appear as Unavailable, alongside the known limit, without an invented percentage. Reset times appear only when reported. Balances retain the API's units: CodexBar does not label them as dollars or infer a cost history.
An invalid key, denied scope, rate limit, unavailable service, or malformed response produces a classified error. The optional free-account daily allowance and grace period are not currently displayed.
API references: billing and rate limits.