# Element Biosciences

> Element Biosciences builds benchtop DNA sequencing and multiomics instruments — AVITI, AVITI LT, AVITI24 and VITARI — based on its Avidite Base Chemistry (ABC). Instrument data is managed in ElemBio Cloud, which exposes a public, versioned, read-only REST API and a first-party CLI for runs, workflow executions, instruments, storage connections and files.

This file was generated by API Evangelist from the provider's published artifacts on 2026-08-04.
Element Biosciences does not publish an llms.txt of its own (https://docs.elembio.io/llms.txt returned 404).

## APIs

- [Element Biosciences Cloud API](https://docs.elembio.io/developers/api/): Read-only REST access to sequencing and multiomics runs, workflow executions, registered instruments, storage connections and their files. Base URL https://cloud-api.usw2.elembio.io, all paths under /v1. 16 operations, all GET.

## Specs

- [OpenAPI 3.1.0 (YAML)](https://cloud-api.usw2.elembio.io/openapi.yaml): The machine-readable contract, served from the API host root.
- [OpenAPI 3.1.0 (JSON)](https://cloud-api.usw2.elembio.io/openapi.json): Same document in JSON.
- [OpenAPI mirror on the docs host](https://docs.elembio.io/scalar/openapi.yaml): Identical content, referenced from the API root document.

## Docs

- [Developer Hub](https://docs.elembio.io/developers/): Entry point for the API and CLI.
- [API getting started](https://docs.elembio.io/developers/api/getting-started/): First call, base URL, key header, pagination.
- [Interactive API reference](https://docs.elembio.io/developers/api/): Scalar-rendered reference with try-it.
- [Core concepts](https://docs.elembio.io/developers/core-concepts/): Resource model, identifiers, pagination, filter expression language.
- [Authentication](https://docs.elembio.io/developers/authentication/): API key handling, profiles, environment variables.
- [API keys and permissions](https://docs.elembio.io/docs/elembio-cloud/api-keys/): The full permission list, key expiry and revocation.
- [API changelog](https://docs.elembio.io/developers/api/api-changelog/): Dated release notes for the Cloud API.
- [ElemBio Cloud documentation](https://docs.elembio.io/): Product documentation for the wider platform.

## CLI

- [CLI getting started](https://docs.elembio.io/developers/command-line/getting-started/): Install via Homebrew, npm, or direct binary download.
- [CLI reference](https://docs.elembio.io/developers/command-line/reference/): All command groups — login, profile, runs, executions, instruments, storage, mount.
- [CLI changelog](https://docs.elembio.io/developers/command-line/changelog/): Dated CLI release notes.
- [npm package](https://www.npmjs.com/package/elembio-cli): `npm install -g elembio-cli` (linux/x64).
- [Homebrew tap](https://github.com/Elembio/homebrew-tap): `brew tap elembio/tap && brew install elembio`.

## Authentication

Every request carries a static API key in the `x-api-key` header. Keys are created in
the ElemBio Cloud console under Organization > API Keys, expire after 1-365 days
(default 30), and carry explicit permissions of the form `resource:action[:resource_id]`
— `Runs:Read`, `Runs:Download`, `Executions:Read`, `Executions:Download`,
`Executions:Logs`, `Instruments:Read`, `Storage:Read`, `Storage:Download`. A request
that is authenticated but under-scoped returns HTTP 403 with reason `INSUFFICIENT_SCOPE`.
Call `GET /v1/auth` to see a key's tenant and scopes. There is no OAuth 2.0 flow.

## Conventions

- Pagination is cursor based: `pageSize` (default 100, max 1000), `pageToken`, `includeTotalCount`; the response carries `nextPageToken`.
- Filtering uses one keyword expression language on the `filter` parameter: `status:completed type:sequencing`, `time_completed>=7d`, `status:completed,failed`.
- Response bodies use lowerCamelCase; filter keywords use snake_case dotted paths.
- Timestamps are RFC 3339.
- Errors return `{code, message, details[]}` where `details[].reason` is the machine-readable code (`RUN_NOT_FOUND`, `INVALID_API_KEY`, `MISSING_API_KEY`, `INSUFFICIENT_SCOPE`, `INTERNAL_ERROR`). This is a google.rpc envelope, not RFC 9457 problem+json.
- `X-Request-ID` on the response correlates with `details[].metadata.request_id`; quote it to support.
- File downloads do not stream through the API. The `*/credentials` operations vend short-lived scoped AWS S3 session credentials for direct S3 access.

## Products

- [All instruments](https://www.elementbiosciences.com/products/all-instruments)
- [AVITI System](https://www.elementbiosciences.com/products/aviti)
- [ElemBio Cloud](https://www.elementbiosciences.com/products/elembio-cloud)

## Open source

- [Elembio on GitHub](https://github.com/Elembio): 16 public repositories.
- [bases2fastq-nf](https://github.com/Elembio/bases2fastq-nf): Nextflow pipeline that demultiplexes AVITI raw basecall data into FASTQ.
- [cells2stats-nf](https://github.com/Elembio/cells2stats-nf): Nextflow pipeline that generates cytoprofiling data from AVITI24 runs.
- [cytoprofiling](https://github.com/Elembio/cytoprofiling): Python and R libraries for processing cytoprofiling datasets (BSD-3-Clause).

## Not published

The following were probed on 2026-08-04 and are genuinely absent — recorded so agents do not chase them:
no /.well-known/ documents on any host, no security.txt, no A2A agent card, no OpenAPI on the docs
host root, no MCP server (mcp.elembio.io is a wildcard SPA catch-all, not JSON-RPC), no webhooks or
event/streaming surface, no AsyncAPI, no status page, no published SLA, no deprecation policy, no
documented rate limits, no OAuth 2.0, no sandbox or test-mode credentials, and no published security
certifications (no SOC 2, ISO 27001, HIPAA or FedRAMP claim).

## Company

- [Element Biosciences](https://www.elementbiosciences.com/)
- [Blog](https://www.elementbiosciences.com/blog)
- [Knowledge base](https://www.elementbiosciences.com/knowledge-base)
- [Contact](https://www.elementbiosciences.com/contact)
- [Terms of use](https://www.elementbiosciences.com/legal/terms)
- [Privacy](https://www.elementbiosciences.com/legal/privacy)