wreq-python
An ergonomic, privacy-aware Python HTTP Client
Runssource: GitHubhomepagePythonApache-2.0commit 24be2b620854
Python, Apache-2.0 licensed. The project labels itself: akamai, akamai fingerprint, censorship resistant, crawler, fingerprint, http, http client and http2.
wreq-python runs. An Argusic agent installed it in 9.5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
wreq Python package builds, installs, and passes all 57 unit tests against a local httpbin server, supporting HTTP/1.1 and HTTP/2 requests, cookie jars, redirect policies, TLS emulation (JA3/JA4), multipart uploads, streaming, and compression.
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.
- bindgen-0.72.1 could not find libclang (libclang.so)7 minutes
- Tests fail with ConnectionError to localhost:8080 (no httpbin service)2 minutes
- Rust toolchain (rustc/cargo) not found in container0.5 minutes
- Install time
- 10 minutes
- Cold machine to finish
- 15 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pytest tests/ -v exited 0 with 57 passed against httpbin on localhost:8080; plus end-to-end smoke test of GET, POST JSON, cookie jar, and redirect against local httpbin
- Model tokens used
- 73,403
- Exact commit tested
- 24be2b620854
- 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.
[2026-10-07 19:32:54 +0000] [9296] [INFO] Booting worker with pid: 9296
[2026-10-07 19:32:54 +0000] [9294] [INFO] Control socket listening at /home/runner/.gunicorn/gunico…
[2026-10-07 19:32:54,256] WARNING in core: flasgger is not installed; serving the static landing pa…
GET /get - success: True - url: http://localhost:8082/get
POST json - echoed json: {'hello': 'world'}
Cookie jar test - success: True
Redirect - is_redirection: True
All smoke tests passed!
All working end-to-end. Here's the summary:
tokens used
73,403
All working end-to-end. Here's the summary: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 9.5 minutes.
- Recovered from all 3 errors 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 Apache-2.0, 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.
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 9.5 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)
akamaiakamai-fingerprintcensorship-resistantcrawlerfingerprinthttphttp-clienthttp2httpsja3ja4pythonrustscrapertlstls-clienttls-fingerprintweb-scrapingwebsocketwebsocket-client
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/wreq-python)Questions
- Does wreq-python run?
- Yes. wreq-python runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test wreq-python?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 24be2b620854. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test wreq-python?
- The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does wreq-python take to install?
- 9.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 wreq-python need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing wreq-python?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for wreq-python?
- 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.