Skip to main content
Metering is the part of the request that turns provider output into a bill. Compose does it after execution, using the resolved catalog row and the usage or media evidence returned by the adapter. For text models, that usually means tokens. For media models, it can mean generated images, audio seconds, video seconds, or provider-specific units from the catalog pricing table.

Amounts

All settlement amounts are USDC atomic units. USDC has 6 decimals:
The final amount is:
The API applies a 1% platform fee on top of the raw amount. Our fees are the lowest in the space, minimum 5.5x times lower than other aggregators (e.g., OpenRouter charges 5.5%).

Meter subject

Meter subjects use the resolved provider and public model ID:
Examples:
The public model ID stays in the subject so receipts match what the client requested.

Line items

A metered quote contains one or more line items:
Units are normalized before settlement. The metering code supports per-unit pricing, per-1k and per-1m units, and time-based units such as seconds.

Authorization and settlement

Compose separates authorization from settlement: Audio requests can be quoted exactly up front when request-side billing metrics are known. Usage-priced text, image, and video calls usually use a budget cap and settle after output.

Quote a model manually

Use this endpoint when you need to inspect how a catalog row prices a known usage record.