Registry-backed preflight · Agent payments

Before an agent pays, check whether you should accept it.

Payment rails help agents spend. Acceptance checks help counterparties say yes: who is responsible, what is authorized, what limit applies, and what receipt proves it.

Run demo preflight Open Agent Registry Download receipt JSON

Point of the build

Turn x402 attention into registry inspection.

An HTTP payment request is only half the commercial decision. A paid API, merchant, marketplace, or other agent also needs a counterparty verdict before granting access.

Default demo agent

#40

Gregers in the Concordium Agent Registry.

1. RequestAgent asks for paid API access.

2. RegistryCheck token, status, wallet, and card URI.

3. Card hashFetch card and compare to on-chain metadata hash.

4. PolicyBind authorization, limit, expiry, and receipt need.

5. VerdictAccept, inspect first, or reject.

Live registry-backed verdict

This call checks the public Concordium Agent Registry and the served agent-card hash. Use a different token id to inspect another registered agent.

Check in Registry

Verdict

Loading…

Fetching registry evidence.

Receipt packet

Loading…

Boundary

This is a Concordium/Gregers reference preflight. It does not run a fresh payment and does not grant production API access. No Coinbase, Base, x402, Cloudflare, Fastly, OpenClaw, or partner integration implied. It demonstrates the registry-backed decision shape a counterparty can require before accepting autonomous-agent activity.