Key history
Every key keeps a record of the work it did. On studio.resourcepack.ai/developers, press History on a key to see each action with its pack, asset and cost. The button appears once the key has done something.
| Recorded | Not recorded |
|---|---|
| Generating, regenerating or editing anything | Polling a job |
| Uploading, duplicating or deleting an asset | Listing packs, assets or the gallery |
| Moving or copying assets to another pack | Downloading an asset file or a version |
| Restoring an earlier version | Reading settings |
| Creating, importing, exporting, changing, duplicating or deleting a pack | Filing assets in folders |
| Changing the style guide, a model's or a sound's settings | Changing who you are told about |
| Pushing to Minecraft, or giving an asset in game | Linking a player to receive pushes |
| Publishing a release, or changing distribution | |
| Inviting, changing or removing a collaborator | |
| Publishing to the gallery, or copying from it |
Reads aren't recorded because a polling loop would bury the few lines that matter under hundreds of "still generating" checks.
The cost shown is what was actually charged, not what was reserved up front. A generation that failed and was refunded, one covered by your own BYOK key, and a free action all show no cost.
Revoking a key keeps its history.
If a key leaks
Revoke it from the Developers page. A revoked key stops working on the next request. Then read its history to see what it did while it was out. Keys can't create other keys, so a leaked key can't extend its own life.