accelerator_type and interconnect_type. Two nodes with the same SKU are interchangeable, so the
market treats them as one pool for pricing and allocation. Each SKU has a stable id (isku_...)
and a human-readable name set by the operator who registered it.
Orders, procurements, and
pool transfers are pinned to a single SKU id. Pass it with
--instance-sku <id> or omit the flag to pick from a list.
List instance SKUs
--verbose to see every property column (interconnect type, zone, etc.).
Get details for one SKU
Interactive picker
Run any command that accepts--instance-sku (e.g. sf orders create, sf procurements create)
without the flag to pick a SKU from a list of registered SKUs and their properties.
Deprecated and deleted values
Values move throughstable, then deprecated, then deleted. Deprecated values stay usable for a
grace period and include a migration message. After deletion, new SKUs cannot be registered with
that value. SKUs already pinned by existing orders keep matching as long as they’re alive, but the
SKU pool drains as inventory turns over. Move workloads to a replacement value before the registry
entry is removed.