JarvisLabs · Rate Limits

Jarvislabs Rate Limits

JarvisLabs does not publish explicit numeric request rate limits for its instance-management API in public documentation. In practice, capacity is governed by real-time GPU availability (surfaced via `jl gpus`), per-account concurrent instance and GPU-count limits (up to 8 GPUs per instance), and wallet balance / grants rather than by request-per-minute throttling. Specific per-account values are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring instances, gpus, and balance.

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

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

4 Limits Throttle: 429
AIGPUCloudInfrastructureComputeRate LimitingQuotasThrottling

Limits

Concurrent Instances account
instances
see provider dashboard
Number of simultaneously running instances per account; not publicly numbered.
GPUs Per Instance instance
gpus
8
Up to 8 GPUs can be attached to a single instance / deployment.
GPU Availability region
gpus
real-time
Launch success depends on live GPU availability per type and region (jl gpus).
Wallet Balance account
balance
prepaid
Usage is gated by prepaid wallet balance and any account grants.

Policies

Capacity-Gated Provisioning
Instance creation is constrained by real-time GPU availability per type and region rather than fixed request quotas.
Backoff Strategy
Clients should implement retry with backoff on capacity errors and honor any Retry-After headers.

Sources