Skip to content

Machine Catalogs

Varity TeamCore Contributors

Varity Cloud exposes three machine catalog scopes. Capacity, regions, configurations, and GPU prices can change independently of this page, so the authenticated catalog and a fresh quote are the only current sources.

Catalogworkloadexecution_classCreate withAccessMonthly maximum
CPU VMsvirtual_machinecpu_virtual_machinePOST /api/machinesSSHWhen present in the quote
GPU VMsgpuvirtual_machinePOST /api/machinesSSHNo
GPU bare metalgpubare_metalPOST /api/machinesSSHNo

Both query parameters are required. Treat availability as a snapshot, not a reservation.

Terminal window
curl "https://varity.app/api/deployment-profiles?workload=virtual_machine&execution_class=cpu_virtual_machine" \
-H "Authorization: Bearer $VARITY_API_KEY"
Terminal window
curl "https://varity.app/api/deployment-profiles?workload=gpu&execution_class=virtual_machine" \
-H "Authorization: Bearer $VARITY_API_KEY"

Use execution_class=bare_metal for the other GPU scope. Read the selected profile’s identifier, resources, region, images, availability, and price fields from the response you receive. Do not copy a profile id or GPU rate from documentation into automation.

  • CPU VMs and GPU machines use POST /api/pricing/machine-quote.
  • The quote binds the current price and configuration and carries a valid_until deadline.
  • If the quote expires or any workload input changes, request another quote.
  • A catalog price is discovery data. The accepted quote is the price contract for the create request.