Skip to main content
GET
Rows are sorted by createdAt, oldest first. Every generation is listed, failed ones included, so the list matches your own logs line by line. The CSV is also in the dashboard: Generations, Export CSV, then a month under “Credits charged per generation”.

Query

string
ISO 8601 timestamp. Only generations created at or after it.
string
ISO 8601 timestamp. Only generations created before it.
number
default:"100"
1 to 1000. GET /usage only.
string
nextCursor of the previous page. GET /usage only.
Without from and to, you get every generation of the account.

Response

GET /usage returns { items, nextCursor, hasMore, count }. nextCursor is null on the last page. Each item:
string
required
The generationId returned by Create Try-On.
string
required
When the try-on was requested. from and to filter on this field.
string | null
required
When it completed or failed. null while it is running.
string
required
PENDING, PROCESSING, COMPLETED or FAILED.
number
required
Credits charged. See the table below.
string | null
required
Set for batch items.
string | null
required
The API key that made the call. null for try-ons made without a key (the MCP server) and for calls made before 2026-11-14.
GET /usage/export returns text/csv with a header row and these columns: generation_id, created_at, completed_at, status, credits, batch_id, api_key_id. It is not paginated.

What credits holds

A batch is charged half the credits of its completed items, rounded up once for the whole batch. The sum of credits over a batch’s items can therefore be 0.5 under what the batch was charged. The sum of credits over a period is what your generations cost in that period. A plan’s allowance follows your billing period, which may not start on the 1st: set from and to to the period dates on your invoice.