Volance, in a form
machines can cite.

What Volance is

Volance is an explainable bot and agent detection product by Oops Games LLC. One reviewed script on your pages and one API call from your server return a 0–100 human-likeness score, a human, agent, or bot label, and the signals behind the verdict. Your server decides whether to allow, flag, or block. Verified AI agents can pay for access through HTTP 402 and x402, and Volance takes no cut of agent payments.

Key facts

• Classification labels: human, agent, bot — distinct from the policy-facing verdict.
• Score: a human-likeness estimate on a 0–100 scale. An estimate, not a probability or proof of identity.
• Verdict bands: human at 80 or above, likely human 70–79, suspicious agent 40–69, bot below 40.
• Suggested action: allow, flag, or block — recommended by Volance, enforced by your server.
• Scopes: a whole site, selected pages, or a single server-side API endpoint.
• Authentication: a public pk_ key requests a session manifest; a secret sk_ key stays server-side as a Bearer token.
• Privacy: on-site signals only, no cross-site identifiers, hashed IP addresses, 30-day raw retention, opt-in collection, and no raw keystrokes or typed content.
• Framing: behavioral detection, not a CAPTCHA; a score does not prove a human was present.

Documentation

• Integration overview — Plan a Volance integration: on-site signals, server-side scoring, and application policy. How the Volance API, collector, and portal fit together.
• API reference — The Volance scoring endpoint, response fields, verdict thresholds, and error shapes, with the authentication boundary for server-side integration.
• Portal guide — How to use the Volance portal: projects, keys, the test area, live traffic, sessions and evidence, plans and usage, team roles, audits, and the collector.
• Agent monetization (402 paygate) — How Volance monetization works: classify the caller, verify Web Bot Auth trust, set a price, and return an x402 challenge your own edge enforces.

Atlas

• Atlas — the state of agent activity — A live, sourced view of the agent web: how much traffic is automated, what the bots are, who runs them, and the x402 agent-payments economy.
• Atlas report | State of agent traffic — A dated, citable report on the agent web: the human/agent/bot split, top AI agents and bots, and the x402 economy, by month.
• State of agent traffic — October 2026 — The frozen October 2026 report: automated traffic, AI crawlers, top bots, and the x402 agent-payments economy.
• Atlas method — sources and limits — How the Volance Atlas is built: the public sources it cites, their licenses, and the limits of the data.
• Atlas — x402 facilitators — Share of settled x402 volume by facilitator, from x402stats.
• Atlas widget — embed agent-activity data — Embed a small, live view of bot activity and the agent economy on your own site.
• Atlas — AI agents — Top AI agents by HTTP request share, from Cloudflare Radar.
• Atlas — the x402 catalog — The x402-payable services listed in Coinbase's CDP Bazaar: how many, what they cost per call, where they settle, and the most-used.

Product

• How it works — collection, scoring, and the decision that stays on your server.
• Agent monetization — classify the caller, verify Web Bot Auth, set a price, and return an x402 challenge your edge enforces. Volance never holds funds.
• Pricing — Free, Pro, and Business plans; Volance takes no percentage of agent payments.
• About Volance — what it is, who makes it, and where to find us.

Trust

• Privacy — what the website and service collect, what is never collected, retention, and controls.
• Terms — terms for the website and service.

Comparisons

• Compare Volance | Explainable bot and agent detection — How Volance compares with Google reCAPTCHA, Cloudflare Turnstile, Fingerprint, and Detection Lab on output, explainability, privacy, and pricing.
• Volance vs Google reCAPTCHA | Explainable detection — How Volance differs from Google reCAPTCHA: a graded, evidence-backed score, separate human / agent / bot classes, and server-side enforcement.
• Volance vs Cloudflare Turnstile | Graded scores — How Volance differs from Cloudflare Turnstile: a graded, explainable score and separate human / agent / bot classes.
• Volance vs Fingerprint | Explainable scoring — How Volance differs from Fingerprint: on-site, explainable session scoring without a persistent visitor ID.
• Volance vs Detection Lab | Scoring compared — Volance vs Detection Lab: both score sessions transparently with behavioural signals. The differences are output shape, governance, pricing, and scope.

Use cases

• Use cases | Bot and agent detection where it matters — Where Volance fits: whole-site visibility, checkout and signup, marketplaces, API and trial abuse, and publishers protecting content.
• Site-wide bot and agent detection — Understand every session across a site, not just the form: on-site behavioural signals, a graded score, and enforcement that stays on your server.
• Bot detection for checkout and signup — Score the signup and checkout requests that matter: fake accounts, card testing, and coupon abuse, with evidence and a decision that stays on your server.
• Bot detection for marketplaces — Separate real buyers and sellers from scrapers, multi-accounting, and fake listings with on-site signals and explainable scoring.
• API and trial-abuse detection — Score request-level evidence for APIs and trials without inventing browser activity: a server-only integration for abuse detection.
• Bot detection for publishers — Tell readers, search crawlers, and content scrapers apart with on-site signals and explainable scoring.

Blog

• Blog | Bot and agent detection, explained — Notes on behavioral bot and agent detection: what a score can and cannot prove, turning scores into policy, and how signed agents change the picture.
• Checkout and signup signals — Fake accounts, card testing, and coupon abuse hit the same two pages. Here is what behavioural signals can tell you.
• API abuse without a browser — APIs and free trials get farmed, but there is no page to instrument. Score the request evidence your edge already has.
• How Web Bot Auth works — A practical walkthrough of signed agent requests: what is signed, where the key lives, and how a verifier decides.
• We red-teamed our own detection — We pointed our red team at a live site we operate, then watched the classification, decisions, and notional toll land in the dashboard.
• What share of traffic is automation? — Every major 2026 report puts automation at or above half of web traffic. The useful question is what kind of automation it is.
• Measurement is not proof (and why that is fine) — A detection score is an estimate, not a verdict of identity. That is not a weakness — it is the only honest way to describe what session scoring can do.
• From a bot score to a policy: allow, flag, block — A score is not a decision. This is how the bands, verdicts, and actions fit together, and why enforcement belongs on your server.
• Signed vs spoofed Web Bot Auth — How verified, spoofed, and unresolved Web Bot Auth signers differ — and why an unknown signer should never be punished.

Company

Volance is a product of Oops Games LLC. Contact: [email protected]. X: @volancehq. GitHub: oops-games-llc.

Machine-readable files

• /llms.txt — the concise text index.
• /llms-full.txt — the page-by-page text index.
• /sitemap.xml — every indexable URL.
• /feed.xml — the blog feed.
• /atlas/snapshot.json — the Atlas data snapshot.