ain
A HTTP API client for the terminal
Runs with mockssource: GitHubGoMITcommit 654623759ec3
Go, MIT licensed. The project labels itself: api, api client, api rest, curl, go, http, httpie and insomnia.
ain runs, with stand-ins for the services it depends on. An Argusic agent installed it in 17 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The ain binary builds and runs, version 1.6.0 prints, 22 e2e tests and all unit tests pass against a local mock HTTP server with curl, httpie, and wget backends all working.
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 86 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.
- e2e test host mock.httpstatus.io did not resolve (no DNS)3 minutes
- go command not found2 minutes
- wget binary not found in container1 minute
- httpie binary not found in container1 minute
- Install time
- 17 minutes
- Cold machine to finish
- 19 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- go test ./... exited 0 (all 22 e2e subtests PASS, 4 unit test suites PASS). Also ./ain -v returned 'Ain 1.6.0 (develop) linux/amd64' and ./ain /tmp/test.ain returned '200 OK'
- Model tokens used
- 135,391
- Exact commit tested
- 654623759ec3
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
=== Mock server running === 200 OK Now I have all the data. Let me calculate the elapsed time more precisely and produce the final res… exec /bin/sh -lc '# The first command ran at approximately 16:31:50 UTC # Current time from last command: 16:48:47 # Total: ~17 minutes' in /work/repo succeeded in 0ms: Here's the final report: tokens used 135,391 Here's the 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
- Recovered from all 4 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
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 17 minutes to install, slower than the median of the 61 comparable projects Argusic has measured.
Of the 62 api projects Argusic has installed and timed, ain was the 55th fastest to reach a running state, and 39 of 62 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 | Runs with mocks | 92.00 | 0.04 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.03 |
Topics (from GitHub)
apiapi-clientapi-restcurlgohttphttpieinsomniapawpostmanterminal
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ain)Questions
- Does ain run?
- ain runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 17 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test ain?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 654623759ec3. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test ain?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ain take to install?
- 17 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 ain need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ain?
- 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 ain compare with the alternatives?
- Of the 62 api projects Argusic has installed and timed, ain was the 55th fastest to reach a running state, and 39 of 62 reached one at all.
- Where is the evidence for ain?
- 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.