api-gateway

API Gateway bridging modern and legacy APIs with WSDL-to-OpenAPI, SOAP-to-REST, XML, OAuth2, and GraphQL.

Runssource: GitHubhomepageJavaApache-2.0commit ca74996ec7aa

Java, Apache-2.0 licensed. The project labels itself: api, api gateway, graphql, oauth2, openapi, rest, soap and wsdl.

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

The Membrane API Gateway 7.6.3-SNAPSHOT distribution built, launched via membrane.sh, and served live HTTP APIs on ports 2000 and 9000 with correct 200/401 behavior.

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.06 (measured)
recorded runs
1
last tested
stars
660
forks
186
open issues
45
watchers
42
size
66 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 api-gateway, 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.

  • java/mvn not found in container3 minutes
  • tar could not extract membrane zip and membrane.sh lacked +x after extraction2 minutes
  • mvn test -pl core: Http2ClientServerTest.testStreamInfoProperlyClosed failed (expected CLOSED, got HALF_CLOSED_LOCAL)1 minute
Install time
28 minutes
Cold machine to finish
30 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
mvn integration-test -pl distribution exited 0 (Tests run: 437, Failures: 0, Errors: 0, Skipped: 8); curl http://localhost:2000/ returned 200, /shop/v2/products returned 200 with JSON of 17 products, /api-docs 200, /fact 200, :9000 admin 401 unauthenticated and 200 with -u admin:admin
Model tokens used
503,832
Exact commit tested
ca74996ec7aa
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.

- No Java or Maven was present; installed Temurin JDK 21.0.12.1 and Maven 3.9.16 into `$HOME/tools`…
- `mvn install -DskipTests` on the Membrane 7.6.3-SNAPSHOT sources (annot, core, distribution, war,…
**Error records**
- `java`/`mvn` not found — fix: downloaded portable JDK 21 + Maven 3.9.16 binaries (~3 min).
- `mvn test -pl core`: 5367 tests, 1 failure (`Http2ClientServerTest.testStreamInfoProperlyClosed`,…
- Extracted ZIP with `tar` failed (it's a zip; `python3 zipfile` worked), and `./membrane.sh` was n…
- `mvn test -pl test` ran 0 tests; the module contains only support classes, not a JUnit suite — no…
**Real verification**
- `./membrane.sh` started and its log printed `Membrane API Gateway 7.6.3-SNAPSHOT up and running!`…
- `curl http://localhost:2000/` → 200, JSON `{"time": ...}`; `/api-docs` → 200; `/shop/v2/` → 200 J…
- `mvn integration-test -pl distribution` (`ExampleTests`/`ExampleTestsWithoutInternet`, which star…
- The 1 leftover `RouterCLI` process was terminated after verification.

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 Apache-2.0, as reported by its host.

What did not, or is not known

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

Of the 62 api projects Argusic has installed and timed, api-gateway was the 61st fastest to reach a running state, and 39 of 62 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.

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.06

Topics (from GitHub)

apiapi-gatewaygraphqloauth2openapirestsoapwsdlxml

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/api-gateway.svg)](https://argusic.com/subject/api-gateway)

Questions

Does api-gateway run?
Yes. api-gateway runs. Argusic installed and launched it on a clean machine in 28 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test api-gateway?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit ca74996ec7aa. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test api-gateway?
The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does api-gateway take to install?
28 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-gateway need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing api-gateway?
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 api-gateway compare with the alternatives?
Of the 62 api projects Argusic has installed and timed, api-gateway was the 61st fastest to reach a running state, and 39 of 62 reached one at all.
Where is the evidence for api-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.

Discussion