IQM Quantum Computers

IQM Quantum Computers (IQM Finland Oy) builds superconducting quantum computers and sells access to them, both as on-premises systems and as a cloud service. Its developer surface is IQM Resonance, a quantum cloud platform at resonance.iqm.tech whose REST API accepts circuits, queues them against a named QPU, and returns measurement results — billed in QPU seconds rather than API calls. Access is through a bearer API token generated from the Resonance dashboard, and the practical client contract is IQM's Apache-2.0 Python stack (iqm-client, with Qiskit, Cirq and Qrisp adapters) rather than a published OpenAPI, which IQM does not ship. IQM does publish 14 first-party Protobuf message contracts defining the Station Control wire format, a dated changelog with explicit breaking-change notices, and a free Starter tier with a monthly credit allowance.

IQM Quantum Computers publishes 1 API on the APIs.io network. Tagged areas include Quantum Computing, Quantum Cloud, High Performance Computing, Research, and Scientific Computing.

IQM Quantum Computers’ developer surface includes documentation, API reference, getting-started guide, signup flow, pricing, support, engineering blog, and 21 more developer resources.

🌐 Visit website 📡 Source on GitHub

44.6/100 developing ▬ flat Agent 21/100 agent aware saas Full breakdown ↓
scored 2026-09-14 · rubric v0.22.0

AccessFreemiumSelf serve⚡ Free to try

1 APIs

Quantum Computing Quantum Cloud High Performance Computing Research Scientific Computing Developer Tools Protobuf Hardware Finland Deep Tech

Kin Score

Kin Score How this is scored →
scored 2026-09-14 · rubric v0.22.0

Composite quality — 44.6/100 · developing

Contract Quality 6.7 / 25

Developer Ergonomics 14.3 / 20

Access Clarity 13.2 / 20

Operational Transparency 3.1 / 13

Contract Governance 0.5 / 12

Discoverability 6.9 / 10

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/iqm-quantum-computers: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

IQM Resonance API

The REST API behind IQM Resonance, IQM's quantum cloud service. It lists the quantum computers available on a server, reports their health and calibration state, accepts circuit...

Pricing Plans 1

Published pricing tiers and plan structures.

Iqm Quantum Computers Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Iqm Quantum Computers Rate Limits

0 limits

RATE LIMITS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Iqm Quantum Computers Authentication

http · 1 scheme

SECURITY

Iqm Quantum Computers Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

Lifecycle

Conformance

DataModel

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 4

Status, limits, changes, and where to get help

Support

Roadmap

ChangeLog

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Protobuf

Protobuf

Source (apis.yml)

aid: iqm-quantum-computers
name: IQM Quantum Computers
description: IQM Quantum Computers (IQM Finland Oy) builds superconducting quantum computers and sells access to them, both
  as on-premises systems and as a cloud service. Its developer surface is IQM Resonance, a quantum cloud platform at resonance.iqm.tech
  whose REST API accepts circuits, queues them against a named QPU, and returns measurement results — billed in QPU seconds
  rather than API calls. Access is through a bearer API token generated from the Resonance dashboard, and the practical client
  contract is IQM's Apache-2.0 Python stack (iqm-client, with Qiskit, Cirq and Qrisp adapters) rather than a published OpenAPI,
  which IQM does not ship. IQM does publish 14 first-party Protobuf message contracts defining the Station Control wire format,
  a dated changelog with explicit breaking-change notices, and a free Starter tier with a monthly credit allowance.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - rate-limits
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
image: https://iqm.tech/wp-content/uploads/2025/02/IQM-Logo-black-transparent.png
url: https://raw.githubusercontent.com/api-evangelist/iqm-quantum-computers/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-23'
modified: '2026-08-23'
tags:
- Quantum Computing
- Quantum Cloud
- High Performance Computing
- Research
- Scientific Computing
- Developer Tools
- Protobuf
- Hardware
- Finland
- Deep Tech
apis:
- aid: iqm-quantum-computers-resonance
  name: IQM Resonance API
  description: The REST API behind IQM Resonance, IQM's quantum cloud service. It lists the quantum computers available on
    a server, reports their health and calibration state, accepts circuit and sweep jobs for execution, and returns measurements,
    measurement counts and sweep results. Requests are made to https://resonance.iqm.tech/api/v1/ with an IQM API token in
    the Authorization header; job execution is asynchronous and discovered by polling. No OpenAPI is published — the operation
    surface recorded in this repo is derived from IQM's own Apache-2.0 iqm-client library.
  humanURL: https://iqm.tech/products/iqm-resonance/
  baseURL: https://resonance.iqm.tech/api/v1/
  tags:
  - Quantum Computing
  - Quantum Cloud
  - Job
  - Calibration
  tags_raw:
  - Quantum Computing
  - Quantum Cloud
  - Jobs
  - Calibration
  properties:
  - type: Documentation
    url: https://docs.iqm.tech/iqm-client/
  - type: GettingStarted
    url: https://docs.iqm.tech/iqm-client/user_guide_qiskit.html
  - type: Protobuf
    url: grpc/iqm-quantum-computers-protobuf.yml
  - type: X-MCPServerCandidate
    url: mcp/iqm-quantum-computers-mcp.yml
    note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list
      derived from the published API contracts, not an existing server. The scorer already read the manifest and reported
      mcp_server correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
  - type: DataModel
    url: data-model/iqm-quantum-computers-data-model.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/iqm-quantum-computers-domain-security.yml
- type: Website
  url: https://iqm.tech/
- type: DeveloperPortal
  url: https://docs.iqm.tech/
- type: Documentation
  url: https://docs.iqm.tech/iqm-client/
- type: APIReference
  url: https://docs.iqm.tech/iqm-client/API.html
- type: GettingStarted
  url: https://docs.iqm.tech/iqm-client/user_guide_qiskit.html
- type: SignUp
  url: https://resonance.iqm.tech/sign-up
- type: Pricing
  url: https://iqm.tech/products/iqm-resonance/
- type: PrivacyPolicy
  url: https://iqm.tech/privacy-policy/
- type: Support
  url: https://iqm.tech/contact/
- type: Blog
  url: https://iqm.tech/blog/
- type: GitHubOrganization
  url: https://github.com/iqm-finland
- type: Roadmap
  url: https://iqm.tech/technology/roadmap/
- type: Packages
  url: packages/iqm-quantum-computers-packages.yml
- type: SDKs
  url: packages/iqm-quantum-computers-packages.yml
- type: Protobuf
  url: grpc/iqm-quantum-computers-protobuf.yml
- type: Authentication
  url: authentication/iqm-quantum-computers-authentication.yml
- type: ErrorCatalog
  url: errors/iqm-quantum-computers-problem-types.yml
- type: Conventions
  url: conventions/iqm-quantum-computers-conventions.yml
- type: Lifecycle
  url: lifecycle/iqm-quantum-computers-lifecycle.yml
- type: ChangeLog
  url: changelog/iqm-quantum-computers-changelog.yml
- type: Conformance
  url: conformance/iqm-quantum-computers-conformance.yml
- type: DataModel
  url: data-model/iqm-quantum-computers-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/iqm-quantum-computers-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Sandbox
  url: sandbox/iqm-quantum-computers-sandbox.yml
- type: Plans
  url: plans/iqm-quantum-computers-plans-pricing.yml
- type: RateLimits
  url: rate-limits/iqm-quantum-computers-rate-limits.yml
- type: LLMsTxt
  url: llms/iqm-quantum-computers-llms.txt
x-enrichment:
  date: '2026-08-23'
  status: enriched
  artifacts_added: 30
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/iqm-quantum-computers"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/iqm-quantum-computers/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/iqm-quantum-computers/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.