D-Wave · Rate Limits
D Wave Rate Limits
D-Wave Solver API (SAPI) request-rate, concurrency, and quota policies. The SAPI does not publish a uniform per-second request quota; instead, the dominant control surface is per-project solver-access-time quota (charge_time / qpu_access_time) and a small set of explicit per-request structural limits documented in the dwave-cloud-client.
D Wave Rate Limits is the machine-readable rate-limit profile for D-Wave on the APIs.io network, conforming to the API Commons Rate Limits specification.
The profile also includes 7 backoff/retry policies defined.
Tagged areas include Quantum Computing, Quantum Annealing, Optimization, Hybrid Quantum-Classical, and Ising.
0 Limits
Quantum ComputingQuantum AnnealingOptimizationHybrid Quantum-ClassicalIsingQUBOIndustrial OptimizationSamplingLeapOcean SDKSAPI
Policies
A single batch problem-status request accepts at most 1,000 problem IDs.
Problem label is bounded in length.
Total monthly QPU + hybrid solver access time, deducted as `answer.timing.charge_time`
on each completed job. Free Developer plans have a small monthly quota; commercial
Premier and Enterprise plans negotiate higher quotas.
Maximum num_reads per QPU sampling request (typical Advantage / Advantage2 limit).
Maximum annealing_time per QPU read (typical solver upper bound).
Hybrid solver `time_limit` is bounded by per-solver minimum_time_limit_s and
maximum_time_limit_hrs (e.g. 24 hours for the NL solver).
SAPI requests must be sent to the regional endpoint associated with the project; use
the Metadata API /regions/ to resolve endpoints.