Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.sfcompute.com/llms.txt

Use this file to discover all available pages before exploring further.

An instance SKU (stock keeping unit) is a unique combination of node properties such as 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 capacity transfers are pinned to a single SKU id. Pass it with --instance-sku <id> or omit the flag to pick from a list. 
sf orders create --side buy --capacity dev --nodes 1 --start now --duration 1h \
  --max-rate 20.00 \
  --instance-sku isku_4UpxzQw7A8N

​
List instance SKUs

sf instance-skus list

NAME         INSTANCE SKU                PROPERTIES
sea-3-h100   isku_cxcwpDW93MaaBelmnLaez  Accelerator type: NVIDIA H100 (80GB HBM3), Interconnect: 400Gb/s InfiniBand, Zone: Seattle, WA
iad-12-h200  isku_NWhD6SrbjcXstGRvgl0eC  Accelerator type: NVIDIA H200 (141GB HBM3e), Interconnect: Standard 100GbE, Zone: Ashburn, VA

​
Get details for one SKU

sf instance-skus get isku_cxcwpDW93MaaBelmnLaez

​
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.

​
Browse the property catalog

Properties (accelerator_type, zone, interconnect_type, etc.) are drawn from a registry of allowed key/value pairs. Browse the catalog to see what each property means and which values exist. 
sf instance-skus properties list

sf instance-skus properties get accelerator_type
Add --json for the raw payload, same as GET preview/v2/instance_sku_property_catalog.

​
Deprecated and deleted values

Values move through stable, 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.