aperture
⚡️L402 (Lightning HTTP 402) Reverse Proxy ⚡️
Runssource: GitHubhomepageGoMITcommit 355c52d6bb9b
Go, MIT licensed. The project labels itself: api gateway, bitcoin, http402, lightning network, macaroons and reverse proxy.
aperture runs. An Argusic agent installed it in 3 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Both binaries (aperture and aperturecli) compile and run. All 14 test suites pass. The server starts on 127.0.0.1:11010 (HTTP/2 cleartext) and serves Prometheus metrics on 127.0.0.1:11011. The CLI reports its version and dumps its schema as JSON.
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.
- Go 1.26+ not installed in container1.5 minutes
- Config validation: authenticator had conflicting lndhost+passphrase and missing lnd TLS files1 minute
- SQLite 'out of memory (14)' error when opening DB0.5 minutes
- Prometheus and main server bound to same port (11010) causing silent crash0.5 minutes
- Install time
- 3 minutes
- Cold machine to finish
- 22 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- make unit: all 14 test packages PASS (netutil, l402, mint, mpp, auth, lnc, aperturedb, pricer, proxy, admin, challenger, aperture, mppvectors, meterd). ./aperture --insecure launched and served HTTP: curl http://127.0.0.1:11010/ returned 404, curl http://127.0.0.1:11011/metrics returned 200 with Prometheus metrics. aperturecli version returned 'aperturecli version 355c52d'. aperturecli schema returned valid JSON schema.
- Model tokens used
- 194,137
- Exact commit tested
- 355c52d6bb9b
- 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.
/bin/sh -lc 'cd /work/repo && ls -la aperture aperturecli && echo "---" && echo "Build: $(stat --fo…
succeeded in 0ms:
-rwxrwxr-x 1 runner runner 76118261 Oct 27 04:52 aperture
-rwxrwxr-x 1 runner runner 20518075 Oct 27 04:52 aperturecli
Build: 1793076731
Now: 1793077714
All verified. Here's the final report:
**ARGUSIC_RESULT:** {"install_succeeded":true,"launch_succeeded":true,"install_minutes":3.0,"errors…
tokens used
194,137
All verified. Here's the final report:
**ARGUSIC_RESULT:** {"install_succeeded":true,"launch_succeeded":true,"install_minutes":3.0,"errors…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 3 minutes, faster than the median of the 31 comparable projects Argusic has measured.
- Recovered from all 4 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.
Of the 32 api-gateway projects Argusic has installed and timed, aperture was the 12th fastest to reach a running state, and 22 of 32 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 3 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
Topics (from GitHub)
api-gatewaybitcoinhttp402lightning-networkmacaroonsreverse-proxy
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/aperture)Questions
- Does aperture run?
- Yes. aperture runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test aperture?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 355c52d6bb9b. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test aperture?
- The run that produced this verdict cost $0.61: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does aperture take to install?
- 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 aperture need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing aperture?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does aperture compare with the alternatives?
- Of the 32 api-gateway projects Argusic has installed and timed, aperture was the 12th fastest to reach a running state, and 22 of 32 reached one at all.
- Where is the evidence for aperture?
- 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.