For AI agents to operate economically, three functions must work together without being confused with one another. Identity → Concordium Agent Registry verifies the agent’s ownership and its association with a verified identity. Payment → x402 carries the payment flow between the agent and the service provider. Network fees → CCD powers transactions on Concordium, while a sponsor or facilitator can cover the fee on the agent’s behalf through a sponsored transaction. These are separate functions, each solving a different part of the process. Identity establishes who stands behind the agent. @x402scan handles payment. concordium:native covers the cost of interacting with the network, even when the agent does not pay that fee directly. That separation matters. An agent’s ability to prove who stands behind it, pay for a service, and get its transaction processed are three distinct requirements. @Concordium brings these components together without treating them as one system. That is how the infrastructure for the agent economy needs to be designed: each function has a clear responsibility, and the connections between them are explicit. concordium:native