gateway
A blazing fast AI Gateway with integrated guardrails. Route to 1,600+ LLMs, 50+ AI Guardrails with 1 fast & friendly API.
Runssource: GitHubhomepageTypeScriptMITcommit 669825cbe89e
TypeScript, MIT licensed. The project labels itself: ai gateway, gateway, generative ai, hacktoberfest, langchain, llm, llm gateway and llmops.
gateway runs. An Argusic agent installed it in 22 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install and build succeed, the Node.js server starts on port 8787 and responds 200 on /v1, 170 unit 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.
- ResponseService constructor signature drift: test passed 4 args but source expects 2 (RequestContext, HooksService)5 minutes
- Top-level await in src/utils/env.ts incompatible with ts-jest CommonJS transform5 minutes
- jest.mock() paths in 4 test files pointed into tests/ instead of src/3 minutes
- ProviderContext.getHeaders/getBaseURL mock expectations mismatched source API3 minutes
- PreRequestValidatorService.getResponse() return type changed; tests accessed .status on wrapper object2 minutes
- TypeScript error: 'version' missing from Params interface (src/types/requestBody.ts)1 minute
- Install time
- 22 minutes
- Cold machine to finish
- 30 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- npx jest tests/unit/ --no-coverage exited 0, 7 suites passed, 170 tests passed; curl -s -o /dev/null -w '%{http_code}' localhost:8787/v1 returned 200; curl -s -X POST localhost:8787/v1/chat/completions -H 'Content-Type: application/json' -d '{"model":"gpt-4","messages":[{"role":"user","content":"hi"}]}' returned a valid JSON error response
- Model tokens used
- 1,310,677
- Exact commit tested
- 669825cbe89e
- 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.
exited 1 in 1979ms: Server started on 8788 HTTP 200 Port 8787 works, the build server simply hard-codes 8787. The server was already running from earli… exec /bin/sh -lc 'fuser -k 8787/tcp 2>/dev/null; fuser -k 8788/tcp 2>/dev/null; kill %1 %2 2>/dev/null; … succeeded in 0ms: All cleaned All 170 tests pass across 7 test suites, the server launches and responds correctly. Here is my rep… tokens used 1,310,677 All 170 tests pass across 7 test suites, the server launches and responds correctly. Here is my rep…
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.
- Installed in 22 minutes.
- Recovered from all 7 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
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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
Topics (from GitHub)
ai-gatewaygatewaygenerative-aihacktoberfestlangchainllmllm-gatewayllmopsllmsmcpmcp-clientmcp-gatewaymcp-serversmodel-routeropenai
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/gateway)Questions
- Does gateway run?
- Yes. gateway runs. Argusic installed and launched it on a clean machine in 22 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test gateway?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 669825cbe89e. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test gateway?
- The run that produced this verdict cost $0.23: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does gateway take to install?
- 22 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 gateway need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing gateway?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for gateway?
- 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.