How we count agent traffic

Trust

Our measurement is the product, so we publish exactly how it works. If a number is ever going to sit on an invoice, both sides should be able to check it from server logs.

The metric

verified agent sessions delivered to merchant properties per week

delivered

An agent (or AI-referred human) session on the MERCHANT'S OWN property. Captured via the click-redirect and the on-site referral beacon. This is the billable / headline number and the Gate-C input.

demand

A hit on B2AC's OWN surfaces (feeds, agent API, MCP). Useful telemetry and a recruitment signal — never billed, never a public per-merchant claim.

Verification ladder

verified: AI-referrer-classified sessions (not UA-spoofable at scale), OR UA-classified crawler hits whose source IP falls within the operator's PUBLISHED IP ranges (OpenAI / Perplexity / Google; refreshed daily). Only 'verified' counts toward Gate C.
claimed: A self-identifying crawler UA whose IP we could not confirm against published ranges — recorded but not billed/claimed.

Session definition

One session = (source, kind, ip_hash, merchant) within a 30-minute window. Repeat hits collapse to one.

Exclusions

B2AC's own bots (synthetic watchdog, crawler) are never counted. Raw IPs are SHA-256 hashed and never stored.