curl_cffi

Python binding for curl-impersonate fork via cffi. A http client that can impersonate browser tls/ja3/http2 fingerprints.

Runssource: GitHubhomepagePythonMITcommit ba87df75970b

Python, MIT licensed. The project labels itself: akamai fingerprint, curl, curl impersonate, fingerprinting, http, http client, http2 fingerprint and http3 fingerprints.

curl_cffi runs. An Argusic agent installed it in 1.2 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

curl_cffi 0.17.0 installed via pre-built wheel, imports work, real HTTP requests succeed with and without impersonation, CLI doctor reports 47 native fingerprints, 711/730 unit tests pass (19 pre-existing skips)

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.13 (measured)
recorded runs
2
last tested
stars
6,878
forks
579
open issues
55
watchers
40
size
3 MB
created
last push

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.

Time lost to each failure while testing curl_cffi, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Cannot build from source: pyconfig.h missing (python3-dev not installed, no root)1.5 minutes
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
pip install succeeded; curl_cffi.get('https://httpbin.org/get') returned 200; unit tests: 711 passed, 19 skipped, 0 failed
Model tokens used
68,891
Exact commit tested
ba87df75970b
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-11-06T04:51:59.077763Z ERROR codex_core::session: failed to record rollout items: thread 01a1a…
2026-11-06T04:51:59.077891Z ERROR codex_core::session: failed to record rollout items: thread 01a1a…
tokens used
68,891
All unit tests pass cleanly. Let me compile the results:
**Installed:** Pre-built wheel (0.17.0) pip-installed via `uv pip install curl-cffi`. The local sou…
**Verified:**
- Import and curl version string: `libcurl/8.23.0-IMPERSONATE BoringSSL ... curl-impersonate/local`
- Real HTTP requests via `curl_cffi.get()`, `requests.Session()`, and impersonation to httpbin.org …
- CLI (`curl-cffi --help` and `curl-cffi get`) works
- `curl-cffi doctor` reports correct diagnostics
**Tests:** 711 passed, 19 skipped (all pre-existing skips: unreachable external websites, Windows-o…

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.2 minutes.
  • 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.
  • Measured 2 times, so the result is not a one-off.

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.2 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.13
Argusic Runner1/3Runs100.000.14

Topics (from GitHub)

akamai-fingerprintcurlcurl-impersonatefingerprintinghttphttp-clienthttp2-fingerprinthttp3-fingerprintshttpsja3ja3-fingerprintja4ja4-fingerprintquic-fingerprintstls-fingerprintweb-scraping

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/curl_cffi.svg)](https://argusic.com/subject/curl-cffi)

Questions

Does curl_cffi run?
Yes. curl_cffi 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 curl_cffi?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit ba87df75970b. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test curl_cffi?
The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does curl_cffi take to install?
1.2 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 curl_cffi need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing curl_cffi?
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 curl_cffi?
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.

Discussion