Claude Code plugin · No API key

403 is not
an answer.

When WebFetch hits a 403, a WAF or a CAPTCHA on a public page, insane-search switches routes (public APIs and feeds, then browser TLS fingerprints, then a real Chrome) until the content comes back. No API key needed. At logins and paywalls it stops and tells you so.

/plugin marketplace add https://github.com/fivetaku/gptaku_plugins.git
/plugin install insane-search@gptaku-plugins
Many violet routes stop at a wall with a 403 door; one coral route slips over the top

Same URL, different outcome

Coupang search for "keyboard", first run on September 28, 2026.

Built-in WebFetch
403
Request refused, no content
insane-search
60 products
Succeeded on route 52 (real Chrome) · 41s

All 52 attempts, replayed

A replay of the actual execution trace.

Four sites, run again the same day

This is the second run. The route that works changes from run to run, so Coupang here differs from the video above (route 52, 41s). The raw logs are on GitHub.

Coupang searchWebFetch 403 → attempt 18, mobile URL + Chrome TLS fingerprint13.9s
Reddit top postsAttempt 1, Reddit's official RSS1.3s
Naver BlogEmpty frameset → attempt 2, mobile URL (m.)0.9s
X profile429 twice → attempt 3, Safari TLS fingerprint2.5s

Blocked? Next route.

01

Official routes first

RSS feeds and public APIs the site already exposes.

02

Look like a browser

Real browser TLS fingerprints, cookies and mobile URLs, in combination.

03

Use a real browser

If all else fails, it opens Chrome on your machine and reads the rendered page.

To be fair

If you need to crawl thousands of pages on a schedule, a hosted crawler is the better fit. insane-search won't break into login-only pages or paywalls; it tells you it couldn't read them. It's built for the one public page that stopped your conversation.

The moment you're blocked,
it steps in.

/plugin marketplace add https://github.com/fivetaku/gptaku_plugins.git
/plugin install insane-search@gptaku-plugins