Browsers run on people, not data centers.
The web stopped trusting data center IPs. SPIDERNET routes your agent's render through a real human's idle Chrome on a real residential connection. $0.001 per page. The page can't tell it isn't a person opening it.
The web stopped trusting data center IPs.
Every site worth scraping for an AI agent now fingerprints headless Chrome and blocks AWS ASN ranges by default. The agent that worked yesterday gets a captcha today, a "verify you're a human" tomorrow, a 403 by Friday. Browserbase and Bright Data sell residential IPs to dodge it. They charge what data centers cost because they run on data centers.
SPIDERNET routes through a real human's home connection. The Chrome session belongs to them. The cookies are theirs. The IP is residential. The page can't tell it isn't a person opening it.
POST a URL. A human opens it.
Paste any URL. The job leaves your browser, hits /v1/render, the router matches a worker by geography, the worker opens Chrome on their laptop and returns HTML or a screenshot. Free 50 renders / day from the public gateway, no signup.
# the same call from your agent curl -X POST https://sp1dern3t.xyz/v1/render \ -H "Authorization: Bearer $SPIDER_KEY" \ -d '{"url":"https://news.ycombinator.com","wait":"load","return":"png"}' # response { "worker": "jp-osaka-#421", "rtt_ms": 890, "cost_usdc": 0.001 }
One contract, two sides, no middleman.
SPIDERNET is the routing layer between AI agents that need a browser and humans that have idle compute. The contract handles payment, slashing, and the 80/20 split.
-
01 / WORKER
Install a 14 MB client.
It boots a headless Chromium when your machine is idle. 2 GB RAM is enough. The client signs jobs with your wallet so the contract knows who to pay.
-
02 / AGENT
POST a job to the gateway.
One endpoint:
/v1/render. Pass a URL, a wait condition, an XPath if you need it. The gateway batches micropayments so you settle in USDC, not gas. -
03 / ROUTE
Match by geography and trust.
The router picks a worker close to the target, with a clean rep, and the right Chrome version. If the worker fails, the job retries on the next best. The user never sees it.
-
04 / SETTLE
80% to the worker. 20% to treasury.
USDC settles per epoch. Treasury sweeps every 24h: 50% buys $SPIDER on the market and burns it, 50% goes to $SPIDER stakers as USDC.
Your laptop already runs eight hours of nothing.
SPIDERNET pays you in USDC to point that nothing at a Chrome window. AI agents around the world need a real browser to render pages, fill forms, scrape data. You give them one. The contract pays you 80%.
# estimated earnings for a typical worker machine 2017 MacBook · 8 GB RAM · 100 Mbps hours / day 12 (10pm – 6am while you sleep) pages rendered 83,200 / month avg job price $0.00126 worker share (80%) $83.84 / month USDC stake boost (10k) +$12 / month # take home total $96 / month, hands-off
$SPIDER. Fair launch. No insiders.
$SPIDER is the routing and revenue token. The contract is open-source and the supply is on-chain. No team allocation, no VC bag, no unlocks waiting to dump on you. 100% in the pump.fun bonding curve.
1,000,000,000 $SPIDER
Single mint. No mint authority. No team wallet. No KOL allocation. The dev's seed buy is whatever the curve costs in the first block, same as you.
20% margin → buyback + yield
The gateway takes 20% of every job. Half buys $SPIDER off the market and burns it, half is paid as USDC to $SPIDER stakers. Network usage = sustained buy pressure + real yield.
# revenue example, conservative scenario gateway throughput = 14,902 pages / min # live average job price = $0.00126 monthly gross = $808,000 worker share (80%) = $646,000 treasury margin (20%)= $162,000 → buy & burn = $81,000 / mo # open-market → staker yield = $81,000 / mo # USDC
Ship the gateway. Then the supply side. Then everything else.
- SHIPPED · Q2 2026
Gateway v0 + browser demo
The site you're on. POST /v1/render returns a real screenshot from a real worker.
- LAUNCH WEEK
$SPIDER fair launch on pump.fun
Full 1B supply hits the bonding curve. CA pinned in the bar above the second it's live.
- Q3 2026
Worker client (macOS + Linux)
Signed installer, opt-in throttling, USDC payout per epoch. Open beta for the first 500 wallets on the waitlist.
- Q4 2026
Agent SDK + paid gateway
Native bindings for Claude Agent SDK, OpenAI Agents, Mastra. Per-token billing in USDC.
- 2027
Stateful sessions + auth
Logged-in workflows. Worker carries a sandboxed profile, agent rents the session by the minute.
The questions you'd ask first.
Why home browsers instead of data centers?
Two reasons. First, cost: a home laptop's headless Chrome session costs the worker close to zero (electricity), where a Browserbase session costs them $0.05+ in AWS time. We pay the worker $0.001 and everyone wins. Second, residential IP: the web increasingly distrusts data center IPs. A home connection in Osaka is the only way to render the Japanese Amazon page the way a person sees it.
How does the gateway not get drowned in abuse?
Workers vote on blocked domains by default (CSAM, malware, sanctioned hosts). Premium routes (logged-in, banking, adult) are opt-in per worker. The contract slashes workers who return mismatched hashes for the same URL at the same time, which catches the "fake-render to earn" attack.
What stops a Browserbase clone from forking this?
Nothing technically, but the moat isn't code, it's the workers. We pay 80% of revenue to the supply side. Whoever owns the supply side at the moment AI agents go mass-market owns this category. We're going to that side first, hard.
Where does the $0.001 per page number come from?
A 2026 worker on a 100 Mbps home line renders ~2,800 pages per CPU-hour. At $0.001 per page that's $2.80/hr to the worker, comfortably above the global remote median for ambient compute. Margins compress as the network scales but the worker share stays at 80% by contract.
Is there a team? Who is shipping this?
One operator, fair-launched, no allocation. The dev's seed buy is whatever they pay on the bonding curve in the first block, posted publicly via the CA bar at the top of this page. The worker SDK is open-source under MIT.
What if I just want to use this and not buy the token?
Do it. The free public gateway gives you 50 renders per day, no signup. The paid API takes USDC, not $SPIDER. The token is for people who want to capture the revenue, not pay for the service.