TokenHub
TokenHub gives enterprises a private gateway to unify AI model access and governance, making every request controllable, traceable, and attributable.
Runssource: GitHubhomepageGoApache-2.0commit 08db06008d68
Go, Apache-2.0 licensed. The project labels itself: ai, ai gateway, enterprise and gateway.
TokenHub runs. An Argusic agent installed it in 36.3 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
TokenHub Go backend built and launched on :8080 with SQLite, serving health/liveness/readiness at HTTP 200 and an OpenAPI spec with 21 endpoints. Frontend builds and all 521 tests pass. Backend non-server test suite passes. 178 repo gate tests pass.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Backend server full test suite times out (>120s) without PostgreSQL - 292 test files contain integration tests requiring external services5 minutes
- Go compiler (Go) not found on system3 minutes
- Node version too old: v18.19.1, project requires v22.23.12 minutes
- Frontend component tests (vitest) require Node >=22, failed with Node 18
- 5 repo gate tool tests fail with Node 18 (TypeScript ESM import not supported)
- Install time
- 36 minutes
- Cold machine to finish
- 37 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- Backend: curl http://localhost:8080/healthz returned 200, /livez returned 200, /readyz returned 200, /openapi.json returned 200 with 21 API paths. Frontend: npm run test:domain exited 0 (182 pass), npm run test:components exited 0 (339 pass), npm run build succeeded. Backend: go test across 13 packages all pass. Repo gates: node --test tools/*.test.mjs exited 0 (178 pass).
- Model tokens used
- 325,534
- Exact commit tested
- 08db06008d68
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
} print() print(\"ARGUSIC_RESULT: \" + json.dumps(report)) '" in /work/repo succeeded in 0ms: Start epoch: 1791481440 Now epoch: 1791483617 Elapsed minutes: 36.3 Much better - 36.3 minutes. Let me output the final answer. tokens used 325,534 Much better - 36.3 minutes. Let me output the final answer.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 36.3 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.
Of the 237 ai projects Argusic has installed and timed, TokenHub was the 231st fastest to reach a running state, and 168 of 237 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.12 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.38 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tokenhub)Questions
- Does TokenHub run?
- Yes. TokenHub runs. Argusic installed and launched it on a clean machine in 36 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test TokenHub?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 08db06008d68. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test TokenHub?
- The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does TokenHub take to install?
- 36.3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does TokenHub need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing TokenHub?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does TokenHub compare with the alternatives?
- Of the 237 ai projects Argusic has installed and timed, TokenHub was the 231st fastest to reach a running state, and 168 of 237 reached one at all.
- Where is the evidence for TokenHub?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.