Each capability, what it does, and where it lives in your existing merchant stack. The full platform deploys behind a single CDN routing rule and runs in front of the fraud engine and checkout you already operate.
BladeRun verifies agent identity at both your boundaries: BladeRun.js on the page when the agent first lands on your customer-facing surface, and BladeRun Gateway at the API when the agent calls your checkout. Registered agents arrive with verifiable mandates carrying scope, spend cap, and the principal who issued them. Unregistered agents are scored against a behavioral baseline at both points.
The agent boundary is your new perimeter. The verifier sits in front of your existing fraud engine, not next to it.
Most merchants today either reject all bot traffic, including the high-conversion shopping agents, or let synthetic abuse through. Both are bad. BladeRun.js scores the agent at the page layer the moment it lands; the Gateway picks up the scored session when the same agent calls your API. Your fraud engine sees a labeled request, not a guess.
Your highest-intent purchase channel, registered, mandated agents, gets a clean conversion path. Everything else gets scored or blocked.
An AP2 or MPP mandate is more than just a credential. It carries explicit authorization scope: which merchants the agent may transact with, which categories, which spend cap. The Gateway enforces that scope on every request before it reaches your checkout.
Your existing fraud rules consume the BladeRun signals as additional features. Your downstream API code does not change.
When an issuer disputes an agent-initiated transaction, you have the entire context in one signed packet: agent identity, verified mandate, scope match, behavioral score, cryptographic timestamp. Stored in your S3 bucket, under your KMS keys.
Disputes that previously tilted against the merchant by default now have evidence the issuer can validate independently.
Opt-in. The Gateway forwards anonymized, one-way signal hashes, synthetic-agent fingerprints, mandate-spoof patterns, abuse signatures, to the merchant Federation Network. Within a minute, every other member merchant has the protection.
Your data does not leave your environment; only the privacy-preserving signal hash does. Membership is double-blind, even from BladeRun staff.
The full merchant-side product page, protocols supported, threat coverage, deployment.
Explore Merchants →The reverse proxy at the agent boundary, verifies, scores, routes into your fraud engine.
Explore Gateway →Per-agent chargeback evidence in your S3 under your KMS keys. Issuer-verifiable.
Explore Time Machine →Cross-merchant agent reputation. One-way signal hashes. Double-blind membership.
Explore Federation →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.
