http-request-action
Create HTTP Requests in GitHub Actions
Runs with mockssource: GitHubJavaScriptMITcommit f98bb26551cd
JavaScript, MIT licensed. The project labels itself: api client, http client, request and rest client.
http-request-action runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Dependencies installed, both CLI (bin/http-action) and GitHub Action bundle (dist/index.js) work correctly; npm run build succeeds with @vercel/[email protected]; HTTP GET, POST, file upload, bearer auth, URL-encoded form, custom headers, and custom content-type all function via the CLI against a real HTTP server.
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.
- yargs@18 (ESM-only) not compatible with Node 18 require(). CLI failed to load.2 minutes
- CLI script called request() without await, so process exited before HTTP request completed.2 minutes
- npm run build failed: @vercel/[email protected] throws 'N.hash is not a function' on Node 18.2 minutes
- Node.js v18 in container (package.json requires >=24). npm install succeeded with EBADENGINE warnings.1 minute
- Install time
- 15 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- Started a local HTTP server (127.0.0.1:1987x), then used node bin/http-action to send GET, POST (JSON, URL-encoded, file upload), bearer auth, custom headers, custom content-type, and timeout requests. Every request returned HTTP 200 with correct body/headers. npm run build completed, producing 1.5MB dist/index.js. Node version 18 remains below the >=24 requirement but all functionality works.
- Model tokens used
- 191,300
- Exact commit tested
- f98bb26551cd
- 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.
/bin/sh -lc 'cd /work/repo && npm ls @vercel/ncc 2>&1 | head -3' in /work/repo succeeded in 159ms: [email protected] /work/repo └── @vercel/[email protected] Here's the full report on what I did and found. Let me calculate total elapsed time exec /bin/sh -lc 'echo "Start estimate: 15 minutes of work"' in /work/repo succeeded in 0ms: Start estimate: 15 minutes of work tokens used 191,300
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.
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 15 minutes to install, slower than the median of the 39 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 40 api-client projects Argusic has installed and timed, http-request-action was the 33rd fastest to reach a running state, and 25 of 40 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 | 1/3 | Runs with mocks | 92.00 | 0.02 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/http-request-action)Questions
- Does http-request-action run?
- http-request-action runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test http-request-action?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f98bb26551cd. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test http-request-action?
- 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 http-request-action take to install?
- 15 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 http-request-action need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing http-request-action?
- 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 http-request-action compare with the alternatives?
- Of the 40 api-client projects Argusic has installed and timed, http-request-action was the 33rd fastest to reach a running state, and 25 of 40 reached one at all.
- Where is the evidence for http-request-action?
- 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.