Install-wide storage usage rollup
GET /admin/storage/usage
Read-only admin view of what storage holds (#402): distinct objects, variant rows, total bytes on disk, the originals-vs-derivatives split, and breakdowns by content type and backend.
total_bytes is DEDUPLICATED on-disk bytes — storage is
content-addressed, so a byte counted once is a byte stored
once. It is summed from storage_variants alone: that table
already carries one row per object under variant_key
original mirroring the object’s size, so adding
storage_objects on top would double-count every original.
Aggregates only, so no paging. Gated on system.storage.read
(or system.admin). No write path.
Authorizations
Section titled “Authorizations ”Responses
Section titled “ Responses ”Storage usage rollup.
object
Distinct content-addressed objects.
Total variant rows (every rendition of every object, including the original).
Deduplicated bytes on disk. Summed from storage_variants alone — see the endpoint description.
Bytes held by the original variant of every object.
Bytes held by every non-original variant (previews, turntables, HLS segments, …).
object
Example
image/pngobject
Example
fsAuthentication required, missing, or invalid
object
Human-readable error summary
Example
the request could not be completedExample
{ "error": "authentication required: sign in and retry with a valid session or API token"}Authenticated but missing required capabilities
object
Human-readable error summary
Example
the request could not be completed