api-umbrella
Open source API management platform
Could not verifysource: GitHubRubyMITcommit b3fbd68d6fa2
Ruby, MIT licensed. The project labels itself: api gateway, api management, api manager, lua, luajit, nginx and openresty.
Argusic could not get api-umbrella running. An Argusic agent installed it in 45 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Build-deps and some deps staged (hugo v0.164.0, node v22.23.1, pnpm, cue, envoy, envoy-control-plane) but full build with Fluent Bit, OpenResty, TrafficServer from source could not complete within time/resources.
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 20 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.
- Build failed at deps:fluent-bit: Fluent Bit compilation from source needs flex/bison/libyaml-dev, not installed and cannot be installed without root15 minutes
- npm install -g fails without root2 minutes
- rsync not found1 minute
- PNPM_HOME unbound variable1 minute
- chrpath not found1 minute
- Install time
- 45 minutes
- Cold machine to finish
- 27 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- Model tokens used
- 193,432
- Exact commit tested
- b3fbd68d6fa2
- 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.
- How the result was proved
- the agent reported that it did not verify the output
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- **cue**, **envoy** (v1.38.0), **envoy-control-plane** (v1.3.0) binaries - Build-deps (hugo, nodejs, pnpm) stamp complete ### Errors encountered and patched (5 total): 1. **rsync missing** → replaced with `cp -a` in `tasks/build-deps/nodejs` 2. **npm -g permission denied** → set npm prefix to `build/work/dev-env` 3. **PNPM_HOME unbound** → hardcoded store-dir path in `tasks/build-deps/pnpm` 4. **chrpath missing** → commented out in `tasks/deps/envoy` 5. **Fluent Bit build fails** (needs flex/bison/libyaml-dev which require root) — patched `FLB_RECO… ### Blockers: - No **Ruby** in container (needed for tests) and no precompiled binary found - No root access to install system packages - Full source compilation of Fluent Bit, OpenResty, TrafficServer would take hours
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
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
- Took 45 minutes to install, slower than the median of the 6 comparable projects Argusic has measured.
Of the 7 api-gateway projects Argusic has installed and timed, api-umbrella was the 7th fastest to reach a running state, and 4 of 7 reached one at all.
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 | Did not run | 20.00 | 0.31 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.15 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/api-umbrella)Questions
- Does api-umbrella run?
- Argusic could not verify that api-umbrella runs. Argusic installed and launched it on a clean machine in 45 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test api-umbrella?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b3fbd68d6fa2. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test api-umbrella?
- The run that produced this verdict cost $0.31: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does api-umbrella take to install?
- 45 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 api-umbrella need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing api-umbrella?
- 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 api-umbrella compare with the alternatives?
- Of the 7 api-gateway projects Argusic has installed and timed, api-umbrella was the 7th fastest to reach a running state, and 4 of 7 reached one at all.
- Where is the evidence for api-umbrella?
- 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.