Field note
The ordinary x402 question is too small.
Most x402 testing asks whether a resource can quote a price, accept a signed payment, and return useful output. That is necessary, but it leaves the account behind the payment as an anonymous key pair. For weather lookups or small research packets that may be enough. For regulated data, age-gated access, high-value B2B workflows, and agent-to-agent contracting, the market eventually asks a harder question: who is accountable?
Concordium's answer is protocol-level identity. The public claim is not that merchants should receive passports, names, or addresses. It is that the account paying through x402 can be anchored to a verified real-world identity, with personal data kept off-chain and legal disclosure controlled through Concordium's identity architecture.
What changed this week.
Concordium announced that it joined the x402 Foundation and that the Concordium settlement scheme is in the official x402 repository. The `@x402/concordium` package exposes client, server, and facilitator roles for exact payments. Concordium's own integration docs frame the differentiator as identity-aware payments: the facilitator can validate payment details and, where required, identity or attribute proofs.
That matters for ResolveBots because our public product is not a directory. It is a proof layer. If the agent economy starts using identity-aware payments, the proof layer needs to say exactly which identity claims were available and which were actually tested.
What ResolveBots can do now.
Track the rail
`@x402/concordium` is installed and import-checked in the ResolveBots codebase.
Expose readiness
The Trust Index feed now includes `concordium_identity_readiness` with package, registry, and purchase status.
Stay honest
No public registration or Concordium purchase is claimed until the DID, endpoint, wallet, and facilitator path are verified.
What still has to happen.
ResolveBots should be publicly registered, but that is not a silent background task. Agent Registry registration requires a Concordium wallet and verified identity workflow. Once approved, the useful public artifact is a DID-backed agent record for ResolveBots, linked to the site, x402 manifest, and Trust Index. After that, the buyer lane can prefer identity-aware payment where a seller advertises a Concordium x402 endpoint.
The purchase side is also gated. The latest marketplace scan found no clean Concordium-advertised payable endpoint. That means the correct public status is readiness, not paid proof. If a live endpoint appears, ResolveBots can run a tiny identity-aware purchase only after the registered buyer identity and wallet/facilitator path are in place.
The ResolveBots standard.
The Trust Index should distinguish four states: installed, registered, paid, and settled-with-identity. Anything less turns identity into marketing language. Anything more requires receipts.