XeroWP
ForgeMesh Pay-per-Crawl
ForgeMesh Pay-per-Crawl

ForgeMesh Pay-per-Crawl

0/5 (0 ratings) — active installs Updated Oct 29, 2026
AI Crawlersanalyticsbotspaywallx402
Download v0.2.5 Plugin Website
Bot analytics: hits per day, who is crawling, paid fetches and revenue.

Bot analytics: hits per day, who is crawling, paid fetches and revenue.

Pay-per-Crawl shows you every AI crawler, SEO crawler and script that fetches your pages, verifies the real search engines by reverse DNS so SEO is untouched, and lets you answer everything else with a standard HTTP 402 price in USDC on Base, paid to your own wallet. Be clear about what pays today: x402-capable agents do; the big AI labs’ crawlers (GPTBot, ClaudeBot, PerplexityBot and friends) do not yet pay anyone per page, and they simply get no content from a charging site. Until they do, this is an honest bot ledger with the price already on the door. You see who takes what, you can block or charge any of it, and when a crawler does pay, it goes straight to you. Nobody in between holds the money. Humans and verified search engines read free.

  • 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. An x402-capable client pays USDC on Base and retries; a crawler that cannot pay gets no content; 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.
  • Hosted account (optional, free). A hosted dashboard for up to 5 sites, a crawler-intelligence feed that keeps the bot list current, and a listing in the paid-sites directory. Everything above works without it.
  • Pro (optional, $4.99/month on the same key). Pricing rules by bot and content group, a revenue report with a settlements CSV, daily paywall monitoring with alerts, and a Monday digest.
  • Bot directory. Every crawler the plugin knows, explained for humans: who runs it, what it does with your pages, how it is verified, its robots.txt line, and what your site currently does with it. Searchable, grouped by purpose, and it grows as new bots appear on your site.
  • Discovery built in. The plugin serves /.well-known/x402.json, /llms.txt and /agents.txt and adds lines to robots.txt, so paying agents and x402 indexes find your paid pages.

How a payment works

This is what happens when an x402-capable client fetches a page.

  1. A bot requests a page and gets 402 Payment Required with the price, asset (USDC on Base) and your wallet.
  2. The bot signs a USDC transfer authorization and retries with it in a header.
  3. The plugin sends that authorization to an x402 facilitator, which checks it and submits it on-chain. The facilitator never holds funds.
  4. The plugin serves the page only when the facilitator returns a transaction hash, and records the hit, the payer and the hash.

Third-party services

The plugin makes outbound requests only when a payment is presented, and only to the x402 facilitator configured in Settings:

  • 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 Pro key or the Crawler Atlas opt-in (off by default), the plugin never contacts ForgeMesh.

Search-engine verification uses ordinary DNS lookups.

Privacy

Visitor IP addresses are never stored. Bot sources are counted by a daily-salted hash. Human page views are stored only as a count (class “human”, no user agent) when that option is on. Rows are deleted after the retention period you set.