Riverlane
Riverlane is a Cambridge (UK) quantum computing company building the quantum error correction (QEC) stack. Its two product lines are Deltaflow — a real-time QEC system covering qubit data readout, decoding, logical operations and orchestration, running error correction on up to 250 physical qubits with the proprietary Local Clustering Decoder — and Deltakit, an Apache-2.0 open-source Python SDK for designing, generating, simulating, decoding and analysing QEC experiments. The public developer surface is the Deltakit cloud service at https://deltakit.riverlane.com/proxy, a bearer-token API with two coexisting versions: a GraphQL endpoint (/api/graphql, API v1) and an asynchronous task REST API (/api/v2/tasks/add|get|kill, API v2). Both front Riverlane's proprietary decoders (Ambiguity Clustering, Local Clustering, Collision Clustering), leakage-aware decoding and simulation, iSWAP native-gate circuit generation, and stability-experiment generation. Riverlane publishes no OpenAPI or AsyncAPI document; the machine-readable contract is the open-source client library at github.com/Deltakit/deltakit, which is where every endpoint recorded in this profile was read from.
Riverlane publishes 1 API on the APIs.io network. Tagged areas include quantum-computing, quantum-error-correction, decoders, scientific-computing, and python-sdk.
Riverlane’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, signup flow, changelog, and 20 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Deltakit Cloud API
Bearer-token cloud service backing the Deltakit SDK. Exposes the compute-heavy and proprietary parts of the QEC workflow that do not run locally: leakage noise generation and si...
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type