capabilities.work

Reservation Readiness Check

A 4-step recipe with Rigetti Computing. We can help you get access.

Recipe · 4 steps

Reservation Readiness Check

with Rigetti Computing

Gather identity, balance, maintenance, and availability ahead of booking.

  1. Resolve the authenticated user to obtain the QCS user id used for balance lookup.
  2. Retrieve the user's account balance in cents USD to confirm spend capacity.
  3. Retrieve the processor's maintenance calendar (iCal) so the caller can avoid windows where execution is unavailable.
  4. List open reservation windows on the processor that start at or after the requested time and match the requested duration.
What you'll need to have ready
  • token: A QCS JWT bearer token used to authenticate API requests.
  • quantumProcessorId: The processor to check (e.g. Aspen-M-3).
  • startTimeFrom: RFC3339 timestamp; the earliest acceptable reservation start.
  • duration: Desired reservation length as a Go duration string (e.g. "30m").
For your developer

Arazzo workflow rigetti:reservation-readiness-check, 4 operations: AuthGetUser → GetUserBalance → GetQuantumProcessorCalendar → FindAvailableReservations. Specs on APIs.io.

More recipes with Rigetti Computing

Book QPU ReservationCancel ReservationCreate Execution EngagementDiscover Quantum ProcessorProvision Endpoint and Engage