ForgeMesh Pay-per-Crawl
| 开发者 | forgemeshlabs |
|---|---|
| 更新时间 | 2026年10月20日 21:02 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Most of a website's traffic is not human. Search indexers, AI crawlers, LLM "readers", scrapers and autonomous agents fetch pages all day and pay nothing. This plugin gives that traffic a price.
- Humans see nothing different. Browsers get the page as always.
- Verified search engines stay free. Googlebot, Bingbot, DuckDuckBot, Applebot and friends are checked by reverse DNS so your SEO is untouched. A crawler that only claims to be Googlebot is treated as a script.
- AI crawlers, SEO crawlers and scripts get HTTP 402 Payment Required. The response carries the x402 challenge (v2 header and v1 body, so every current client can pay) and an MPP challenge. The client pays USDC on Base and retries; the page is served only after the payment is settled on-chain.
- You keep 100%. The payer's USDC goes directly to the wallet you enter. Nothing is held by the plugin, by ForgeMesh, or by anyone else.
- Bot analytics in wp-admin. Who is crawling (by name and class), how often, from how many sources, which paths, what was paid, every settlement with its transaction link. Start in Monitor mode and see what the bots would have paid before you charge anything.
- Pro (optional, $4.99/month). A hosted dashboard for up to 5 sites, a Monday digest, daily paywall monitoring with alerts, a crawler-intelligence feed that keeps the bot list current, and a listing in the paid-sites directory. Everything above works without it.
- Discovery built in. The plugin serves
/.well-known/x402.json,/llms.txtand/agents.txtand adds lines torobots.txt, so paying agents and x402 indexes find your paid pages.
- A bot requests a page and gets
402 Payment Requiredwith the price, asset (USDC on Base) and your wallet. - The bot signs a USDC transfer authorization and retries with it in a header.
- The plugin sends that authorization to an x402 facilitator, which checks it and submits it on-chain. The facilitator never holds funds.
- The plugin serves the page only when the facilitator returns a transaction hash, and records the hit, the payer and the hash.
- PayAI facilitator (default):
https://facilitator.payai.network— terms · privacy. It receives the payer's signed authorization and the payment terms (your wallet address, amount, the page URL). No visitor data, no site content. - Or any facilitator URL you enter, including one you run yourself.
- ForgeMesh Pay-per-Crawl Pro (only after you enter a Pro license key):
https://proxy.forgemesh.io— terms · privacy. The plugin sends your license key, the site's host, name, mode, price and payout wallet, daily per-bot counts (bot name, class, hits, paid, revenue, number of distinct hashed sources) and settlement records (transaction hash, payer wallet, path, amount). No visitor IPs, no page content, no human user agents. It pulls a crawler list from the same service once a day. Without a key the plugin never contacts ForgeMesh.
安装:
- Upload the plugin and activate it.
- Go to Pay-per-Crawl → Settings, paste your payout wallet (a 0x address on Base, for example from Coinbase Wallet or MetaMask), choose a price, save.
- Watch Pay-per-Crawl → Bot analytics for a day or two in Monitor mode.
- Switch the mode to Charge.
屏幕截图:
常见问题:
Will this hurt my Google ranking?
No. Verified search engines are free by default and are checked by reverse DNS, the same method Google documents for verifying Googlebot. Social link previews and uptime monitors are also free by default.
What do bots pay with?
USDC on the Base network, using the x402 protocol (HTTP 402) or MPP. Payers sign a transfer authorization; a facilitator submits it on-chain. You receive USDC in your own wallet within seconds.
Do I need a Coinbase account or an API key?
No. The default facilitator needs no account. You only need a wallet address.
Can a bot read the page without paying?
Not through WordPress: the 402 is answered before any template runs, and the page body is empty. Pages cached by a CDN or a full-page cache plugin may be served to bots from the cache; exclude bot user agents from that cache or put the cache behind the plugin.
Does it work with caching plugins?
The 402 is sent with Cache-Control: no-store, and paid responses are marked private. Full-page caches that serve HTML before WordPress loads will bypass the gate for cached pages.
What if the facilitator is down?
Payers get a 402 with the reason, can retry, and are never charged. Humans are never affected.
更新日志:
0.2.2
- Security: exempt-path matching is anchored. Look-alike paths (/robots.txt.x, /sitemapfoo, /.well-known/../post, an allow path /pricing matching /pricing-secret) no longer bypass the paywall; dot segments and %2e / %2f paths are gated.
- Security: with a multi-value client-IP header (X-Forwarded-For), use the right-most address so a crawler cannot prepend a search-engine IP and bypass the paywall.
- Pro: license key, hourly sync to the hosted dashboard, crawler-intel feed merged into the classifier, directory opt-in.
- CSV export neutralises formula-leading cells.
- First release: classifier with 80+ known agents, x402 v1 and v2 plus MPP challenges, facilitator verify/settle, discovery files, bot analytics, CSV export.