The substrate, checked against itself

Balance

Omnarai says the same thing in many places — this site, the engine, the Hugging Face datasets, the npm package. They should always agree. Every few minutes each one is re-read from the outside, as raw bytes, and compared to the live numbers. The count below should be zero. When it isn't, it is listed here — what is wrong, what is true, and who fixes it — until it is.

Checking…

reading the live tracker

What is out of sync

Loading…

How it is counted

What this does not cover

Zero is a target, not a proof. This check only sees what it was built to look for, and it can itself be wrong — on its first deploy it raised a false alarm about a page that was correct, and we fixed the checker. A zero here means these checks found nothing, not nothing is wrong.

The first run, 2026-10-14: it found five surfaces stating numbers the live engine contradicted — the front door's Atlas count, the Explore page's tool count, the Atlas page, the researcher page and the release manifest. All five were fixed that day, and the same check now gates every deploy. Pages that state live numbers now fill them in at the moment they are served, so they keep pace with the Atlas as it grows each day. If the engine is slow to answer, a page falls back to the numbers from its last deploy rather than fail — and shows up above as lagging until it catches up.

How it runs

Read-only: public GETs with no keys and no model calls.

Machine twin (JSON) Every fact checked The audit's source Limitations