Rigetti Computing · Rate Limits

Rigetti Rate Limits

Documented rate-limit and concurrency policies for the Rigetti QCS API surface. Rigetti does not publish a public per-second request budget for the QCS HTTP API; the operational rate-limiting comes from (1) reservation-based time-boxed exclusive QPU access, and (2) engagement scope on the gRPC Controller service. The HTTP API does enforce standard HTTP throttling responses (429) with a Retry-After header on abuse.

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

It captures 3 rate-limit definitions, across the All QCS users tier.

The profile also includes response codes documented for throttled and quotaExceeded.

Tagged areas include Quantum Computing, QCS, Rate Limiting, and QPU.

3 Limits Throttle: 429 Quota: 429
Quantum ComputingQCSRate LimitingQPU

Limits

Account, billing, reservations, endpoints, and quantum-processor metadata endpoints. Token is valid 24 hours after issuance; abusive callers receive 429 with retry-after.
Execution is gated by engagement scope and QPU duty cycle. Only the active reservation holder can submit Controller jobs to a quantum-processor endpoint. BatchExecuteControllerJobs is the preferred high-throughput surface.
Quil-to-Controller-Job translation; pre-execution step. No documented public RPM.

Sources