Seller acceptance for x402 agents

The seller-side check for x402 agents.

A trading agent wants to buy fresh market data before moving money. x402-style payment flows can get it to checkout. The seller still needs to know: who controls the agent, what it may buy, what cap applies, and what receipt survives.

For API sellers, data providers, SaaS vendors and marketplaces asking the next question after agent payment: should this agent be accepted?

Try the 30-second seller check Open seller kit View live acceptance receipt Open JSON for builders

American-market use case

A trading agent buys fresh data before moving money.

The point is not another wallet. The point is whether a serious API seller, SaaS vendor, broker, marketplace, or logistics counterparty can safely accept an autonomous buyer.

Thesis

x402-style payment evidence can show payment capability or settlement evidence. Acceptance proof explains why the seller still verified authority, policy, receipt binding and freshness before serving data.

Run a seller-side acceptance check

1. Agent requests
fresh market data

2. API prices
x402 payment requirement

3. Agent pays
0.25 USDC

4. Seller verifies
authority, policy, cap, receipt

5. Seller releases
data/service + receipt

Scenario

Trading data

Run live check Open API URL

Live verdict

Not run yet

Choose a scenario, then run the live registry-backed acceptance API for Agent #40.

Acceptance receipt

The receipt will appear here.

Boundary

This is a public Gregers/Concordium reference demo. It does not claim a Coinbase, Base, You.com, Glassnode, Cloudflare or x402 partnership/integration. It does not execute a fresh payment. It reuses the live Concordium Agent Registry-backed acceptance API to show the seller-side decision shape.