Lifebit Biotech

Lifebit Biotech Ltd is a London-founded (2017) health-data infrastructure company that builds federated Trusted Research Environments (TREs) for population-scale biomedical research and sovereign health AI. Rather than centralising sensitive patient data, Lifebit sends compute to the data: analyses execute inside each participating custodian's own infrastructure and every proposed output passes through an automated airlock (the "sixth safe") controlled by the data custodian rather than the vendor. The commercial platform, CloudOS, orchestrates Nextflow and WDL/Cromwell pipelines, interactive analysis sessions, projects, job queues and federated datasets, and exposes a REST API at https://cloudos.lifebit.ai/api (v1/v2/v3) authenticated with an apikey header. Lifebit publishes a first-party open-source Python client and command line interface, cloudos-cli, plus a GitHub Action wrapper. Product surface includes the federated TRE, Airlock Tower output disclosure control, an agentic federated TRE, AI-automated OMOP CDM v5.4 harmonisation, federated learning, a trusted data lakehouse and a trusted data marketplace. Publicly disclosed deployments include Genomics England, the US NIH National Library of Medicine, CanPath, Singapore Synapxe, Boehringer Ingelheim, Flatiron Health and 23andMe.

Lifebit Biotech publishes 1 API on the APIs.io network. Tagged areas include Company, Health, Genomics, Bioinformatics, and Federated Learning.

Lifebit Biotech’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, pricing, YouTube channel, and 29 more developer resources.

🌐 Visit website 📡 Source on GitHub

34.2/100 thin ▬ flat Agent 8/100 agent aware open core · GPL-3.0 Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

1 APIs

Company Health Genomics Bioinformatics Federated LearningTrusted Research EnvironmentData Governance Life Sciences Sovereign AIOMOPWorkflow Orchestration

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 34.2/100 · thin

Contract Quality 0.0 / 19

Developer Ergonomics 10.7 / 15

Access Clarity 6.5 / 15

Operational Transparency 1.8 / 10

Contract Governance 0.0 / 9

Discoverability 5.7 / 8

Regulatory Posture 4.9 / 15

Open Source Surface 2.5 / 10

Agent readiness — 8/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 4 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 75 points between them, because both conditional facets apply and carry 25 points together. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/lifebit-biotech: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Lifebit CloudOS API

The REST API behind the Lifebit Platform (CloudOS): manage workspace projects, job queues, workflows/pipelines, Nextflow and Cromwell/WDL job submission and monitoring, interact...

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Lifebit Biotech Authentication

apiKey/http · 2 schemes

SECURITY

Lifebit Biotech Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Lifebit Biotech Trust Center

SOC 2 Type II, ISO/IEC 27001, ISO 9001, FedRAMP, Cyber Essentials Plus, HIPAA, GDPR, NHS Data Security and Protection Toolkit (DSPT), G-Cloud 13, EHDEN, HITRUST CSF v11

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Conformance

Lifecycle

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

CLI

Access & Security 4

Authentication, authorization, and security posture

TrustCenter

Compliance

Authentication

DomainSecurity

Learn 1

Tutorials, courses, talks, and written guidance

YouTube

YouTube

Operate 4

Status, limits, changes, and where to get help

IssueTracker

Releases

Support

ChangeLog

Commercial 3

Pricing, plans, and the legal terms of use

License

License

Pricing

Pricing

PrivacyPolicy

PrivacyPolicy

Company 4

The organization behind the API

Website

Website

Blog

Blog

Twitter

Twitter

LinkedIn

Other 4

Properties that don't map to a standard resource type

CaseStudies

Publications

WhitePapers

Glossary

Source (apis.yml)

aid: lifebit-biotech
name: Lifebit Biotech
description: 'Lifebit Biotech Ltd is a London-founded (2017) health-data infrastructure company that builds federated Trusted
  Research Environments (TREs) for population-scale biomedical research and sovereign health AI. Rather than centralising
  sensitive patient data, Lifebit sends compute to the data: analyses execute inside each participating custodian''s own infrastructure
  and every proposed output passes through an automated airlock (the "sixth safe") controlled by the data custodian rather
  than the vendor. The commercial platform, CloudOS, orchestrates Nextflow and WDL/Cromwell pipelines, interactive analysis
  sessions, projects, job queues and federated datasets, and exposes a REST API at https://cloudos.lifebit.ai/api (v1/v2/v3)
  authenticated with an apikey header. Lifebit publishes a first-party open-source Python client and command line interface,
  cloudos-cli, plus a GitHub Action wrapper. Product surface includes the federated TRE, Airlock Tower output disclosure control,
  an agentic federated TRE, AI-automated OMOP CDM v5.4 harmonisation, federated learning, a trusted data lakehouse and a trusted
  data marketplace. Publicly disclosed deployments include Genomics England, the US NIH National Library of Medicine, CanPath,
  Singapore Synapxe, Boehringer Ingelheim, Flatiron Health and 23andMe.'
url: https://raw.githubusercontent.com/api-evangelist/lifebit-biotech/refs/heads/main/apis.yml
deliveryModel:
  model: open-core
  license: GPL-3.0
  open_source: true
  commercial: true
  callable_host: false
  label: Open core · an OSS project plus a commercial hosted product
  confidence: high
  source:
  - license
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://lifebit.ai/wp-content/uploads/2025/04/favicon.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- techstars
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Health
- Genomics
- Bioinformatics
- Federated Learning
- Trusted Research Environment
- Data Governance
- Life Sciences
- Sovereign AI
- OMOP
- Workflow Orchestration
apis:
- aid: lifebit-biotech:cloudos-api
  name: Lifebit CloudOS API
  description: 'The REST API behind the Lifebit Platform (CloudOS): manage workspace projects, job queues, workflows/pipelines,
    Nextflow and Cromwell/WDL job submission and monitoring, interactive analysis sessions, and datasets/files across S3 and
    Azure Blob storage. Requests are scoped to a workspace with a teamId query parameter and authenticated with an apikey
    request header. Version prefixes /api/v1, /api/v2 and /api/v3 are in concurrent use. Lifebit does not publish an OpenAPI
    description; the operation surface catalogued here was derived from the first-party open-source client, cloudos-cli.'
  humanURL: https://lifebit-ai.github.io/cloudos-cli/
  baseURL: https://cloudos.lifebit.ai/api/v1
  tags:
  - Genomics
  - Workflow Orchestration
  - Bioinformatics
  - Job
  - Datasets
  tags_raw:
  - Genomics
  - Workflow Orchestration
  - Bioinformatics
  - Jobs
  - Datasets
  properties:
  - type: Authentication
    url: authentication/lifebit-biotech-authentication.yml
  - type: Conventions
    url: conventions/lifebit-biotech-conventions.yml
  - type: ErrorCatalog
    url: errors/lifebit-biotech-problem-types.yml
  - type: CLI
    url: cli/lifebit-biotech-cli.yml
  - type: SourceCode
    url: https://github.com/lifebit-ai/cloudos-cli
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: IssueTracker
  url: https://github.com/lifebit-ai/cloudos-cli/issues
- type: Releases
  url: https://github.com/lifebit-ai/cloudos-cli/releases
- type: License
  name: GPL-3.0
  url: https://github.com/lifebit-ai/cloudos-cli/blob/main/LICENSE
- type: Website
  url: https://lifebit.ai/
- type: DeveloperPortal
  url: https://lifebit-ai.github.io/cloudos-cli/
- type: Documentation
  url: https://lifebit-ai.github.io/cloudos-cli/
- type: APIReference
  url: https://lifebit-ai.github.io/cloudos-cli/cli.html
- type: GettingStarted
  url: https://lifebit-ai.github.io/cloudos-cli/getting_started.html
- type: GitHubOrganization
  url: https://github.com/lifebit-ai
- type: Blog
  url: https://lifebit.ai/blog/
- type: Support
  url: https://lifebit.ai/contact-us/
- type: Pricing
  url: https://lifebit.ai/pricing/
- type: Login
  url: https://cloudos.lifebit.ai/
- type: PrivacyPolicy
  url: https://lifebit.ai/privacy-policy/
- type: TrustCenter
  url: security/lifebit-biotech-trust-center.yml
- type: Compliance
  url: https://lifebit.ai/trust-center/
- type: CaseStudies
  url: https://lifebit.ai/case-studies/
- type: Publications
  url: https://lifebit.ai/publications/
- type: WhitePapers
  url: https://lifebit.ai/white-papers/
- type: Glossary
  url: https://lifebit.ai/glossary/
- type: Twitter
  url: https://x.com/lifebitAI
- type: LinkedIn
  url: https://www.linkedin.com/company/lifebit-ai/
- type: YouTube
  url: https://www.youtube.com/channel/UCZD4p-fsOh6AUgRvMl1RNfQ
- type: Packages
  url: packages/lifebit-biotech-packages.yml
- type: SDKs
  url: packages/lifebit-biotech-packages.yml
- type: CLI
  url: cli/lifebit-biotech-cli.yml
- type: LLMsTxt
  url: llms/lifebit-biotech-llms.txt
- type: WellKnown
  url: well-known/lifebit-biotech-well-known.yml
- type: X-MCPServerCandidate
  url: mcp/lifebit-biotech-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Authentication
  url: authentication/lifebit-biotech-authentication.yml
- type: Conventions
  url: conventions/lifebit-biotech-conventions.yml
- type: ErrorCatalog
  url: errors/lifebit-biotech-problem-types.yml
- type: Conformance
  url: conformance/lifebit-biotech-conformance.yml
- type: Lifecycle
  url: lifecycle/lifebit-biotech-lifecycle.yml
- type: ChangeLog
  url: changelog/lifebit-biotech-changelog.yml
- type: DomainSecurity
  url: security/lifebit-biotech-domain-security.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/lifebit-biotech"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/lifebit-biotech/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/lifebit-biotech/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.