An open mind, built from verified knowledge.
Olo Commons grows every 15 minutes from sources the world already trusts: Wikipedia (in English and Spanish), Wikidata, the Internet Archive, arXiv, Project Gutenberg, PubMed and Data.gov. Every fact keeps where it came from, its licence and a fingerprint of its content. Anyone can read it. Only verified sources can write to it. The Olo in helius-olo.io and in the Helius app think with it.
The brain
Watch it think
Every point of light is an atom of knowledge with its provenance; every thread, a connection Olo found between two of them. Atoms arrive all day and settle into the graph while you watch. Drag to orbit, pinch or scroll to zoom, tap an atom to light up what it knows.
Growth
Thirty days of learning
Ask
Ask the Commons, get an answer that was checked
Olo finds the passages (meaning search merged with keyword search), writes an answer in a few sentences, then Zeus checks every sentence against the passages it cites: supported, contradicted or not covered, with the quoted evidence. Nothing is asserted without a source you can open.
Curiosity
What Olo is reading next
When a question finds nothing, Olo keeps the topic words (never the question) and goes looking for them in its sources on the next ingest. This is the Commons growing toward what people actually ask.
Zeus
The model that checks the answers
Zeus is Olo's own verifier: a small open-weight model fine-tuned on the Commons, trained in the open and scored on a frozen test split after every run. Every number here is measured; nothing is estimated.
Latest
What Olo read in the last hours
Sources
Who Olo is allowed to learn from
Only enabled, openly licensed sources are ever fetched. Each has a trust level that feeds the quality score of every atom.
Build
Projects on the Commons
Apps, research, datasets and tools built on Olo knowledge. Add yours; it appears once reviewed.
Build on the Commons
Cited passages, or a checked answer, in one call
Read-only, free, no key needed. 120 questions an hour per address; partners get 3,000 with a key. Query text is never stored. olo-query returns passages; olo-answer adds a drafted answer with a verdict on every sentence.
Playground
See the raw response
// response appears here
Bulk data
Take the whole Commons with you
Page through every atom and every link, in creation order, with the anon key. Build a dataset, a graph, a model, an index. Attribute the compilation (CC BY-SA 4.0) and respect each atom's licence.
POST /rest/v1/rpc/olo_export
{"p_after": "1970-01-01", "p_limit": 500}
→ { atoms: [...], next_after: "2026-10-20T18:15:03Z" }
POST /rest/v1/rpc/olo_links_export
{"p_after": "1970-01-01", "p_limit": 2000}
Headers: apikey: <anon key>, Content-Type: application/json. Pass the returned next_after as p_after for the next page.
Starter kits
Three things you can ship this weekend
Each one is a single file in the repository. Copy it, change the question, you have a product.
A chatbot that cites
Asks the Commons first, then any LLM, and prints the answer with numbered sources. Works with Claude, GPT or a local model.
examples/cited-chat.mjs ›A research notebook
Pulls every atom on a topic into a pandas DataFrame with provenance columns, ready for analysis or a thesis appendix.
examples/notebook.py ›The brain as a dataset
Exports atoms and links to GraphML or JSON for Gephi, NetworkX or your own visualisation.
examples/graph-export.mjs ›Contribute
Four ways in, from five minutes to a weekend
Propose a source
Know an open, trustworthy source Olo should read? Tell us the licence and why. Reviewed in public.
Flag a bad atom
Wrong, outdated, duplicated or badly extracted? Send the atom's fingerprint and what is wrong. Fixes land in the next ingest.
Add a source connector
One function in olo-ingest that returns candidates from a public API, plus a registry row. Merged connectors earn HLS from the treasury and a Builder mark on your profile.
Build and list a project
Ship something on the Commons and add it to the gallery above. Approved projects are featured here and in the Helius app.
People building this
Contributors
Towards Web 5
Verified people. Verified knowledge.
Helius verifies that a real person was really there. Olo Commons verifies where a fact came from. Put the two together and you get a web where both the people and the knowledge can be trusted, and where the record of what humanity knows belongs to everyone, like the Internet Archive and Wikipedia before it.
Protection
How the Commons is kept safe
Write-only by the server
No browser, app or API key can add or change knowledge. Only the hourly ingester, running inside Supabase with the service role, writes.
Allow-listed sources
The ingester can only fetch sources that are enabled in the registry. A new source needs a licence and a review before a single byte is read.
Fingerprinted
Every atom carries a SHA-256 of its content and the time it was retrieved. Duplicates are refused; tampering is detectable.
Nothing personal
Only public knowledge is stored. Questions are never kept, only their length; addresses are hashed with a daily salt for rate limiting.