IonQ · Rate Limits

Ionq Rate Limits

Name: Ionq Rate Limits
Creator: IonQ
Keywords: Quantum Computing, Trapped Ion, QPU, Aria, Forte, Tempo, Quantum Cloud, Cloud, Hardware, Public Company

IonQ does not publish a single fixed requests-per-second number for the Quantum Cloud REST API. Rate limiting is enforced at three layers: HTTP rate limits on the control-plane API, QPU queue capacity per backend (visible via /backends average_queue_time), and per-Session limits set by the caller (job_count_limit, duration_limit_min, cost_limit).

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

The profile also includes 4 backoff/retry policies defined.

Tagged areas include Quantum Computing, Trapped Ion, QPU, Aria, and Forte.

0 Limits

Quantum ComputingTrapped IonQPUAriaForteTempoQuantum CloudCloudHardwarePublic Company

Policies

Standard HTTP-level rate limit on /v0.4 control-plane requests. Specific values are not publicly documented; clients receive HTTP 429 when limits are exceeded and should back off and retry.

Each QPU backend has a job queue. The /backends endpoint reports `average_queue_time` so clients can choose lower-queue backends. There is no fixed jobs-per-minute number; throughput depends on circuit depth, shot count, and reserved Sessions.

Sessions support caller-set limits on total job count (job_count_limit), duration in minutes (duration_limit_min), and total cost (cost_limit). When any limit is reached, the session ends automatically.

Maximum shots per job vary by backend (simulator vs Aria vs Forte). Submit via the `shots` field on the job creation payload.