Skip to main content
Keep access material separate from instance requests. AI Reserve stores public SSH keys and encrypted registry credentials as organization resources that you can reference from future launches.

​
SSH keys

For a one-off launch, pass a local public key file directly:
For a reusable organization key:
Reference the returned key ID at quote or launch time with --ssh-key-id. Revoking a key excludes it from subsequent starts; it does not end an existing SSH session on a running instance.
Upload public keys only. Never pass a private key, password, or secret through --public-key.

​
Private container registries

Add a credential once, then reference its ID from instance requests:
The CLI reads the password from a protected prompt or standard input; it does not accept the password as an argument. Secrets are encrypted at rest and never returned by list or get operations.
Rotate or remove a stored credential with:
An active resource can block rotation or deletion while it still references the credential.

​
Usage and charges

Usage records are immutable compute and storage billing windows. See Billing timeline for accrual semantics and use the generated API Reference for exact SSH key, registry credential, and usage schemas. Templates remain available primarily for the provider-shaped Pods compatibility flow. The normalized Instances request does not currently accept a template ID; pass an image and workload settings explicitly instead.