BLAZINGFAST — STORAGE VOLUMES
Reviewed: 5 October 2026. Setup: 00-index.txt.
Production release: SDK/CLI 0.1.17; contract 2026-10-07.1. Check GET /v1/version and GET /v1/capabilities before using optional workflow features. Strict response validation is enforced.

PURPOSE
Additional provisioned storage capacity attachable to compatible VPS services.
A volume is not a backup. Discover valid attachment targets rather than assuming
any VPS, region or dedicated server can accept it.

PUBLIC API
GET /v1/storage/volumes: owned volumes and allocation/attachment information.
GET /v1/storage/volumes/{serviceId}/attach-options: eligible targets.
POST .../attach with targetServiceId; POST .../detach; POST .../rename with name.
Permissions: storage.read / storage.write plus ownership/project access.

CLI / SDK
Use bf (bf-api remains an equivalent supported alias):
bf storage list
bf storage attach-options SERVICE_UUID
After selecting an eligible target and confirming the change:
bf storage attach SERVICE_UUID --target-service-id TARGET_SERVICE_UUID --confirm
bf storage detach SERVICE_UUID --confirm
bf storage rename SERVICE_UUID --name archive-volume --confirm
List/attach-options require storage.read; writes require storage.write and owned
resources. Python, Node.js, PHP and Go SDKs expose the corresponding methods.

MCP
Hosted: list_storage_volumes, get_storage_attach_options,
request_storage_attach, request_storage_detach, request_storage_rename.
Local: bf_storage_volume_list only; no local attach/detach/rename tools.

LIMITS AND SAFETY
Inspect mount/filesystem use before detaching; detach can interrupt disk access.
Capacity fields describe allocated space. Missing usedBytes is unavailable usage,
not an empty volume. Guest filesystem preparation may still be required.
Customer object/S3 storage is not advertised by this customer volume API.
See the separate backup brief for recovery and retention workflows.