gracy
Gracy helps you handle failures, logging, retries, throttling, and tracking for all your HTTP interactions.
Runssource: GitHubPythonMITcommit 44df30beb317
Python, MIT licensed. The project labels itself: http client, python and python3.
gracy runs. An Argusic agent installed it in 1 minute and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
gracy 2.0.0a0 builds from source with its compiled Rust core, passes 621 tests (1 intentional skip) on both rust and python engines, and its quickstart and CLI agent mode return live HTTP 200 data from PokeAPI.
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
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.
- System Python blocked by PEP 668 externally-managed environment1 minute
- Install time
- 1 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- .venv/bin/python -m pytest -q returned '621 passed, 1 skipped'; README quickstart ran and printed mew: name='mew' order=248 and agumon: None; gracy x 'GET /pokemon/pikachu' returned status 200; gracy --version returned 'gracy 2.0.0a0'
- Model tokens used
- 189,824
- Exact commit tested
- 44df30beb317
- 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.
**Tests (tier1 real):** `pytest` → `621 passed, 1 skipped` on both the default rust engine and `GRA… **Real behavior:** README quickstart against live PokeAPI returned `name='mew' order=248` and `None… GRACY_ENGINE = python fallback verified too. No third-party keys required (PokeAPI is public). tokens used 189,824 I have everything I need for the report. **Summary of findings:** **Install:** `pip install -e .` in a fresh venv built the Rust core via maturin and succeeded. `gra… **Errors:** One — the system Python is PEP 668 externally-managed, so `pip install` was blocked; fi… **Tests (tier1 real):** `pytest` → `621 passed, 1 skipped` on both the default rust engine and `GRA… **Real behavior:** README quickstart against live PokeAPI returned `name='mew' order=248` and `None… GRACY_ENGINE = python fallback verified too. No third-party keys required (PokeAPI is public).
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.
- Installed in 1 minute, faster than the median of the 4 comparable projects Argusic has measured.
- Recovered from all 1 error 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 MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 5 http-client projects Argusic has installed and timed, gracy was the 1st fastest to reach a running state, and 4 of 5 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.
- A quick evaluation: it was running 1 minutes after the clone.
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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/gracy)Questions
- Does gracy run?
- Yes. gracy runs. 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 gracy?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 44df30beb317. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test gracy?
- 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 gracy take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does gracy need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing gracy?
- 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.
- How does gracy compare with the alternatives?
- Of the 5 http-client projects Argusic has installed and timed, gracy was the 1st fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for gracy?
- 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.