Summary
GO terms answered from the ontology, not from memory.
A GO id looks plausible whether or not it exists. This resolves them against QuickGO, so the identifier that goes into a pipeline is one that was checked rather than one that looked right.
What it is
A read layer over the Gene Ontology, served from EBI's QuickGO API. Terms can be searched by keyword or fetched by identifier, and the ontology's own statistics sit alongside them.
What you get
- GO terms searched by keyword, name or definition, scoped to one branch such as biological_process
- The full record for a term you name by its GO id
- An identifier checked for both format and existence before you build on it
- Ontology statistics: term counts and how recently each branch was updated
- Resource paths for a term, its hierarchy, a gene's annotations and a search, addressable directly
Requirements
Node with npm install and npm run build, then one stdio entry in your client config. No account and no key — everything comes from public Gene Ontology data via QuickGO.