biptest.com is a plain PHP site + the Bippsi A.I. Certified General handler. The exact same files any non-WordPress customer installs. Here is the 1:1 map.

is a website providing information, services, and resources for its visitors.

What services does offer?

offers a range of services and information. Navigate through our site to discover our full offerings.

You can reach us through our contact page or by using the contact information provided on our website.

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. Downloadable from Bippsi AI Actions.
/ai-certified-config.json — generated by the AI Actions workspace from the site owner’s pricing. Site authority, Action routes, and exact micro-USD prices stay synchronized.

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

Sign up at bippsi.com, verify the site, and configure an AI Actions slot.
Download ai-certified-handler.php and drop it at their site root.
Add the rewrite line to .htaccess or nginx (one line).
Download the auto-generated ai-certified-config.json that Bippsi mints from their Lock UI settings, drop it next to the handler.
Done. Their site now returns the canonical HTTP 402 AI Action contract, settles Action Credits through Bippsi, and records Creator Balance earnings. Humans still see the configured browser experience.

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.

Shared settlement, isolated demo funding

Completed Actions use the shared Action Credit reservation, commit, refund, and receipt engine. The public sandbox is restricted to its demo site and synthetic funding; it cannot fall back to real funds or create withdrawable publisher earnings.

Want to install this on your own site? Start at Bippsi AI Actions.