Lindus Health
Lindus Health is a next-generation contract research organization (CRO) that runs clinical trials end to end for biotech and pharmaceutical sponsors. It pairs Citrus, an AI-assisted trial operating system connecting patient identification through final data capture, with centralized patient identification and enrollment (AI-powered EHR querying, digital pre-screening, centralized patient support), flexible site models spanning site-based, hybrid and fully virtual delivery, and integrated clinical services from protocol design through database lock. Its platform surface covers EDC, eSource, ePRO/eCOA, eConsent and CTMS. The company operates across the US, UK and Europe with APAC partnerships, employs over 160 staff, and works in cardiometabolic, respiratory, psychiatry, women's health and dermatology. Commercial engagements are performance-based with milestone pricing. Lindus Health publishes no public developer API, developer portal or API documentation; its public technical footprint is two open-source CDISC clinical-data repositories.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Lindus Health the way a machine reads it — 1 machine-readable artifact, 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 — Lindus Health scores 17.2/100 (emerging), with a separate agent-readiness read of 0/100 (human only). 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 Lindus Health
Each block below is one kind of artifact we hold for Lindus Health. 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.
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.
Resources
Every other property we hold for Lindus Health — 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
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
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 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/lindus-health · machine-readable index on apis.io