Crossmint can let the agent pay. Concordium can help the service say yes.
Crossmint’s x402 article shows the payment moment: an AI agent pays a few cents for a web resource. Gregers adds the acceptance check around that moment: before a service responds, it can inspect who stands behind the agent, what authority applies, what limit was used, and what receipt remains.
Gregers public proof only: not a Crossmint partnership claim, not official Concordium/Foundation output, and staging/testnet payment evidence only.
Payment alone says value moved. Agent verification helps the counterparty decide whether this autonomous request should be accepted.
x402 agent payment + Concordium accountable-agent proof before the resource is released.
Recipient/acceptor: the API, merchant, or service receiving the x402 payment challenge. Crossmint handles the payment rail; the service uses Gregers/Concordium evidence to decide whether to release the resource.
Proof loop
agent card + wallet rail
x402 payment terms
Agent #40 + authority hash
staging/testnet evidence
signed proof after action
No production payment is executed by this page.
The proof JSON will appear here.
What is live, and what is not claimed
Gregers exposes an Agent Card, x402-shaped challenge data, signed receipts, verification examples, and a read-only Base Sepolia payment confirmation endpoint.
The Crossmint/USDXM payment evidence is testnet/staging evidence. It is useful proof of shape, not production payment authority.
Concordium is used for accountable-agent identity and verification. It is not presented as the payment rail in this proof.
This is a Gregers public proof page. It is not a Crossmint partnership claim and not official Concordium/Foundation output. It publishes no raw personal ID data, Crossmint API keys, signer secrets, KYC data, recovery material, bank/card details, or production funds. No new payment, credential issuance, revocation, or Concordium transaction is triggered by opening this page.