9router

Unlimited FREE AI coding. Connect Claude Code, Codex, Cursor, Cline, Copilot, Antigravity to FREE Claude/GPT/Gemini via 40+ providers. Auto-fallback, RTK -40% tokens, never hit limits.

Runssource: GitHubhomepageJavaScriptMITcommit 39e36d3d0c84

JavaScript, MIT licensed. The project labels itself: ai agents, ai gateway, anthropic, chatgpt, claude, claude code, cline and codex.

9router runs. An Argusic agent installed it in 8.2 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Root npm install completed, npm run build succeeded, the standalone Next.js app serves the login page (200), models API (200 with JSON model list), and version endpoint (200), and the test suite runs 2562 passing tests.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.09 (measured)
recorded runs
1
last tested
stars
29,774
forks
5,605
open issues
2,233
watchers
159
size
15 MB
created
last push

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.

Time lost to each failure while testing 9router, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Node.js v18.19.1 too old for Next.js 16 (requires >=20.9.0)1.5 minutes
  • vitest 4.x native binding error for rolldown (missing @rolldown/binding-wasm32-wasi)1 minute
  • npm install in tests/ failed with Cannot read properties of null (reading edgesOut)0.5 minutes
Install time
8 minutes
Cold machine to finish
42 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
npm run build succeeded (next build --webpack); app started with custom-server.js on port 20128 returning 200 on /login, /api/v1/models (JSON model list), /api/version (currentVersion 0.5.86); npx vitest run in tests/ returned 2562 passed out of 2737 tests
Model tokens used
463,273
Exact commit tested
39e36d3d0c84
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.

  "errors": [
    {"msg": "Node.js v18.19.1 too old for Next.js 16 (requires >=20.9.0)", "fix": "Downloaded Node …
    {"msg": "npm install in tests/ failed with Cannot read properties of null (reading edgesOut)", …
    {"msg": "vitest 4.x native binding error for rolldown (missing @rolldown/binding-wasm32-wasi)",…
  ],
  "test_depth": "tier1_real",
  "notes": "2562 tests passed, 102 failed, 14 expected fail, 59 skipped (277 test files). 41 test f…
  "verified_how": "npm run build succeeded (next build --webpack); app started with custom-server.j…
  "final_state": "Root npm install completed, npm run build succeeded, the standalone Next.js app s…
}
tokens used
463,273

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 3 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 MIT, as reported by its host.

What did not, or is not known

  • Took 8.2 minutes to install, slower than the median of the 18 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 19 ai-agents projects Argusic has installed and timed, 9router was the 12th fastest to reach a running state, and 12 of 19 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.
  • A quick evaluation: it was running 8.2 minutes after the clone.

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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.09

Topics (from GitHub)

ai-agentsai-gatewayanthropicchatgptclaudeclaude-codeclinecodexcopilotcursordeepseekfree-aigeminigemini-clillmllm-gatewayopenaiopenai-proxyqwentoken-saver

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/9router.svg)](https://argusic.com/subject/9router)

Questions

Does 9router run?
Yes. 9router runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test 9router?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 39e36d3d0c84. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test 9router?
The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does 9router take to install?
8.2 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 9router need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing 9router?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does 9router compare with the alternatives?
Of the 19 ai-agents projects Argusic has installed and timed, 9router was the 12th fastest to reach a running state, and 12 of 19 reached one at all.
Where is the evidence for 9router?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion