Backed by: @pithy-sh/media and @pithy-sh/storage, their GET {basePath}/admin/usage, answered by your own Worker. Scopes: media:usage:read, storage:usage:read.
What it shows
Media and storage are the capabilities it reads, and the control-plane scopes say why a per-owner figure is always one organization’s.
What your media and storage hold, in records and bytes, read live from your Worker. It appears in the rail under Operations when your Worker composes either capability, at whatever path you mounted it. Each side stands alone: a Worker that composes storage and not media shows a storage column and nothing about media.
The index is one row per organization, largest first, with media and storage side by side on the row. Records written with no organization in force are the No organization row. A side that holds nothing for an organization says nothing, or not among the rows shown when its read was truncated and the organization may hold records past them.
The record
With no row chosen, the record is the project’s sum on each side: records and bytes, labelled Sum. It says how many organizations it adds up. When a read was truncated, the sum says it covers only the organizations shown, and that it is not the project’s total.
Choose an organization and the record lists its owners on each side, largest first, as your Worker sent them. A row with no owner is labelled System, never as a person. When the owners read was truncated, the record says these are the largest owners only.
Sizes are in decimal units, in your locale. A record of unknown size counts zero bytes, as the kit counts it, and the record says so.
Per organization, never across them
That is the kit’s rule, not a layout. Your Worker refuses a per-owner read with no organization named, because a per-person total summed across organizations would disclose that the person holds an account elsewhere. So the pane asks for owners only with an organization named, and only for an organization the index listed: a hand-edited address names nothing it will read.
A query your Worker refuses as malformed, validation/invalid_input, is drawn with your Worker’s own sentence. For that code, and only for this pane’s reads, the dashboard reads your Worker’s error body: at most 4 KB, kept only when it parses as the kit’s public error payload with that code, and never on a 401 or a 403. Every other failure is drawn with our own sentence.
Read once, held nowhere
The pane reads when you open it, on the current connection, and keeps nothing. Each answer is parsed with core’s own usage schema, not cached, and held in no Pithy table. A response that does not parse fails on screen, naming the environment.
A connection without a side’s scope is refused by name on that side, and nothing is sent for it. The other side still answers. Both scopes are reads, so they are in the default grant; Scopes has how to add one to a connection made before it existed.
It reads, and it never writes
Raising an owner’s headroom and deleting a record are not buttons here. The pane counts what is held, and does not split it into images and video, because the usage read does not. What your images and video were served is Delivery.