View provider details
Providers and their devices are documented once, on Provider's Devices. That page is the canonical reference: how to open Provider Details, the full provider list with credential types, device permissions, device status, and the related jobs for a provider.
This page covers only what matters when you are choosing a target from code.
Choosing a device for a function
- The provider must be compatible with the SDK the function was created with. Only compatible providers appear at invocation time — a provider missing from the list usually means an SDK mismatch, not an outage.
- Simulator or QPU. Simulator devices carry
simulatorin the name. A simulator returns quickly; a QPU queues behind other users and its availability window. - Check device status before a batch run. The device list is fetched fresh each time the page is opened, so it reflects current availability.
- Some providers need a workspace credential before they can be used at all, and an unverified credential blocks invocation. See Workspace Provider Credentials.
Next
- Provider's Devices — the full provider and device reference
- Job Invocation — selecting a provider and device when invoking
- Job Queue — why a job waits on a QPU