What was spent over a time window, grouped by atomic op, by API key, or by UTC day, with the window's total beside the groups:

• jobs — jobs created in the window
• credits and items — what those jobs were charged and how many of their items settled, so far
• sync — synchronous calls (/images/transform, /images/render) that succeeded and so cost an op from the allowance; never counted in jobs. /images/metadata is free and not counted

A job submitted as a raw type groups under that type; a console session, which has no key, groups under console. Days are UTC. Usage lives as long as the job records it comes from, so a window older than the plan's retention reads short.

USE THIS WHEN:

• An agent has a budget and needs to know what it has spent, and on what
• Attributing cost across several keys (one key per agent is the usual shape)

DO NOT USE WHEN:

• You need one job's own cost → GET /api/v1/jobs/{id} (actualCredits, and credits per item)
• You need every credit movement, top-ups and refunds included → the credit ledger, which a signed-in console session reads and an API key cannot