Use case
Oncologists, clinical researchers, or pharma intelligence staff who need to quickly understand a cancer type, target, therapy, or trial work through oncology material scattered across literature databases, trial registries, and institutional pages, and must obtain a cited entity page (cancer/therapy/target/trial/institution/person) or structured data for downstream judgment.
The current alternative is users searching back and forth across literature databases, trial registries, and institutional pages, or using differently-purposed existing resources such as Onconetix stock information, Oncolink patient education materials, and ONCO Inc. oncology data management software, none of which provide a unified, cited entity-level knowledge graph.
Public materials show oncology information is scattered across literature databases, trial registries, and institutional pages, forcing users to search back and forth and stitch it together; OnCo's positioning as a public knowledge graph with one page per entity indicates it targets friction in retrieval and consolidation.
xOcto's call
Demand is evidenced
The trend is that domain knowledge is being broken into structured entities that AI can call directly, rather than another review article. A wedge exists in similarly literature-heavy, long-decision-chain fields such as rare disease, pharmacovigilance or trial recruitment, packaging one-page-per-entity plus citations as a data layer that hospitals or pharma systems can query, sold via data subscription or API calls; pricing is not disclosed.
Reason to use it
Why users would choose it
Inference: compared with manual cross-database searching, OnCo reduces the burden of per-database retrieval and manual stitching by organizing cancers, therapies, targets, trials, institutions, and people into one cited page each and offering a JSON API, MCP server, and CLI, so oncologists, clinical researchers, and pharma intelligence staff who need programmatic access or a quick entity-level overview would choose it when looking up a cancer type or target.
Where the easy answer breaks down
The tension worth following
An English validation note will follow from the public evidence.
If this is your job
Worth trying. Inference: compared with manual cross-database searching, OnCo reduces the burden of per-database retrieval and manual stitching by organizing cancers, therapies, targets, trials, institutions, and people into one cited page each and offering a JSON API, MCP server, and CLI, so oncologists, clinical researchers, and pharma intelligence staff who need programmatic access or a quick entity-level overview would choose it when looking up a cancer type or target.
Entry and what to borrow
The trend is that domain knowledge is being broken into structured entities that AI can call directly, rather than another review article. A wedge exists in similarly literature-heavy, long-decision-chain fields such as rare disease, pharmacovigilance or trial recruitment, packaging one-page-per-entity plus citations as a data layer that hospitals or pharma systems can query, sold via data subscription or API calls; pricing is not disclosed.