Q-omics runs statistics across hundreds of sampling splits before a result ever reaches you — so a hit means something held up, not that it happened to clear p<0.05 once. Query it as an AI-agent tool today, or call the REST API directly once general access opens.
POST /qomics/api/plot { "class_name": "box_plot", "q_data": { "sample_type": "Tissue", "lin_code": "BRCA", "x_type": "rna", "x_symbol": "TP53" } } // 200 OK { "chart_type": "box", "stats": { "p_value": 3.1e-08, "fold_change": -1.842 }, "criteria": "Comparison: Group1 (Low) vs Group2 (High) rna — median split; Welch t-test", "data": { "counts": { "group1": 274, "group2": 273 } } }
Same curated warehouse, two doors — pick by what you're building.
Connect Claude, ChatGPT, or any MCP-compatible client. Your LLM resolves genes, drugs and lineages in natural language, then calls 17 read-only tools — survival, correlation, association, normal-vs-tumor, and more — across guided analyses and a PQL query layer for anything the fixed tools don't cover.
Call the same curated data directly over JSON — browse hit tables, pull summary rollups, render plots, or run the sampling-consensus grid — without going through an LLM. The contract below is stable; general access is opening in phases.
Pre-computed and validated across sampling splits and cancer lineages before it's ever queried — not raw counts run fresh per request.
Everything a client needs to build against — the reference, the data it's built on, and the trust questions that come before either.
Request/response envelopes, endpoint map, operating limits, worked examples.
The verb-pipeline query language behind pql_run — sources, verbs, aggregates, ~40 worked examples.
All 17 agent tools, parameters, and which one to reach for by question shape.
Every data type, valid combination, and lineage-availability table — plus what's honestly not supported.
Auth model, data handling, de-identification, and the query guard's exact limits.
Accounts, API keys, acceptable use, and data-handling policy.
Q-omics is in developer preview. The MCP connector is open today; direct REST API access is opening in phases as usage limits and API keys roll out. Request access to get on the list.