Yes. curl_cffi runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 4 errors 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. One attempt is 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.14: 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?

12 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?

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.

Where is the evidence for curl_cffi?

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.

curl_cffi

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

Runssource: GitHub homepagePythonMITcommit 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 12 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

After installing the pre-built curl-cffi wheel (v0.16.3) into a fresh venv, the library imports, the CLI runs (curl-cffi get, doctor, --help), real HTTP requests with browser impersonation return 200, and the unit test suite passes 600+ tests across all 20 test modules including sync/async HTTP, websockets, fingerprints, cookies, headers, cache, upload, and CLI.
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.14 (measured)
recorded runs: 1
last tested: 2026-09-28
stars: 6,610
forks: 556
open issues: 62
watchers: 39
size: 3 MB
created: 2022-03-10
last push: 2026-09-28

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-28. 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.

Several stress/performance tests hang due to resource constraints in container (test_high_parallel, test_high_concurrency, test_huge_payload, test_high_frequency_ping_pong, test_multithreaded_event_loops)10 minutes
Source build failed: missing python3.12-dev headers (pyconfig.h) - cannot install system packages without root5 minutes
Background /tmp/or-proxy.py process occupied ports needed by test fixtures, causing hangs5 minutes
test_sync_websockets.py failed at collection: WebSocket._MAX_CURL_FRAME_SIZE attribute mismatch between installed wheel and source tree3 minutes

Install time: 12 minutes
Cold machine to finish: 38 minutes
Errors hit and fixed: 4 hit, 4 fixed with no human help
How the result was proved: python3 -m curl_cffi get https://httpbin.org/get impersonate=chrome returned HTTP 200; CLI --help displayed correctly; python3 -m curl_cffi doctor reported libcurl 8.21.0-IMPERSONATE working with 38 fingerprints; unit test suite passed ~650+ tests with ~20 skipped across all modules
Model tokens used: 547,591
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.

        }
    ],
    'test_depth': 'tier1_real',
    'verified_how': 'python3 -m curl_cffi get https://httpbin.org/get impersonate=chrome returned H…
    'final_state': 'After installing the pre-built curl-cffi wheel (v0.16.3) into a fresh venv, the…
}
print(json.dumps(result, ensure_ascii=False))
\" 2>&1" in /work/repo
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 12.0, "errors": [{"msg": "…
tokens used
547,591

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 12 minutes.
Recovered from all 4 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 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.

What it is a reasonable choice for

Trying it on a laptop or a small server: it reached a running state without a GPU.

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	100.00	0.14	2026-09-28 22:54 UTC

Topics (from GitHub)

akamai-fingerprint curl curl-impersonate fingerprinting http http-client http2-fingerprint http3-fingerprints https ja3 ja3-fingerprint ja4 ja4-fingerprint quic-fingerprints tls-fingerprint web-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 12 minutes, hitting 4 errors 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. One attempt is 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.14: 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?: 12 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?: 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.
Where is the evidence for curl_cffi?: 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.