APIAuto
☔ 敏捷开发最强大易用的接口工具，机器学习零代码测试与 AI 问答、生成代码与静态检查、生成文档与光标悬浮注释，腾讯、华为、SHEIN、传音、工行等使用 ☔ The most advanced tool for HTTP API. Machine learning no-code testing and AI assistant, generating codes and static analysis, generating comments and floating hints. Used by Tencent, Huawei, SHEIN, TRANSSION, ICBC, etc.
Runs with mockssource: GitHubhomepageJavaScriptApache-2.0commit f2042ae79d14
JavaScript, Apache-2.0 licensed. The project labels itself: aitesting, api, api testing, apijson, apitesting, artificial intelligence, autotesting and documentation tool.
APIAuto runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The server starts, prints the startup banner to stdout, and all three endpoints (/test/status, /test/start, /test/compare) respond with correct HTTP status codes and valid JSON bodies.
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 92 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.
- SyntaxError: Cannot use import statement outside a module in js/main.js:87-88 — two import statements with ES module syntax inside a require()-based eval() block in the Node.js path2 minutes
- Install time
- under a minute
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- node js/server.js starts without error and prints startup banner; curl http://localhost:3000/test/status returns HTTP 200 with JSON body containing code:200 and progress fields; curl -X POST http://localhost:3000/test/compare -d '{}' returns HTTP 200 with JSON comparison result; curl http://localhost:3000/test/start returns HTTP 302 redirect to /test/status
- Model tokens used
- 33,013
- Exact commit tested
- f2042ae79d14
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- `test_depth`: "tier2_mock" — the server starts and processes requests. The `/test/compare` endpoi…
- `verified_how`: "node js/server.js exits without error; curl http://localhost:3000/test/status re…
- `final_state`: "The server starts, prints the startup banner, and responds on all three endpoints…
exec
/bin/sh -lc 'pkill -f "node js/server.js" 2>/dev/null; sleep 0.3' in /work/repo
exited 143 in 0ms:
exec
/bin/sh -lc "ARGUSIC_RESULT: {\"install_succeeded\":true,\"launch_succeeded\":true,\"install_minute…
exited 127 in 0ms:
/bin/sh: 1: ARGUSIC_RESULT:: not found
tokens used
33,013Replay 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
- Installed in 0.5 minutes.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 with mocks | 92.00 | 0.02 |
Topics (from GitHub)
aitestingapiapi-testingapijsonapitestingartificial-intelligenceautotestingdocumentation-toolgrpcheadlesshttphttp-apihttp-clienthttp-requesthttp-tooltest-automationtestingtesting-toolsvuejs2
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/apiauto)Questions
- Does APIAuto run?
- APIAuto runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test APIAuto?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f2042ae79d14. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test APIAuto?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does APIAuto take to install?
- 0.5 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 APIAuto need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing APIAuto?
- 1 thing 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 APIAuto?
- 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.