Agentic commerce · x402 + ERC-8004
Know who you're paying,
before your agent pays them.
Three tools for agentic commerce on x402 and ERC-8004: validate a counterparty's payment challenge, look up their on-chain identity and reputation, and combine both into a single allow/warn/block decision — before your agent signs a USDC payment on Base.
Agent Commerce Gate, in aggregate — live
630
checks run
60%
allow
35%
warn
5%
block
45
avg. score
Recently scanned
Most recent 50
Each decision is scored against the specific agent identity and payment challenge checked at that moment — not a fixed rating of the endpoint itself. The same URL can score differently for a different counterparty or a different agent ID.
Try Agent Commerce Gate on your own endpoint →The three tools
x402 Inspector
Validate a target endpoint's x402 payment challenge — response shape, network/address format, spec-version detection.
Free · BetaERC-8004 Inspector
Look up an agent's on-chain identity and reputation across six EVM mainnets plus Base Sepolia.
ProAgent Commerce Gate
Combines both into one allow/warn/block decision, plus a receipt endpoint to independently verify a settlement afterward.
How it fits together
Two free tools, one paid decision
x402 Inspector and ERC-8004 Inspector are free forever and independently useful. Agent Commerce Gate combines both into a single scored decision for automated payment gating. Pro feature.
A transparent score, never a black box
Every point in the 0–100 decision is tied to a named, inspectable check. Hard gates override the score for genuinely broken payment setups or unregistered identities — never a hidden formula.
Independently verifiable receipts
After a payment settles, submit the transaction hash and get it checked directly against the chain — not just trusted on your say-so — and bound back to the original decision.
Built on open standards
x402 (Coinbase) and ERC-8004 ("Trustless Agents") are open, multi-party standards — not a proprietary trust ledger only ContextIQ controls. Win on execution, not lock-in.
API-first, built for automation
Every tool here has a paid v1 API — gated by API key or a live x402 payment — so an agent framework can call it before authorizing a payment, not just a human reading a dashboard. Every endpoint also has an x402 wire v2 sibling, for Bazaar/Agent.market discovery.
Who uses it
Agent framework operators
Gate an autonomous agent's payments on a single call instead of hand-rolling identity and payment checks separately.
B2B agentic-commerce platforms
Add pre-payment risk checking and post-payment receipt verification to your own product without building on-chain lookup infrastructure yourself.
Security and compliance reviewers
Audit which counterparties an agent fleet has been paying, why each check allowed, warned, or blocked, and confirm settlements independently.
Frequently asked
What is agentic commerce?
Agentic commerce is the set of protocols and tools that let AI agents autonomously discover, evaluate, and pay for services on the internet, without a human clicking "buy" each time. x402 (HTTP 402 Payment Required) handles the payment side; ERC-8004 ("Trustless Agents") handles on-chain identity and reputation.
How do x402 and ERC-8004 work together?
They solve two different halves of the same problem. x402 lets an endpoint request payment over plain HTTP and lets an agent pay it, but says nothing about who's asking. ERC-8004 gives an agent a portable, on-chain identity and reputation record, but doesn't touch payment. Agent Commerce Gate checks both together before your agent pays.
Is this the same as Stripe's Agentic Commerce Protocol (ACP)?
No. ACP (Stripe and OpenAI) governs how an agent completes a checkout with a merchant that has integrated it. x402 and ERC-8004 are open, chain-based standards for any HTTP endpoint to request and receive payment and prove identity — a complementary layer, not a competing checkout flow.
Does Agent Commerce Gate cost money?
x402 Inspector and ERC-8004 Inspector are free. Agent Commerce Gate, the combined identity + reputation + payment-challenge decision, is a Pro feature: $5/month for the dashboard, or $0.02 per call via API key or a live x402 payment for programmatic use.
What does a "block" decision actually mean?
Block is reserved for genuine impossibility — a payment challenge that can't be parsed at all, or an agent ID that isn't registered anywhere. It's never a judgment call about "how much reputation is enough" — that threshold stays configurable and yours to set.