DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to pull On Co cancer records into a script via CLI or API with On Co

Use the onco command or the static JSON API to load cancer records into your own analysis.

  • Research
  • Intermediate
  • 30 minutes
  • From the README
  • Any agent

Who it is forA data analyst or developer who needs structured oncology records, such as cancers, drugs or trials, for a dashboard, report or dataset.

The problemOncology facts are scattered across journals, regulators and registries, which makes repeatable structured pulls hard.

The outcomeA script that reads On Co records as JSON, with the required attribution line carried through to the output.

What you need first

  • Node.js and npm (inferred, needed for the repository scripts)
  • Git and a GitHub account for cloning the repository or opening issues and pull requests
  • An MCP-capable client or agent for the MCP server (optional)

Steps

  1. Install Node.js so that npx is available. (inferred, check the README)
  2. Run npx onco to see the command-line tool and its options.
  3. Open https://onco.cc/api/ for the endpoint list and https://onco.cc/api/v1/openapi.json for the OpenAPI 3.1 schema.
  4. Fetch the JSON records your script needs from the static JSON API under https://onco.cc/api/v1/.
  5. Keep the attribution line "Data from On Co (onco.cc)" in every export or report you publish.

Prompt for your agent

Using the OnCo JSON API at https://onco.cc/api/v1/ and the OpenAPI schema at https://onco.cc/api/v1/openapi.json, fetch all records of the kind <kind name> and write them to a CSV file with the attribution line "Data from OnCo (onco.cc)" in the header. Verify that the row count matches the endpoint's reported count and report any record missing a primary link.

Caveat. The corpus is licensed CC BY-NC 4.0, so commercial use requires contacting On Co for a data licence, as the README states.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page