Manage GPU rentals and projects with ispeed ctl

Inspect offerings and submit deliberate account-scoped changes using JSON request files.

Before you start

Authenticate the CLI and select the account to own and pay for resources. Provisioning and lifecycle commands change real services.

Steps

List projects, services, GPU offerings, and existing instances before creating anything.
Prepare the request JSON from the current API options; use only compatible images, hardware, and provider network settings.
Use --dry-run on supported mutations to validate local JSON and inspect the method/path without submission.
Submit the provision request once, then inspect the resulting instance and its status.
Use a lifecycle command to stop an intended instance only after saving work, and verify billing and storage behavior afterward.

Example

ispeed-ctl projects list
ispeed-ctl gpu offerings
ispeed-ctl gpu list
ispeed-ctl gpu provision --body-file rental.json --dry-run
ispeed-ctl gpu action INSTANCE_ID stop

Check the result

The created resource appears under the selected account and project with the expected configuration.

Troubleshooting

A dry run does not verify live price, capacity, remote authorization, or application readiness. Do not put tokens in shared JSON files or automatically retry purchases.