Pay-per-Crawl for every stack.
The WordPress plugin, ported to Python, JavaScript, Go and PHP. Drop one in front of your site and AI crawlers pay per page in USDC on Base, straight to your wallet. You keep 100%. No custody, no account, no API key.
Pick your edition
WordPress
v0.2.2Any WordPress 6.x site
Plugins → Add New → Upload Plugin
wordpress.org directory listing is in review.
Python
v0.1.2FastAPI, Flask, Django
pip install forgemesh-pay-per-crawl
JavaScript
v0.1.1Cloudflare Workers, Next.js, Node (Express, Fastify, Hono, Koa), nginx njs
npm i @forgemeshlabs/pay-per-crawl-node
Go
v0.1.1net/http middleware, Caddy module, Traefik plugin
go get github.com/forgemeshlabs/pay-per-crawl-go
Caddy: xcaddy build with the module; Traefik: plugins catalog, topic traefik-plugin.
PHP
v0.1.0Plain PHP, Laravel 10+, Drupal 10/11
composer require forgemesh/pay-per-crawl-core
What every edition shares
- Same behaviour everywhere
- One crawler catalog, one 402 shape, the same classifier. Humans and reverse-DNS-verified search engines read free; AI crawlers and bots pay per page.
- You keep 100%
- Each edition calls the facilitator itself: verify, then settle, then serve only on a transaction hash. Nothing routes through ForgeMesh.
- x402 v1 + v2 and MPP
- Every 402 carries a PAYMENT-REQUIRED v2 header, a v1 JSON body and a WWW-Authenticate: Payment challenge, so more agent clients can pay.
- Discovery files
- Each edition serves /.well-known/x402.json, llms.txt and agents.txt so agents can find your terms.
- Proven with real money
- Every edition was verified with two live $0.01 settlements on Base mainnet, one per protocol version, before release.
- Optional Pro reporter
- Point any edition at Pro for a hosted dashboard, Monday digest and paywall monitoring. Pro sees per-bot counts and settlements only.
Security notes
Two hardening fixes shipped across all editions on 17 October 2026 and are in every version listed above: trusted X-Forwarded-For now uses the right-most hop, so a client cannot prepend a search-engine IP to read free, and path exemptions are anchored to exact files or slash-delimited prefixes, so a crafted path cannot match an allow rule. Report issues to [email protected].