CUDO Compute · Rate Limits

Cudo Compute Rate Limits

The CUDO Compute REST API is a control-plane API for provisioning and managing compute, storage, and networking resources. CUDO Compute does not publish numeric per-endpoint request-rate limits; practical constraints are governed by per-account and per-project resource quotas (number and size of virtual machines, GPUs, disks, networks, and public IPs), data-center capacity, and billing-account spend limits. Excessive control-plane request rates may be throttled by the platform. Specific numeric values are not reconciled in this artifact.

Cudo Compute Rate Limits is the machine-readable rate-limit profile for CUDO Compute on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring requests, virtual_machines, gpus, disks, and spend.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and unauthenticated.

Tagged areas include GPU, Cloud Compute, Infrastructure, Virtual Machines, and Marketplace.

5 Limits Throttle: 429
GPUCloud ComputeInfrastructureVirtual MachinesMarketplaceRate LimitingQuotasThrottling

Limits

API Requests account
requests
see provider documentation
Control-plane request throttling; numeric per-endpoint rate not publicly documented.
Virtual Machine Quota project
virtual_machines
see provider documentation
Number and size of VMs constrained by project quota and data-center capacity.
GPU Quota project
gpus
see provider documentation
Number of GPUs available subject to account standing and data-center capacity.
Storage Quota project
disks
see provider documentation
Disk count and size constrained by project quota and data-center capacity.
Spend Limit account
spend
account-configured
Billing accounts carry hourly and monthly spend limits and billing thresholds.

Policies

Resource Quotas
Provisioning is gated by per-account/per-project resource quotas and live data-center capacity rather than fixed request-rate limits.
Spend Limits
Hourly and monthly spend limits on the billing account cap resource consumption.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources