Shadeform · Rate Limits

Shadeform Rate Limits

The Shadeform REST API authenticates every request with an X-API-KEY header. Specific published request-per-minute or request-per-day limits for the control plane are not documented in the public API reference. The more meaningful limits in a GPU marketplace are capacity-driven: real-time GPU availability per cloud, region, and GPU type (surfaced via GET /instances/types), and any per-account concurrent-instance or quota caps applied to a given account or tier. Specific values are not reconciled in this artifact.

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

It captures 3 rate-limit definitions, measuring requests, capacity, and instances.

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

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

3 Limits Throttle: 429
GPUCloudMarketplaceComputeInfrastructureRate LimitingQuotasThrottling

Limits

Control-Plane Requests account
requests
see provider documentation
No specific RPM/RPD published for the management API; verify in dashboard.
GPU Availability marketplace
capacity
real-time, per cloud / region / GPU type
Launch success depends on live availability; query GET /instances/types with available=true.
Concurrent Instances account
instances
see provider documentation
Per-account concurrent instance / quota caps may apply by tier; not reconciled.

Policies

API Key Authentication
Every request must carry a valid X-API-KEY header issued from the Shadeform dashboard.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Availability-Aware Retries
When a launch fails for lack of capacity, re-query instance types/availability and retry against an available cloud, region, or GPU type.

Sources