Atom Computing
Atom Computing is a Berkeley, California neutral-atom quantum computing company building large-scale, gate-based quantum computers using optically-trapped Ytterbium-171 nuclear-spin qubits. Founded in 2018 by Ben Bloom, the company became the first in the industry to exceed 1,000 qubits in a gate-based quantum computer with its second-generation platform in October 2023 (1,180 qubits across 1,225 sites). Its current commercial product, AC1000, is a universal gate-based, on-premises quantum computing system with 1,200+ physical qubits, all-to-all connectivity, mid-circuit measurement with qubit reuse and reset, real-time conditional branching, and better-than-threshold fidelities (>99.9% single-qubit, >99.6% two-qubit, >99.8% SPAM). The platform is programmable via OpenQASM and QIR (Quantum Intermediate Representation) and ships with a 20-qubit classical emulator. In January 2025 Atom Computing and Microsoft announced an on-premises 50-logical-qubit system (Magne), with additional strategic collaborations across Cisco (networked/distributed quantum, March 2026), NVIDIA NVQLink integration (March 2026), and a Letter of Intent for $100M from the U.S. Department of Commerce (May 2026). The commercial model centers on enterprise and national-lab on-premises system sales and partnerships; there is no public cloud API or self-serve developer portal — programmatic access is via the standard OpenQASM/QIR toolchains targeting customer-deployed AC1000 hardware.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Atom Computing the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Atom Computing scores 7.4/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Atom Computing
Each block below is one kind of artifact we hold for Atom Computing. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Atom Computing — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 6
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/atom-computing · machine-readable index on apis.io