Collaborative Drug Discovery
Collaborative Drug Discovery (CDD) provides the CDD Vault, a cloud‑based scientific data management and electronic lab notebook platform for drug discovery. Founded in 2004 as a spin‑out from Eli Lilly, CDD serves biotech, pharma, CROs and academic labs, offering tools for chemistry, biology, assay data, AI‑driven analysis, and secure collaboration. The platform supports small‑molecule, biologics, CRISPR, PROTAC and antibody‑drug conjugate projects, with extensive data visualization, inventory, and compliance features.
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 Collaborative Drug Discovery the way a machine reads it — 38 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 — Collaborative Drug Discovery scores 37.9/100 (thin), with a separate agent-readiness read of 28/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.
Why this profile is thin
the company publishes no developer documentation host and no machine-readable contract on its own domain
This is an honest zero, not a gap in our research. Collaborative Drug Discovery does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://www.collaborativedrug.com/mcp→ HTTP 403https://www.collaborativedrug.com/→ HTTP 200https://www.nasdaqprivatemarket.com/→ HTTP 200
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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from Collaborative Drug Discovery's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/collaborative-drug-discovery/"
title="Collaborative Drug Discovery on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/collaborative-drug-discovery.svg"
alt="Collaborative Drug Discovery Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/collaborative-drug-discovery/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/collaborative-drug-discovery/"
title="Collaborative Drug Discovery on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/collaborative-drug-discovery/card.svg"
alt="Collaborative Drug Discovery Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Collaborative Drug Discovery
Each block below is one kind of artifact we hold for Collaborative Drug Discovery. 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 31
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.
Collaborative Drug Discovery API Executions API
Track asynchronous API request executions
Collaborative Drug Discovery Batch Move Jobs API
Asynchronous batch move jobs
Collaborative Drug Discovery Batches API
Batches handling
Collaborative Drug Discovery Collections API
Collections of molecules
Collaborative Drug Discovery Control Layouts API
Control well layouts for protocols and runs
Collaborative Drug Discovery Datasets API
Public and vault datasets
Collaborative Drug Discovery Deep Learning Bioisosteres API
Deep learning bioisostere suggestions
Collaborative Drug Discovery Deep Learning Similarity API
Deep learning molecular similarity
Collaborative Drug Discovery Dose Response Calculations API
Protocol dose response calculations management
Collaborative Drug Discovery Dose Response Data Series API
Dose response data series management
Collaborative Drug Discovery ELN Entries API
Electronic lab notebook entries
Collaborative Drug Discovery Exports API
Asynchronous data exports
Collaborative Drug Discovery Fields API
Vault field definitions
Collaborative Drug Discovery Files API
File attachments
Collaborative Drug Discovery Import Parsers API
Import parsers for structured data files
Collaborative Drug Discovery Inventory API
Sample inventory locations
Collaborative Drug Discovery Inventory Samples API
Inventory samples and their events
Collaborative Drug Discovery Mapping Templates API
Import mapping templates
Collaborative Drug Discovery Molecules API
Molecules handling
Collaborative Drug Discovery Plates API
Plates of wells
Collaborative Drug Discovery Projects API
Projects within a vault
Collaborative Drug Discovery Protocols API
Protocols and their readout data
Collaborative Drug Discovery Readout Rows API
Rows of protocol readout data
Collaborative Drug Discovery Registration Forms API
Registration forms
Collaborative Drug Discovery Registration Systems API
Registration systems
Collaborative Drug Discovery Runs API
Runs of protocol data
Collaborative Drug Discovery Searches API
Saved searches
Collaborative Drug Discovery Slurps API
Data import jobs (slurps)
Collaborative Drug Discovery Status API
Vault operational status
Collaborative Drug Discovery Users API
Users management
Collaborative Drug Discovery Vaults API
Vaults management
Scroll within the panel for all 31 ·
Semantic 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.
Spectral 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.
Security Posture 4
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 Collaborative Drug Discovery — 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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Access & Security 8
Authentication, authorization, and security posture
Scroll within the panel for all 8 ·
Operate 1
Status, limits, changes, and where to get help
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/collaborative-drug-discovery · machine-readable index on apis.io
This is an independent, third-party profile of Collaborative Drug Discovery, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.