Summary
XDC Network is integrating Concordium as the identity verification provider for XDC AI, allowing agents to prove that they are backed by a verified individual or business without publicly exposing the owner’s identity. The move addresses accountability as autonomous agents gain access to wallets and payment functions.
AI agents are moving from software tools to financial actors
XDC Network is adding an identity verification layer to XDC AI, its marketplace for autonomous agents, by selecting Concordium as the platform’s exclusive identity verification provider. According to reporting by The Next Web, the integration is designed to let an AI agent prove that a verified individual or business stands behind it without publishing the owner’s identity on-chain.
The development comes as AI agents begin to move beyond generating content or calling software APIs. XDC AI, which the source says launched in July 2026, enables autonomous agents to discover services and make payments in USDC through non-custodial wallets using the x402 payment standard. Once an agent can control or use a wallet and initiate a financial transaction, the question is no longer only whether the payment can be executed. It is also whether other participants can identify the person or organisation responsible for the agent’s actions.
Addressing the accountability gap
Blockchain payment systems can provide records of wallet addresses, signatures and transaction outcomes. Those records do not necessarily reveal who controls an address or which organisation has authorised an automated process to use it. For businesses considering autonomous agents for financial operations, that distinction can create a gap between transaction visibility and accountability.
The Concordium integration is intended to narrow that gap without turning personal information into public blockchain data. Agents operating on XDC AI can receive publicly verifiable on-chain badges confirming that an authenticated owner stands behind them. At the same time, the owner’s personal information remains off-chain.
This design separates two ideas that are often treated as the same: proving that an identity has been verified, and disclosing the details of that identity. Publishing passport information or other personal data on a public network would create obvious privacy concerns. A completely anonymous wallet, however, gives a counterparty little basis for determining whether a responsible person or business exists behind an agent. A verification badge offers an intermediate signal: a public claim that can be checked without making the underlying identity record public.
The approach may be relevant to businesses that need to distinguish among agents, suppliers or automated accounts while limiting unnecessary disclosure. It can also give service providers more context than a standalone wallet address would provide. But the badge should be understood as an identity-related credential, not as a complete assessment of the agent, its owner or every transaction it conducts.
How the verification process works
The reported process begins with the agent owner completing a passport and liveness check through the Concordium Wallet. The check is conducted by an independent identity provider. After verification, the owner links an XDC wallet to the agent using two signatures that do not transfer funds, then registers the agent to receive the verification badge.
The sequence creates several distinct control points. The identity check is intended to establish that a real individual or business has been authenticated. The signatures are used to demonstrate control of the relevant wallet without moving assets. The registration step associates that wallet and verification status with a particular agent.
That separation matters because an identity check alone does not demonstrate control of a blockchain account, while wallet control alone does not establish who is behind the account. Combining the two creates a more explicit relationship between the verified owner, the wallet and the autonomous agent.
The model also raises operational questions that are not fully answered in the available announcement. Participants will need to understand how verification statuses are updated, how badges can be revoked or expire, and what happens if a wallet is compromised or an owner changes the agent’s operating authority. Those procedures will be important if the credential is used in real financial workflows rather than simply as a public label.
What it could mean for agent payments
XDC AI is positioned as an agent payments marketplace. Its agents can discover services and use non-custodial wallets to make USDC payments under the x402 standard. Adding an identity layer changes the platform’s focus from whether an agent can call a service or transfer funds to whether a counterparty can establish who is responsible for that activity.
For service providers, a verifiable association with an individual or business may provide additional information when deciding how to interact with an agent. A provider could distinguish an agent linked to an authenticated owner from an address with no stated relationship to a responsible party. For organisations deploying agents, the credential could become one input into internal reviews of permissions, vendor relationships or unusual activity.
However, the identity badge does not resolve the full set of risks created by autonomous payments. It does not show that the agent has been granted the appropriate authority, that a transaction complies with an organisation’s policies, or that the agent’s software is operating as intended. It also does not by itself protect private keys, prevent a compromised wallet from being used, or determine who should bear responsibility if an agent makes an erroneous payment.
Those issues require separate controls, including permission management, transaction limits, monitoring and procedures for suspending activity. Identity can support those controls by making the responsible party easier to identify, but it cannot replace them.
Privacy is useful, but not the same as compliance
Keeping identity information off-chain can reduce the risk of exposing sensitive personal data on a public ledger. It also creates governance requirements. Users and counterparties may need clarity on who stores the verification data, under what circumstances it can be disclosed, how long it is retained, and how a public badge reflects a change in verification status.
The source material describes the passport, liveness and wallet-linking process, but does not provide a complete account of the regulatory arrangements in every jurisdiction or the treatment of data across borders. Those details may become more significant as agents are used for financial services rather than low-risk software interactions.
A verified identity should also not be confused with full regulatory compliance. Depending on the activity and jurisdiction, compliance obligations can include customer identification, anti-money-laundering controls, sanctions screening, transaction monitoring, recordkeeping and explicit authority management. A public credential may support some of these processes, but it does not demonstrate that all of them have been completed for a particular owner, agent or transaction.
Institutions using autonomous agents will still need to define what the agent may do, which wallet permissions it receives, how exceptions are escalated and who handles disputes. Service providers will likewise need policies for expired, revoked or unverifiable badges. These questions are especially relevant when an agent operates continuously or interacts with counterparties that have different compliance requirements.
A broader infrastructure trend
The XDC-Concordium integration reflects a wider shift in how the industry is thinking about agent infrastructure. A blockchain address traditionally represents control over assets and the ability to sign transactions. In an agent economy, an address may also represent a software entity acting on behalf of a person or organisation. That creates demand for a link between automated behaviour and an accountable principal.
Whether such identity layers gain broad adoption will depend on interoperability, privacy protections and the ability of businesses to incorporate credentials into existing risk and compliance systems. It will also depend on whether the credentials remain meaningful over time: verification must be maintained, authority must be updated and compromised or misused agents must be distinguishable from active, properly authorised ones.
For XDC AI, the current integration provides a mechanism for verifying the owner behind an agent while keeping the owner’s personal details off-chain. It does not, on the information currently available, solve every question around permissions, continuous monitoring or cross-platform accountability. Those issues will need to be addressed as autonomous agents take on more financial functions.
The central change is therefore not simply that an AI agent can make a USDC payment. It is that the payment can be associated with a verifiable responsible party without requiring that party’s identity to be exposed publicly. That is a meaningful step toward accountable agent payments, but its practical value will ultimately depend on the surrounding controls, governance and regulatory treatment.
Source: link