Life Sciences
Industry-vertical index for the life sciences, biotechnology, and pharmaceutical landscape. Catalogs the major public and commercial APIs spanning clinical trial registries, drug and regulatory data, genomic reference data, electronic health record exchange, laboratory informatics systems, and bioinformatics pipeline platforms. The catalog is anchored by shared schemas for the three core records that recur across this domain: the clinical trial, the drug, and the gene.
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 Life Sciences the way a machine reads it — 33 machine-readable artifacts across 22 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 — Life Sciences scores 33.5/100 (thin), with a separate agent-readiness read of 32/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 Life Sciences
Each block below is one kind of artifact we hold for Life Sciences. 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 22
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.
EU Clinical Trials Register / CTIS
The European Medicines Agency's Clinical Trials Information System (CTIS) and the legacy EU Clinical Trials Register. CTIS is the single entry point for sponsors and regulators ...
openFDA
A U.S. Food and Drug Administration project that exposes public FDA data via a single Elasticsearch-backed REST/JSON API. Covers adverse-event reports, drug labels, recalls, NDC...
DailyMed
The National Library of Medicine's authoritative source of FDA-approved Structured Product Labeling (SPL) for prescription and over-the-counter medications marketed in the Unite...
RxNorm API
The National Library of Medicine's web service for accessing RxNorm, the standardized nomenclature for clinical drugs that links names of drugs across the major U.S. drug vocabu...
DrugBank API
A commercial drug knowledge API providing curated pharmacology, pharmacokinetics, drug-drug interaction, indication, and identifier cross-walk data covering small molecules and ...
NCBI Entrez E-utilities
The set of nine programmatic interfaces (ESearch, EPost, ESummary, EFetch, ELink, EInfo, EGQuery, ESpell, ECitMatch) that provide unified access to all NCBI databases including ...
Ensembl REST API
The European Bioinformatics Institute's REST/JSON interface to the Ensembl genome browser. Provides programmatic access to genomic annotation, variation, comparative genomics, r...
UCSC Genome Browser REST API
The University of California Santa Cruz Genome Browser's REST API for programmatic retrieval of assemblies, tracks, sequences, and annotations across the genomes hosted in the U...
ClinVar (via E-utilities)
The NIH/NLM database of relationships among human genomic variation and phenotype, with supporting evidence. Accessible programmatically via Entrez E-utilities and via a structu...
dbSNP (via E-utilities)
The NCBI Short Genetic Variations database, the canonical reference for single nucleotide polymorphisms (SNPs) and small insertions/deletions in humans and other organisms. Acce...
HL7 FHIR
Fast Healthcare Interoperability Resources (FHIR) is HL7's standard for health care data exchange. The current normative version is R5, released March 2023. Defines roughly 150 ...
SMART on FHIR
An open-spec authorization profile layered on top of FHIR that enables third-party clinical applications to launch within an EHR session with OAuth 2.0 / OpenID Connect scopes s...
Benchling Developer Platform
Benchling's REST API and webhook platform for its R&D cloud, exposing programmatic access to the Notebook (entries), Registry (registered entities, sequences, plasmids), Invento...
TetraScience Data Platform
A cloud-native scientific data platform that harmonizes instrument and informatics data across pharma R&D. Exposes REST APIs and SDKs for ingesting, querying, and integrating la...
Sapio Sciences ELN/LIMS API
Sapio Sciences' platform API providing programmatic access to its Electronic Laboratory Notebook, Laboratory Information Management System, and Scientific Data Cloud, covering s...
DNAnexus Platform API
DNAnexus is a cloud bioinformatics platform used by pharma, biotech, and research institutions to run genomic and biomedical compute workflows. Its platform API provides program...
Seven Bridges (Velsera) Platform API
A multi-cloud bioinformatics platform (now part of Velsera) offering hosted instances of the NCI Cancer Genomics Cloud and other cohort analysis environments. Provides REST APIs...
Galaxy Project API
The open-source Galaxy bioinformatics workbench exposes a REST API for managing histories, datasets, workflows, tools, jobs, and users across community Galaxy servers and self-h...
GA4GH APIs (htsget, DRS, WES, TES, Beacon)
The Global Alliance for Genomics and Health publishes a suite of open REST specifications enabling federated access to genomic data and compute. Includes htsget (sequencing read...
Life Sciences Stats API
The Stats API from Life Sciences — 1 operation(s) for stats.
Life Sciences Studies API
The Studies API from Life Sciences — 3 operation(s) for studies.
Life Sciences Version API
The Version API from Life Sciences — 1 operation(s) for version.
Scroll within the panel for all 22 ·
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).
ClinicalTrials.gov API v2
OPEN COLLECTIONSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Life Sciences Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Life Sciences API Rules
SPECTRALJSON Schema 3
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Examples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 1
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.
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 Life Sciences — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 1
Authentication, authorization, and security posture
← All providers · Data indexed from github.com/api-evangelist/life-sciences · machine-readable index on apis.io