Benchling
Benchling is a life-sciences R&D cloud - a unified LIMS, electronic lab notebook (ELN), molecular biology registry, sample inventory, and workflow platform for biotech and pharma. Its tenant-scoped REST API (v2) exposes the same objects scientists work with in the UI - DNA/RNA/protein sequences, custom entities and the registry, inventory (boxes, locations, containers, plates), notebook entries, assay results and runs, lab-automation transforms, workflow tasks, and requests - plus events and webhooks for event-driven automation.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Benchling the way a machine reads it — 29 machine-readable artifacts across 20 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 — Benchling scores 43.1/100 (thin), with a separate agent-readiness read of 48/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 Benchling
Each block below is one kind of artifact we hold for Benchling. 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 20
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.
Benchling AA Sequences API
Amino-acid (protein) sequences.
Benchling Apps API
Benchling Apps, app config, canvases, and sessions.
Benchling Assay Results API
Structured assay results, including transactional bulk loads.
Benchling Assay Runs API
Assay runs and their automation input/output generators.
Benchling Blobs & Files API
Binary attachments and file objects.
Benchling Custom Entities API
Schema-driven custom entities registered in Benchling.
Benchling DNA Sequences API
DNA sequences and sequence-aware operations.
Benchling Entries API
Electronic lab notebook (ELN) entries and templates.
Benchling Events API
Tenant event stream (also delivered via EventBridge and webhooks).
Benchling Inventory API
Locations, boxes, containers, and plates for physical samples.
Benchling Lab Automation API
Automation input generators and output processors for instrument files.
Benchling Molecules API
Small molecules.
Benchling Oligos API
DNA/RNA oligos.
Benchling Projects & Folders API
Organize entries and entities into projects and folders.
Benchling Registry API
Register/unregister entities and browse registry schemas and dropdowns.
Benchling Requests API
Cross-team service requests, tasks, and fulfillments.
Benchling RNA Sequences API
RNA sequences and sequence-aware operations.
Benchling Teams & Organizations API
The Teams & Organizations API from Benchling — 4 operation(s) for teams & organizations.
Benchling Users API
The Users API from Benchling — 4 operation(s) for users.
Benchling Workflows API
Workflow task groups, tasks, and outputs.
Scroll within the panel for all 20 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Benchling API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Benchling Lims Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Benchling Lims Finops
FINOPSSecurity Posture 3
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Benchling — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/benchling-lims · machine-readable index on apis.io