Skip to main content
The Xenarch Joomla package detects AI bots, returns HTTP 402 with x402 payment terms, and serves the page once the bot has paid. It behaves the same as the WordPress plugin. Pricing, gating, per-bot overrides and the receiving wallet are stored on the Xenarch platform and edited in the dashboard or the component’s admin screen.

Requirements

  • Joomla 5.0 or later
  • PHP 8.1 or later
  • A wallet on Base to sign in to dash.xenarch.dev with

Installation

No packaged release is published yet. Build pkg_xenarch.zip from the xenarch-plugins repository:
Then, in Joomla admin:
  1. Go to System > Install > Extensions.
  2. Upload pkg_xenarch.zip.

What gets installed

The package contains two extensions: The package creates no database tables. It stores the site token, the site id and a browser-proof secret in the component’s parameters.

Setup

  1. Go to Components > Xenarch.
  2. Click the connect button. You are sent to dash.xenarch.dev.
  3. Sign in with your wallet, confirm the domain, and you return to Joomla with the site paired.
  4. Review gating, pricing and the receiving wallet in the admin screen or the dashboard.

Settings

Two settings are kept locally as fallbacks for when the Xenarch API cannot be reached:

Bot categories

New sites start with AI Search allowed and AI Assistants, AI Agents, AI Training, Scrapers and General AI gated. Change categories and per-bot overrides (allow or charge) in the dashboard.

Receiving wallet

Payments go to your account’s receiving wallet, which starts as the wallet you signed in with. A wallet you link later becomes eligible after a 24-hour cooldown. The plugin has no field for typing in another address.

How it works

Request flow

  1. Skip: logged-in users, /.well-known/* paths and static assets always pass.
  2. Check proof of payment: if the request carries X-Xenarch-Gate-Id and X-Xenarch-Tx-Hash, the plugin verifies them with the platform and serves the page on success. A standard x402 X-PAYMENT header is settled through the platform and served on success.
  3. Free paths and gating switch: free paths and a disabled gate are served.
  4. Detect: match the User-Agent against known AI bot signatures, then score the request headers.
  5. Apply policy: per-bot override first, then the category default.
  6. Respond: allow (the page), challenge (HTTP 403 with a browser check), or gate (HTTP 402 with the payment terms).

Discovery documents

The plugin serves:
  • /.well-known/pay.json: machine-readable pricing (pay.json v1.2)
  • /.well-known/xenarch.md: payment instructions in Markdown

Bot detection

Detection runs in this order:
  1. Empty User-Agent: blocked
  2. Signature match: known AI bot User-Agent strings (social preview bots pass free)
  3. Trusted search crawlers: Googlebot, Bingbot and others, always allowed
  4. HTTP client signatures: python-requests, curl, wget, Go-http-client
  5. Browser proof: a valid proof cookie from a previous challenge
  6. Header scoring: missing Accept, Accept-Language or Sec-Fetch-* headers raise the score
  7. Unknown non-browser traffic: gated unless Gate Unknown Traffic is off

Local development

This starts Joomla 5 and MySQL 8 with the source mounted for live editing.

Admin UI development

The admin dashboard is a React and TypeScript app:
npm run build writes to admin-ui/dist/. When admin-ui/node_modules exists, scripts/build-release.sh rebuilds the UI and copies xenarch-admin.js and xenarch-admin.css into src/media/com_xenarch/js/ and src/media/com_xenarch/css/.