benchling-integration
The facts
Its description
Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse queries. Use when automating lab data with benchling-sdk or the v2 API.
The description the agent reads to decide when to use it.
Tools it may use, or may not
allowed-tools: Read Write Edit Bash
Tools it may use while it runs without asking you first.
Files it mentions
references/authentication.md, references/core_capabilities.md, references/sdk_reference.md, references/api_endpoints.md (first 5 of 6 lines)
Files the text names, such as ones to read or write. Found by matching words, so treat them as pointers.
Licence
MIT, from the skill file
The terms its author shares it under, which let it be shown here.
Other settings
compatibility: Requires Python 3.9+, benchling-sdk 1.25.0, network access, a Benchling tenant with API access, and API key or OAuth app credentials. metadata: name: BENCHLING_TENANT_URL, name: BENCHLING_API_KEY, name: BENCHLING_CLIENT_ID, name: BENCHLING_CLIENT_SECRET, name: BENCHLING_PROD_TENANT_URL, name: BENCHLING_PROD_API_KEY, name: BENCHLING_STAGING_TENANT_URL, name: BENCHLING_STAGING_API_KEY
More settings at the top of the file, shown as written.
Other files in this skill (5) Close
The text
Most marks come from matching words in the file, so treat them as pointers.
Benchling Integration
Raw lines 1 to 41When to use
Use this skill for Benchling registry entities, sequence imports, inventory, ELN entries, workflow tasks, apps, event-driven integrations, and warehouse analytics.
Reviewed 2026-09-30: examples target the released benchling-sdk 1.25.0 and its stable v2 API models. The current authentication guide recommends V3 for new development, while the V3 guide still describes endpoint-specific early access. Confirm your tenant's V3 availability and stability before migrating; these v2 SDK examples must not be mechanically rewritten to V3.
SDK imports, model serialization, and request construction were checked locally against 1.25.0. Tenant-dependent examples are illustrative: no authenticated requests, mutations, AWS deployment, or warehouse connection were run.
Raw lines 42 to 56Workflow
- Identify the tenant, API version, identity, and permissions. Use OAuth app credentials for background integrations; use delegated authorization when acting as an individual user. See authentication.
- Read the relevant schema and resolve actual folder, registry, status, and dropdown IDs. Preserve sequence alphabet/topology and sample units. A valid Python model does not establish biological correctness or satisfaction of a tenant's required fields.
- Read a small filtered page before writing. Use typed SDK methods and check their actual parameter names; not all services share the same CRUD naming convention.
- Construct and serialize a representative payload. For imports, retain external IDs and returned Benchling IDs so a retry can reconcile a partial run without duplicates.
- Perform the requested operation and read back the result. Check terminal async status; completed polling can still mean
FAILED.
Setup and a read-only query
uv pip install "benchling-sdk==1.25.0"import os
from benchling_sdk.benchling import Benchling
from benchling_sdk.auth.client_credentials_oauth2 import ClientCredentialsOAuth2
tenant_url = os.environ["BENCHLING_TENANT_URL"].rstrip("/")
benchling = Benchling(
url=tenant_url,
auth_method=ClientCredentialsOAuth2(
client_id=os.environ["BENCHLING_CLIENT_ID"],
client_secret=os.environ["BENCHLING_CLIENT_SECRET"],
token_url=f"{tenant_url}/oauth/token",
),
)
for page in benchling.dna_sequences.list(page_size=10, name_includes="plasmid"):
for sequence in page:
print(sequence.id, sequence.name)
break # deliberate first-page connectivity/permission checkA successful empty page is a valid connectivity result. It does not imply access to all projects. There is no documented v2 users/me route or SDK users.get_me().
Important SDK conventions
- Import
fieldsfrombenchling_sdk.helpers.serialization_helpers. Its input is{"field_name": {"value": value}}, including the innervaluemapping. - Use
dna_sequence_idfor DNA updates andworkflow_task_idfor workflow updates. Workflow task creation requires aworkflow_task_group_id. - Entry methods are
create_entry,get_entry_by_id,list_entries, andupdate_entry. list()usually returns pages; iterate twice to reach the objects.estimated_countis a property that can raiseNotImplementedError, not a method or guaranteed count.- Moving a tube uses
ContainerUpdate(parent_storage_id=...). Material transfer is a separate operation; it changes contents and quantities. - Register on creation with
registry_idplus eitherentity_registry_id(a human registry identifier) ornaming_strategy. Do not confuse those with the registry's ID.
Common use cases
Raw lines 115 to 116Import FASTA sequences
Install Biopython separately (uv pip install biopython). This illustrative import creates unregistered linear DNA; choose topology and resolve collisions before running.
from Bio import SeqIO
from benchling_sdk.models import DnaSequenceCreate
for record in SeqIO.parse("sequences.fasta", "fasta"):
payload = DnaSequenceCreate(
name=record.id,
bases=str(record.seq),
is_circular=False,
folder_id="lib_example",
)
created = benchling.dna_sequences.create(payload)
print(record.id, created.id) # persist this mapping for restart/reconciliationRaw lines 117 to 136Audit inventory under a location
for page in benchling.containers.list(ancestor_storage_id="box_example"):
for container in page:
print(container.id, container.name, container.barcode)ancestor_storage_id includes descendants. For immediate children only, inspect the returned parent storage or use the documented storage-contents service.
Export sequences for one schema
import csv
with open("sequences.csv", "w", newline="", encoding="utf-8") as handle:
writer = csv.DictWriter(handle, fieldnames=["id", "name", "bases", "length"])
writer.writeheader()
for page in benchling.dna_sequences.list(schema_id="ts_example"):
for seq in page:
writer.writerow({
"id": seq.id, "name": seq.name,
"bases": seq.bases, "length": len(seq.bases),
})Raw lines 148 to 163References
- Core capabilities: scientific workflows and boundaries.
- SDK reference: validated constructors, updates, inventory, entries, workflow tasks, retries, and async handling.
- REST reference: endpoint paths, payloads, filters, response envelopes, pagination, and rate limits.
- Authentication: app credentials, personal keys, delegated authorization, legacy OIDC, and HTTP clients.
- EventBridge: supported event types, payloads, setup, and recovery; webhook differences.
- Official SDK 1.25.0
- Official REST reference
Boilerplate, lines 178 to 193. The same text appears in 125 other files here. Close
From K-Dense-AI/scientific-agent-skills at 5f2bc03, 2026-10-26. Not read by a model yet. Summary and techniques by Claude Opus 5.5 on 2026-11-06.