Billing and usage
Linked accounts, postpaid usage and exact AI charges.
Link a billing account to each project that uses paid products. Usage and invoice charges belong to that account. Each paid product must also be enabled for the project.
AI currently requires a USD billing account. AI has no upfront credit or monthly allowance hold. Verified actual usage is charged afterward, and the balance may go negative. Customer monthly caps stop new requests once settled usage reaches the cap; in-flight work may finish above it.
Read GET /v1/ai/tasks/{id} for exact billing.provider_cost_usd, charged_micros, the original price version and meter breakdown. Preserve decimal and micro-USD values without converting them through binary floating-point calculations. The account ledger uses micro-USD; $1 equals 1,000,000 micros.
A timeout or unknown provider outcome keeps billing pending for reconciliation. Never treat an interrupted response as a free request or start a replacement with a new key. AI pricing describes markup, caching and reconciliation.
Daily quota and requests-per-second limits constrain traffic; monthly spend caps constrain new AI work, while other paid products also enforce account credit. Setting one does not replace the others.