CDISC Library API
25
AI ReadinessNon-Ready (F)25/100
Community OpenAPI document · agent-readyHealthcareClinical DataapiKey144 EndpointsREST
Know of an official OpenAPI document? Contribute it →
Install Jentic One Beta
Connect the CDISC Library API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CDISC Library API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcdisc.org%2Fcdisc" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcdisc.org%2Fcdisc" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with CDISC Library API.
Search the CDISC Library for standards content
List the standards products the library publishes
Read controlled terminology packages, codelists, and terms
Look up CDASH classes and domains by version
Look up SDTM classes and datasets by version
Use Cases
Patterns agents use CDISC Library API for, with concrete tasks.
★ AI agent clinical standards lookup
An AI agent building clinical data mappings can pull CDISC metadata on demand. Through Jentic the agent searches by intent and the API key never enters its prompt context, so a standards assistant can look up codelists and datasets without a hand-built integration.
Use Jentic to search 'search the CDISC Library', call GET /mdr/search with a query, and read the matching standards content.
Controlled terminology retrieval
A data-management agent needs the exact terms in a controlled terminology codelist. It lists the terminology packages and then reads a codelist's terms, keeping submissions aligned to the published values rather than a stale copy.
List packages with GET /mdr/ct/packages, then read the terms via GET /mdr/ct/packages/{package}/codelists/{codelist}/terms.
SDTM dataset mapping
When mapping source data to SDTM, an agent needs the datasets defined for a version. It reads the SDTM datasets for a version so a mapping workflow builds against the correct structure.
Read SDTM datasets for a version via GET /mdr/sdtm/{version}/datasets and use them to build a mapping.
Key Endpoints
144 endpoints — the cdisc library api serves cdisc's clinical research data standards as structured metadata.
METHOD
PATH
DESCRIPTION
GET
/mdr/search
Search the CDISC Library
GET
/mdr/products
List standards products
GET
/mdr/ct/packages
List controlled terminology packages
GET
/mdr/ct/packages/{package}/codelists/{codelist}/terms
Read a codelist's terms
GET
/mdr/cdash/{version}
Read a CDASH version
GET
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the CDISC Library API by hand means managing its api-key header against api.library.cdisc.org and encoding the search and standards calls yourself. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.
Permission scoping
The library puts the package, codelist, and version in the URL path (/mdr/ct/packages/{package}/codelists/{codelist}/terms), so a rule can pin your agent to a package or standard. You choose the operations it may call, and the whole surface is read-only.
Credential isolation
Your CDISC API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'read a codelist' or 'list SDTM datasets', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using CDISC Library API through Jentic.
Is there a CDISC Library API MCP server?
You don't need an MCP server to give your agent the CDISC Library. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the search and standards operations. That keeps your agent's context free of an extra server's tool definitions.
What authentication does the CDISC Library API use?
It authenticates with an API key sent in the api-key header, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own instance and injected at call time, so it never reaches the agent's context.
Can I look up controlled terminology with the CDISC Library API?
Yes. GET /mdr/ct/packages lists the terminology packages, and GET /mdr/ct/packages/{package}/codelists/{codelist}/terms returns the terms in a specific codelist so a submission uses the published values.
How do I search the CDISC Library through Jentic?
Search Jentic for 'search the CDISC Library', load the input schema, and execute GET /mdr/search with your query. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the CDISC Library API?
Yes. Write a rule that allows only the search and controlled-terminology operations, so the agent can read standards content and codelists and nothing else, and every call it makes is logged. Because the whole surface is read-only, no operation can change library data regardless.
GET STARTED