9Router: evaluate an AI gateway without assuming unlimited access
9Router first run: resolve the 20127 and 20128 examples
Keep the published CLI and repository application distinct and verify the listening port before configuring a client.
What you will learn
- Identify the installation path
- Prepare a limited source trial
- Check the client and stop cleanly
Before you start
- Basic command-line and configuration reading
- Ability to work in a disposable authorized environment
Design an evidence record that separates requested model, actual attempts and accepted response without retaining secrets.
Key takeaways
- Source scripts explicitly specify 20127.
- A README CLI example is not every launch mode.
- Use the key and model from the actual instance.
Identify the installation path
The README documents npm installation of the published 9router CLI and a dashboard on 20128. The repository root is a private application package; its dev and start scripts explicitly pass --port 20127. These are different launch paths.
For a source trial, inspect package.json and use the port printed by the actual process. Do not assume that setting PORT=20128 will override an explicit command-line option. Record the command and resulting listener together.
Prepare a limited source trial
Use an audited checkout, review dependency lifecycle scripts and protect the environment file. Build and start through the repository scripts after approving those local changes. The start script loads custom-server.js rather than a bare Next server.
Configure one provider through the application’s approved account flow and use the gateway key shown for that instance. Never paste provider or gateway secrets into article examples. Begin with synthetic text and no fallback.
Check the client and stop cleanly
Point the client to the observed local port and the documented /v1 base path. Choose a model actually available in that configuration. Compare the returned text and any error status with the gateway and provider records.
Stop the foreground process after the trial and preserve a private configuration backup if continuing later. This procedure was not executed for the series; it does not assert that every client accepts the same fields or endpoint features.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Record CLI versus source installation explicitly.
- 2
Inspect startup output and use its actual port.
- 3
Validate one approved model route, then stop the trial.
Copy-ready example
npm run build
npm run start
# Inspect startup output: the pinned source script passes --port 20127.Frequently asked questions
Why does localhost:20128 fail for my source checkout?
The inspected repository scripts pass 20127. Check the running command and listener.
Can I use any model name in the client?
Select an identifier supported by the configured provider and gateway.
Sources
- 9Router / README.mdSource checked 2026-09-18
- 9Router / package.jsonSource checked 2026-09-18
- 9Router / custom-server.jsSource checked 2026-09-18