Platform How it works Banks Merchants Networks Docs Pricing About Get a demo
How BladeRun works · for Merchants

Five capabilities. One agent boundary in front of your fraud engine.

Click each capability to see what it does and where it lives in your existing merchant stack. The diagram on the right highlights the components involved. The full platform deploys behind a single CDN routing rule and runs in front of the fraud engine and checkout you already operate.

VERIFY Where this happens at your perimeter
MERCHANT PERIMETER Shopping Agent OPERATOR · CLAUDE · BOT AP2 / MPP PROTOCOL TRUST ROOTS BladeRun.js PAGE TAG · IN BROWSER CDN · WAF EXISTING EDGE BladeRun Gateway AT AGENT BOUNDARY VERIFY · SCORE · LOG Fraud Engine YOUR EXISTING STACK Merchant API CART · CHECKOUT · INV Issuer / Acquirer PAYMENT · CHARGEBACK Time Machine YOUR S3 · CHARGEBACK PROOF Merchant Federation CROSS-MERCHANT SIGNAL
Pilot it on your traffic

One CDN routing rule.
Visible results in 48 hours.

Point one endpoint at the BladeRun Gateway — search, cart, or checkout. The first week runs in shadow mode so your team sees the agent breakdown on real traffic before any enforcement is enabled.