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.
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 Lifebit Biotech the way a machine reads it — 5 machine-readable artifacts across 1 API, 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 — Lifebit Biotech scores 39.7/100 (thin), with a separate agent-readiness read of 33/100 (agent aware). 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 Lifebit Biotech
Each block below is one kind of artifact we hold for Lifebit Biotech. 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 1
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.
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...
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.
lifebit-biotech-mcp.yml
MCP SERVERSecurity 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.
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
SECURITYResources
Every other property we hold for Lifebit Biotech — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/lifebit-biotech · machine-readable index on apis.io