> ## Documentation Index
> Fetch the complete documentation index at: https://veryfront.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Billing and Usage API

> How subscriptions, credits, budgets, usage, and limits relate.

The Billing and Usage API manages subscriptions, payment details, credits, spending limits, and usage reports. These resources describe both available capacity and recorded consumption.

## Subscriptions and credits

A subscription determines plan features and resource limits. Credits pay for supported consumption and can come from a monthly allocation or purchased balance.

Payment methods, invoices, checkout sessions, and credit transactions record different parts of the billing lifecycle. A usage total is not an invoice or a payment record.

## Budgets

A budget caps monthly AI spending for a project, person, API key, or combination of these fields. A request matches a budget when it matches every configured scope field.

Creating or changing a budget does not reset usage already recorded that month. Multiple budgets can apply to a request. Account credit and other spending checks still apply.

## Usage and attribution

Usage reports group consumption by the dimensions supported by the operation, such as project, member, model, or API key. Some account-wide totals are exposed through a project-scoped endpoint; the reference identifies that scope explicitly.

Unattributed usage means that caller information was not recorded. Missing deployment metadata does not establish where inference ran.

## Quotas and reporting scope

A quota describes the capacity allowed for a resource; credits describe available balance for supported consumption; a budget limits AI spending for its scope. A positive credit balance does not imply every quota has remaining capacity.

For a scheduled support-summary task, a representative run can help estimate repeated consumption. Compare matching resource types and reporting periods, and check whether the response covers one project or the whole account.

## API key and model limits

Per-key inference limits can narrow allowed models and request rates within project policy. The [AI Gateway API](/docs/cloud/apis/ai-gateway) describes policy and enforcement behavior. The [Identity and Access API](/docs/cloud/apis/identity-and-access) manages the keys themselves.

## Get started

[Check usage and limits](/docs/cloud/billing) shows how to read account consumption and quota information.

## API references

* [REST endpoints](/docs/cloud/rest/apis/billing-and-usage-api)
* [GraphQL queries and mutations](/docs/cloud/graphql/apis/billing-and-usage)
* [MCP tools](/docs/cloud/mcp/apis/billing-and-usage)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.