Boltz
Boltz (Boltz PBC) is a public-benefit AI research company building open-source and proprietary foundation models for biomolecular structure prediction, binding-affinity estimation, and generative protein and small-molecule design. Its open-source models (Boltz-1, Boltz-2, BoltzGen, all MIT-licensed) are used by 100,000+ scientists across pharma and biotech, and its commercial platform, Boltz Lab, pairs those models with managed compute and collaborative interfaces. The Boltz Compute API exposes these capabilities as asynchronous jobs - structure & binding prediction, ADME prediction, and small-molecule / protein design and library screening - with official Python, TypeScript, and Go SDKs, a CLI, and an MCP server for agentic drug-discovery workflows. Backed by a $28M seed round led by Amplify Partners, a16z, and Zetta Venture Partners.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Boltz the way a machine reads it — 10 machine-readable artifacts across 7 APIs, 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 — Boltz scores 54.8/100 (developing), with a separate agent-readiness read of 51/100 (agent ready). 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 Boltz
Each block below is one kind of artifact we hold for Boltz. 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.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Boltz Admin API
The Admin API from Boltz — 7 operation(s) for admin.
Boltz Auth API
The Auth API from Boltz — 1 operation(s) for auth.
Boltz CLI API
The CLI API from Boltz — 1 operation(s) for cli.
Boltz Predictions API
The Predictions API from Boltz — 8 operation(s) for predictions.
Boltz Protein API
The Protein API from Boltz — 15 operation(s) for protein.
Boltz Share Links API
The Share Links API from Boltz — 4 operation(s) for share links.
Boltz Small Molecule API
The Small Molecule API from Boltz — 14 operation(s) for small molecule.
Scroll within the panel for all 7 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
boltz-mcp.yml
MCP SERVERSecurity Posture 2
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 Boltz — 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.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/boltz · machine-readable index on apis.io