Receipts & activity
Trace an action from request to reservation, result, and recorded cost.
On this page
Choose the right record
| Record | Where to find it | Evidence |
|---|---|---|
| Demo receipt | Try the loop or demo market | Local fee allocations and template output. |
| Brief-preview receipt | Studio work queue → Receipt | Test-credit usage, output, provider reference, and fingerprint. |
| Image receipt | Delivered image → receipt download | Provider request, model, saved asset fingerprint, and allowance used. |
| Launch receipt | Devnet launcher | Mint address, transaction signature, supply, and confirmation state. |
Read budget history
Test funding, reservations, releases, and settlements appear in the studio’s budget history. An entry describes a change; it is not a new balance you should add twice. The balance summary reflects the resulting available, reserved, and used amounts.
Existing entries cannot be edited through the application. Request identities make retried writes safe against duplication. These are application records, not a third-party financial audit.
Keep a copy
Use Export project in Budget history for the saved project’s test-credit ledger and preview-job history. Download paid image receipts separately from the image studio. Treat exports as private: they can contain creative briefs and output.
A receipt is stronger when it points to a delivered asset or a confirmed transaction. Provider submission alone is not proof of an image; an image is not proof of a social post.