aceOmics data discovery agents: Agent-supported retrieval, reanalysis, and synthesis of published omics data
The biomedical literature contains a vast collection of omics studies, yet most published data remain functionally inaccessible for computational reuse. When raw data are deposited in public repositories, essential information for reproducing reported results is dispersed across main text, supplementary files, and code repositories, and in the rarer cases where intermediate data (e.g., protein abundance files) are shared, their location is irregular. Here we present an agentic framework for the agent-supported r…
LLM agents with containerized tools completed five proteomics and RNA-seq reanalyses that closely reproduced authors' deposited abundances, supporting automated reuse of published omics data.
The authors describe the work as a feasibility demonstration, not a validated benchmark of literature-wide performance, and the corpus-scale outputs are not a validated measure of extraction accuracy.
Evidence
- Peer-reviewedPLOS Computational Biology2026-10-06
How should this claim be treated?
Truvace Impact Record TRV-2026-1820, v1: “Omics data discovery agents: Agent-supported retrieval, reanalysis, and synthesis of published omics data.” Truvace, 2026-10-18. /record/TRV-2026-1820 (accessed at citation time). sha256 2fe7c9c535823cc6…
Calibration history
Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.
Certified into the record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1820 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.