Usage
Retrieve consumption and usage data per project for monitoring and billing reconciliation.
The usage endpoints report consumption — the metered resource use that underpins billing. Silos meters usage-based resources such as compute time, storage, and data transfer, and exposes them per project.
The API is stabilizing. The paths below reflect the current interface; field-level details may still change before general availability. Use these endpoints for monitoring and reconciliation rather than as a billing system of record.
Usage across projects
GET /v1/usage/projects
Return consumption summarized across your projects.
curl https://api.silos.sh/v1/usage/projects \
-H "Authorization: Bearer $SILOS_API_KEY"{
"projects": [
{
"project_id": "proj_abc123",
"period": {
"start": "2026-06-01T00:00:00Z",
"end": "2026-06-30T23:59:59Z"
},
"usage": {
"compute_seconds": 12450,
"storage_bytes": 524288000,
"data_transfer_bytes": 104857600
}
}
]
}Usage for one project
GET /v1/projects/{id}/usage
Return consumption for a single project.
curl https://api.silos.sh/v1/projects/proj_abc123/usage \
-H "Authorization: Bearer $SILOS_API_KEY"{
"project_id": "proj_abc123",
"period": {
"start": "2026-06-01T00:00:00Z",
"end": "2026-06-30T23:59:59Z"
},
"usage": {
"compute_seconds": 12450,
"storage_bytes": 524288000,
"data_transfer_bytes": 104857600
}
}What's metered
Silos uses a usage-based model. Because compute scales to zero when idle, you're not charged for compute while a database is suspended. The metered dimensions are:
Compute
Time spent actively serving queries, reported in compute-seconds.
Storage
Durable state held as snapshots and WAL in object storage, in bytes.
Data transfer
Bytes moved in and out, in bytes.
For pricing and plan details, see Pricing & billing. The exact metered fields and their names are part of the API that is still stabilizing.