Yes. apinto runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 7 errors on the way, and recorded the session.

How did Argusic test apinto?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 708a2ec565a0. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test apinto?

The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does apinto take to install?

14 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 apinto need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing apinto?

7 things broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for apinto?

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.

apinto

基于golang开发的网关。具有各种插件，可以自行扩展，即插即用。此外，它可以快速帮助企业管理API服务，提高API服务的稳定性和安全性。

Runssource: GitHub homepageGoApache-2.0commit 708a2ec565a0

Go, Apache-2.0 licensed. The project labels itself: api, api gateway, apigateway, apinto, dubbo2, gateway, go and goku.

apinto runs. An Argusic agent installed it in 14 minutes and hit 7 errors on a clean machine with no GPU, and the whole session was recorded.

Apinto API gateway v0.x builds from source, starts as a daemon, serves the admin API on :9400 and the proxy gateway on :8099, and passes 15 of its 15 functional test packages (checker, auth, plugins, strategies, protobuf parsing).
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 82.9 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 82.9 / 100
cost of the verifying run: $0.10 (measured)
recorded runs: 1
last tested: 2026-10-06
stars: 1,679
forks: 260
open issues: 48
watchers: 31
size: 6 MB
created: 2021-07-19
last push: 2026-09-22

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-06. 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 apinto, 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.

Go 1.25.0+ compiler not found in container1 minute
drivers/plugins/gzip/gzip_test.go: TestFilter/wantCompress SIGSEGV (nil pointer dereference)
drivers/plugins/params-check/check_test.go: can not find body param '$.search[0].val'
drivers/plugins/params-check-v2/check_test.go: build failed - MockHeaderReader missing SetCookie method
drivers/service/send_test.go: ':invalid balance' - depends on external discovery service
drivers/output/syslog/output_test.go: connection refused on tcp 127.0.0.1:514

Install time: 14 minutes
Cold machine to finish: 14 minutes
Errors hit and fixed: 7 hit, 1 fixed with no human help
How the result was proved: go build produced 135MB binary; /tmp/apinto_test version printed version info; /tmp/apinto_test start launched master+worker+admin processes; curl http://127.0.0.1:9400/ returned HTTP 200 with JSON body; curl http://127.0.0.1:8099/ returned HTTP 404; go test passed on 15 test packages
Model tokens used: 107,253
Exact commit tested: 708a2ec565a0
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.

1. go build succeeded → 135MB binary at /tmp/apinto_test
2. /tmp/apinto_test version → prints version info
3. /tmp/apinto_test start → master/worker/admin processes launched
4. curl http://127.0.0.1:9400/ → HTTP 200
5. curl http://127.0.0.1:8099/ → HTTP 404 (expected, no routes)
6. go test on 15 packages → all passed
Here is my final report:
2026-10-06T13:30:16.468206Z ERROR codex_core::session: failed to record rollout items: thread 01a11…
2026-10-06T13:30:16.468252Z ERROR codex_core::session: failed to record rollout items: thread 01a11…
tokens used
107,253
Here is my final report:

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.
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 14 minutes to install, slower than the median of the 15 comparable projects Argusic has measured.
Hit 7 errors during setup, 6 of which were not solved.
Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 16 api projects Argusic has installed and timed, apinto was the 11th fastest to reach a running state, and 11 of 16 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 by	attempt	outcome	score	cost USD	when
Argusic Runner	1/3	Runs	82.86	0.10	2026-10-06 13:30 UTC

Topics (from GitHub)

api api-gateway apigateway apinto dubbo2 gateway go goku golang grpc loadbalancer microservice middleware plugin proxy router servicemesh

Embed the badge

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

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

Questions

Does apinto run?: Yes. apinto runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 7 errors on the way, and recorded the session.
How did Argusic test apinto?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 708a2ec565a0. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test apinto?: The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does apinto take to install?: 14 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 apinto need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing apinto?: 7 things broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does apinto compare with the alternatives?: Of the 16 api projects Argusic has installed and timed, apinto was the 11th fastest to reach a running state, and 11 of 16 reached one at all.
Where is the evidence for apinto?: 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.