How biptest.com is built

Everything on biptest.com is one of three things

1. The handler and its config (these are the plugin)

Two files at the site root. A customer downloads them, drops them next to their index, adds one rewrite line to .htaccess or nginx, and the site speaks HTTP 402 to AI agents from that moment on.

• /ai-certified-handler.php — the General HTML/PHP handler. Open-source. Downloadable at bippsi.com/ai-key. Version 2.3.5 at the time of this page.
• /ai-certified-config.json — generated by the A.I. Lock UI on bippsi.com from the site owner’s pricing. Site keys, paywall routes, prices. Auto-syncs via wp-cron on WordPress sites and lazy-polls on everything else.

2. Normal site content (this is the site)

Regular PHP and HTML. Zero Bippsi-specific code, zero function calls to anything named biptestPaywall or bippsiCharge or anything similar. When the handler decides a request is paid or free, it just include()s these files to render the response.

• /index.php, /pricing.php, /about.php, /contact.php, /buy.php, /premium-report.php
• /articles/whitepaper.php
• /health/*.php, /tech/*.php, /news/*.php — 9 articles using a shared _article.php + _category.php template
• /downloads/whitepaper.php — serves a PDF blob
• Static: /llms.txt, /AGENTS.md, /agents.json, /robots.txt, /sitemap.xml, /bippsi-unified.md, /favicon.svg

No priced page has a require paywall.php line. No priced page calls a gating function. The article files are pure rendering. Delete the handler and you get the full site back, free. Swap the handler for a different plugin and the content is untouched.

3. Demo-only additions (the terminal)

The dark strip at the bottom of every page is a transparency aid, not part of the paywall stack. A customer installing the handler on their own site would not have this. It’s two files we add specifically for the public showcase:

• /_terminal.php — the strip markup, included by _layout.php
• /terminal-events.php — a tiny Server-Sent Events endpoint that echoes recent hits so visitors can watch real traffic

What a customer sees end-to-end

1. Sign up at bippsi.com, verify their business via Authenticate.com, get an A.I. Lock slot.
2. Download ai-certified-handler.php and drop it at their site root.
3. Add the rewrite line to .htaccess or nginx (one line).
4. Download the auto-generated ai-certified-config.json that Bippsi mints from their Lock UI settings, drop it next to the handler.
5. Done. Their site now returns HTTP 402 to AI agents, takes payments in Bips, writes earnings to their partner account every time a bot hits a priced URL. Humans still see everything free.

Wait, how do humans see pages but agents get 402?

The handler detects agents by three signals: a Bippsi Bearer header, a known AI crawler User-Agent (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and a dozen others), or a machine-only Accept: application/json. Any one triggers the 402/charge flow. Zero signals — what a browser sends — passes through to the content. Default-on behavior, no per-route config.

Site owners who explicitly want to gate humans too (almost nobody) can flip paywall.gate_humans = true in their config. Most don’t.

No backend special cases

Every Bip charged on biptest.com writes a real bips_spend row on the Bippsi side — same table, same 20% house / 80% creator split, same accrual-to-partner mechanics as any customer site. We don’t have a “demo mode.” We have a demo user (payout-ineligible by the is_system_account flag) and a shared 25,000-Bip daily pool that’s not real money, but the rest of the stack is production.

Want to install this on your own site? Start at bippsi.com/ai-key.