curl_cffi vs httpcloak: SubQ matrix

Run 19 Nov 2026. Model subq-snap-preview, POST https://api.subq.ai/v1/systemone, 98,732 input tokens. State: evidence.md (log's client inventory, a live fingerprint test, both libraries' docs, every Scraping Enthusiasts message on these clients). Both repeats of the choice pass and the claim pass agreed. Raw: matrix/subqResults.json. Rerun: node docs/httpClients/matrix/runMatrix.mjs (needs SUBQ_API_KEY).

Options: hybrid = One identity, curl_cffi plus httpcloak by switch, curl = curl_cffi 0.17 behind one identity, stay = Keep curl_cffi 0.16.3, each client as it is, cloak = httpcloak everywhere, wreq = wreq / rnet everywhere.

Winner: one identity, curl_cffi everywhere, httpcloak by switch later (hybrid, 3.15)

CriterionSubQ's pick (both passes)hybridcurlstaycloakwreq
matchesRealChromecloak3.122.071.203.970.96
oneIdentityhybrid3.503.310.203.132.23
osCoherencecloak3.633.120.693.941.84
websocketcurl3.613.933.940.180.75
asynciocurl3.273.893.960.811.04
migrationEffortstay2.632.943.870.690.44
vendorDiffstay2.913.043.981.220.92
freshnesscloak3.292.981.243.431.26
proxyH2cloak3.012.692.192.760.83
communityBackingcurl2.993.193.113.272.45
maturitycurl2.393.413.370.591.23
cookieMatchcloak2.492.340.942.371.07
newPlatformscurl3.002.650.592.521.36
silentFlagDetectionhybrid3.331.970.431.200.56
reversiblehybrid3.723.241.851.201.18
riskstay3.453.063.811.591.39
mean (0–4)3.152.992.212.061.22
  • httpcloak alone wins the fingerprint criteria: matchesRealChrome, osCoherence, freshness, cookieMatch and proxyH2. Its newest preset matched real Chrome 157 on JA4 and peetprint.
  • It also loses badly where log depends on it: WebSocket (0.18), asyncio (0.81), migration (0.69) and maturity (0.59). Its docs show no WebSocket client and no Python asyncio.
  • curl_cffi 0.17 behind one identity comes a close second (2.99). The hybrid adds httpcloak for plain REST once a bake-off through each platform's own proxy proves it.
  • What was built: the curlUnified part of the hybrid. LOG_HTTP_CLIENT exists but refuses httpcloak until its adapter exists, so nothing silently falls back.

Claims (probability true, both passes)

Claimp
For the same Chrome version, curl_cffi and httpcloak sent identical JA4 and peetprint fingerprints in the live test.0.999
httpcloak's chrome-latest-windows preset matched the real Chrome 157 on this machine on both JA4 and peetprint.0.999
curl_cffi 0.16.3, the version log runs, stops at chrome150 and its Chrome targets carry a macOS user agent.0.999
curl_cffi 0.17.0 adds Windows Chrome targets (chrome151, chrome152) and Windows Firefox 153-155.0.996
httpcloak's documentation shows no WebSocket client API.1.000
httpcloak's documentation shows no asyncio API for Python.0.999
curl_cffi WebSocket handshakes use the same impersonated TLS fingerprint, proxies and cookies as its HTTP requests.1.000
JWriter20, the Camoufox maintainer, recommended httpcloak in Scraping Enthusiasts.0.993
Scraping Enthusiasts members reported that random JA3 fingerprints still get blocked and recommended copying a real browser.0.998
A member reported that a platform ties cookies to the JA3/JA4 fingerprint they were issued to.0.998
log's HTTP clients today present more than three different browser identities.0.999
Both libraries produced the same Akamai HTTP/2 fingerprint as real Chrome in the live test.0.998

Live test

Real Chrome 157 on this machine against curl_cffi and httpcloak at tls.peet.ws. The table is in evidence.md.