sdk client and an authenticated MKA1 CLI.
Inspect an accelerator
Use a name returned by the accelerator catalog.Inspect offers
Availability is an observation, not a reservation. Detailed offer and provider discovery can be unavailable on deployments that hide provider information; use the public quote operation in that case.Inspect providers
Provider entries describe the configured backend; they do not promise capacity for a particular job.List jobs
Read the first page. For subsequent pages, pass the returnednext_cursor as cursor until it is null. The SDK does not automatically traverse these lists.
List services
Use the same cursor pattern for services.Inspect job instances
Instance observations describe the hardware associated with a job; use them alongside lifecycle events when diagnosing provisioning.Read service logs
Usesource=user for application output or source=system for allocation and bootstrap output. Pass next_cursor as cursor to read more.
Read service events
Events describe lifecycle transitions. They are distinct from your server logs.Inspect service instances
Inspect the observed instances for this service.List secrets
Only names, IDs, and key names are readable; stored values are not returned.Inspect a secret
Use the returned key names when configuringcontainer.secret_env.
Delete a secret
Delete a secret only when it is no longer needed for new workloads or provisioning. This removes the stored credential; it does not terminate existing jobs or services.Create a shared volume
Standalone volumes provide persistent shared storage on compatible placements. Confirm your deployment supports this capability before using it; a volume is not portable to every GPU provider. Creating and retaining storage can accrue charges independently of jobs.List volumes
Volumes are scoped to your organization.Inspect a volume
Check volume state before launching a workload that depends on it.Inspect volume attachments
Attachments show the workloads that reference a volume.Delete a volume
This permanently deletes its data. Terminate attached workloads and wait for their attachments to become terminal first; deletion is refused while non-terminal attachments exist.Mount a volume in a workload
Add the following field to the complete job or service creation body from the workload guides, using a placement compatible with the volume:Volume mount field
volumeId and mountPath; Python uses volume_id and mount_path.
C# uses ComputeStandaloneVolumeMount with VolumeId and MountPath.
Your container must read and write under the mount path to use persistent storage.
For workflows on external GPU capacity without compatible volume support, publish artifacts to repositories.
Usage and administration
Use the job usage or service usage examples; selectvolume as the resource type to inspect volume usage where supported.
Tenant enablement and pricing administration require elevated permissions. Their complete schemas are in the Compute Tenants and Compute Pricing groups of the API reference.