TRV-2026-1435Certified recordPeer-reviewed

AI-assisted characterization of psychedelic clinical trials from ClinicalTrials.gov

Abstract Background The registry record of psychedelic and related rapid-acting compounds is large, heterogeneous and laborious to synthesize by hand. We tested whether a large language model (LLM) with live access to the ClinicalTrials.gov application programming interface (API) could produce a timely, structured and reproducible characterization of this landscape. Methods Cross-sectional analysis of interventional trials on ClinicalTrials.gov as of 13 January 2026. The core-set comprised classic serotonin 5-HT…

Health · The Trace — both readings · certified 2026-10-15 · v1 · article view · machine-readable

Current reading — gain

An LLM connected to the registry API, using documented field-specific query expressions, produced a structured and reproducible map of 412 core-set psychedelic trials plus 300 ketamine/esketamine trials.

Current reading — problem

Open-ended conversational querying by the LLM underestimated the registry record several-fold for some compounds, so unstructured use gave unreliable counts.

What this doesn’t fix

The authors state the approach complements rather than replaces systematic review, and its accuracy against manual extraction remains to be quantified.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1435, v1: “AI-assisted characterization of psychedelic clinical trials from ClinicalTrials.gov.” Truvace, 2026-10-15. /record/TRV-2026-1435 (accessed at citation time). sha256 c0d01eb1f0ca12bf…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1c0d01eb1f0ca…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1435 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.