Wick – censorship circumvention tech repurposed for AI web access

Name: Wick – censorship circumvention tech repurposed for AI web access
Availability: InStock
Author: adamfisk

by adamfisk·Apr 2, 2026·4 points·2 comments

Visit Project View on HN

AI Analysis

●●●BangerBig BrainZero to OneSolve My Problem

Censorship circumvention tech stops AI agents getting blocked by bot detection systems.

Strengths

•Author's Lantern pedigree suggests proven expertise in traffic indistinguishability and evasion techniques.
•Targets TLS fingerprinting and handshake details instead of just rotating residential proxies.
•Solves the pain point of AI agents failing to crawl protected sites.

Weaknesses

•Crowded scraping market means players like BrightData have deeper enterprise integration already.
•Unclear if this runs client-side or requires relay infrastructure like Lantern did.

Post Description

I helped build Lantern, a censorship circumvention tool that’s been downloaded over 150 million times globally, with most users in China, Russia, Iran, and the UAE. Before Lantern I was the lead engineer at LimeWire (back in those days our whole dev team was about 5 people!).

Making your traffic indistinguishable from normal internet traffic has long been a foundational part of effective censorship circumvention, a technique sometimes referred to as “collateral freedom.” If censors can’t differentiate your traffic from other traffic they don’t want to block, then they can’t block you without incurring collateral – and economic – damage.

It turns out this is fundamentally the same challenge AI agents face when trying to crawl webpages. The tools they use are identifiable by various means, whether it’s unique TLS handshakes from Python, Go, Node, etc, or whether it’s details in the page processing that make it clear the requester is not a real browser and/or human.

To get around this, Wick uses Cronet (Chrome's network stack as a standalone lib) as the default for all requests. It’s not a headless browser – just the network layer. Wick works as an MCP server so Claude Code and Cursor pick it up automatically and also supports local API access. I also just got it on Apify's store if you want to try it without installing anything — it works from their datacenter IPs, which surprised me honestly. Importantly, it’s local by default. That way, if you’re running from your house, it can automatically take advantage of your residential IP address, which is less likely to get flagged.

The Cronet version is lightning fast and effective, but it doesn’t do JS rendering. If you need that (a requirement for accessing some sites), we have Wick Pro that does some fancy things on that side too that are very different from other tools out there.

Open source, MIT. Pro for $20/mo if you need JS rendering.

Code: https://github.com/wickproject/wick

Site: https://getwick.dev