Provision Endpoint and Engage

Provision Endpoint and Engage

Provision a dedicated endpoint, wait for it to become healthy, and engage on it.

1. Create an endpoint associated with the caller's account, bound to the processor.
2. Poll the endpoint until it reports healthy. Retries while the endpoint is still provisioning, then proceeds to engage once it is up.
3. Create an engagement against the now-healthy endpoint, returning the address and credentials required to execute on the processor.

What you'll need to have ready

• token: A QCS JWT bearer token used to authenticate API requests.
• quantumProcessorId: The processor the new endpoint should serve (e.g. Aspen-M-3).
• datacenters: Optional datacenters available for endpoint placement. Defaults to berkeley-775 when omitted.

For your developer

Arazzo workflow rigetti:provision-endpoint-and-engage, 3 operations: CreateEndpoint → GetEndpoint → CreateEngagement. Specs on APIs.io.