The launch of Moca Chain’s mainnet marks a pivotal moment for the intersection of blockchain technology, digital identity, and the rapidly expanding world of autonomous AI agents. Animoca Brands’ Moca Network, together with the Moca Foundation, has moved beyond testnets to deliver a purpose‑built ledger that treats identity as a first‑class citizen rather than an afterthought. This shift arrives as AI agents evolve from simple chatbots into actors capable of shopping, booking travel, subscribing to services, and even negotiating contracts on behalf of their human principals. The core challenge that has emerged is not merely whether an agent can perform a task, but how a service provider can verify that the agent is legitimately acting for a specific user and that its actions stay within the bounds of the user‑granted authority. Existing identity systems, which were designed around static human profiles, force users to repeat verification steps across countless platforms, creating silos of personal data that agents must constantly re‑present. By contrast, Moca Chain proposes a portable, verifiable credential model that travels with the agent, allowing businesses to trust the delegate without repeatedly collecting sensitive information. In the following sections we unpack the technical architecture, the economic incentives for early adopters, and the practical steps organizations can take today to prepare for an agent‑centric future.

Today’s internet identity landscape is a patchwork of username‑password pairs, OAuth flows, and knowledge‑based authentication, each requiring users to hand over personal details and then re‑authenticate whenever they switch services. This model worked adequately when the primary actors were people who infrequently changed contexts, but it breaks down when an AI agent needs to traverse a dozen different APIs in a single workflow. Imagine a travel‑planning agent that checks flight prices, books a hotel, purchases travel insurance, and updates a calendar – each step demands proof of identity, age, residency, or payment capability. If the agent must present a fresh copy of a driver’s license or a bank statement at every hop, the user’s data proliferates across service providers, increasing both privacy risk and operational friction. Moreover, the repetitive verification process adds latency that can erode the convenience agents promise. Moca Chain addresses this by anchoring identity claims on a tamper‑ resistant blockchain, where a trusted issuer (such as a bank, telco, or government agency) signs a credential that the user stores in a personal wallet. When an agent needs to prove a fact, it presents the cryptographically signed credential; the verifier checks the signature against the issuer’s public key and confirms that the credential has not been revoked. Because the credential lives on‑chain, any update or revocation is instantly visible to all relying parties, eliminating the need for users to resubmit documents.

The introduction of AI agents adds a layer of delegation that traditional identity frameworks were never designed to handle. In the physical world, granting someone power of attorney requires a notarized document that clearly delineates the scope of authority – what actions they may take, which assets they can touch, and for how long the authorization remains valid. Digital agents, however, often operate under vague or overly broad permissions, such as ‘full account access,’ which creates a mismatch between user intent and actual capability. This mismatch is especially risky when agents handle financial transactions, personal data, or access to privileged services. Moca Chain’s approach treats delegation as a first‑class attribute of identity. Rather than issuing a blanket credential that says ‘you are Jane Doe,’ the system enables the issuance of scoped credentials that encode specific permissions, such as ‘may book flights up to USD 400 using card ending in 1234’ or ‘may view subscription status but not modify billing details.’ These scoped credentials are themselves verifiable on‑chain, allowing a relying party to confirm not only that the agent is acting for Jane Doe, but also that the requested action falls within the delegated authority. Crucially, because the user holds the credential in their wallet, they can modify or revoke the permission at any time, and the change propagates instantly across the network. This fine‑grained control aligns digital delegation with the legal principles of limited power of attorney, while preserving the speed and automation that AI agents promise.

Unlike general‑purpose blockchains that later bolt on identity modules through smart contracts or sidechains, Moca Chain was architected from genesis to treat identity as a core primitive. The consensus mechanism, transaction format, and state model are all optimized for the creation, transfer, and verification of verifiable credentials (VCs) compliant with W3C standards. This design choice yields several practical advantages. First, transaction fees for credential issuance and presentation remain predictable and low, because the network does not need to execute complex smart‑contract logic for every identity check. Second, the ledger’s data structures support efficient revocation mechanisms, such as bit‑vector or accumulator‑based schemes, ensuring that a revoked credential is instantly recognized without scanning through massive logs. Third, developers benefit from a clear separation of concerns: identity‑related operations are handled by the protocol layer, while business logic can reside in off‑chain services or in lightweight smart contracts that simply verify signatures. By avoiding the overhead of a generic virtual machine for identity tasks, Moca Chain can achieve higher throughput and lower latency, which is essential when agents need to present credentials in real time across multiple service endpoints. Moreover, the chain’s governance model incorporates representatives from sectors that are natural credential issuers – finance, telecommunications, retail, and ticketing – ensuring that the technical specifications reflect real‑world requirements for trust, privacy, and interoperability.

When an organization decides to issue a credential on Moca Chain, the process begins with off‑chain verification of the user’s attributes. For example, a bank might confirm that a customer has passed KYC, holds a checking account, and resides in a specific jurisdiction. Once satisfied, the bank creates a JSON‑LD document describing these claims, signs it with its private key, and records the signed document as a transaction on Moca Chain. The resulting on‑chain entry contains a cryptographic hash of the credential, the issuer’s identifier, timestamps, and, optionally, a revocation registry pointer. The user receives the credential (typically stored in a mobile wallet or browser extension) and retains full control over when and how to share it. When a service provider needs to validate a claim – say, whether the user is over 18 or possesses a loyalty‑tier status – it requests the relevant credential from the agent. The provider then checks the signature against the bank’s published public key, verifies that the credential has not been revoked by consulting the on‑chain revocation list, and ensures that the credential’s subject matches the decentralized identifier (DID) presented by the agent. Because the verification relies solely on cryptographic proofs, the provider never sees the raw underlying data (such as the user’s full name or address) unless the credential deliberately includes it. This zero‑knowledge‑friendly model dramatically reduces the data exposure surface for both users and businesses, while still providing strong assurances about the truth of the claim.

Complementing the core blockchain, Moca Network has launched AIR – the Agent Identity and Rights layer – as an integrated middleware stack that bundles identity, payments, and loyalty functionalities into a single API surface for enterprises. AIR sits atop Moca Chain, abstracting away the intricacies of transaction signing, key management, and credential formatting while exposing straightforward endpoints for credential issuance, presentation, and verification. Enterprises can onboard users by invoking AIR’s ‘create credential’ endpoint, which guides them through the necessary KYC or AML checks, then automatically records the resulting VC on the ledger. Conversely, the ‘verify credential’ endpoint lets a service confirm a user’s age, membership level, or payment capability without building custom verification logic. AIR also includes a payments module that enables frictionless settlement of transactions initiated by AI agents, using the same verified credentials to authorize debits or credits. The loyalty component allows points, rewards, or access tiers to be issued as verifiable credentials, making them portable across partner networks and easily redeemable by agents. By consolidating these functions, AIR reduces integration overhead for businesses that would otherwise need to maintain separate contracts with identity providers, payment gateways, and loyalty platforms. Importantly, AIR is designed to be extensible: new data partners – such as credit bureaus, utility companies, or educational institutions – can plug into the ecosystem by issuing their own VCs on Moca Chain, thereby expanding the repertoire of attributes that agents can present.

AIR’s bidirectional architecture creates powerful network effects. On one side, organizations can transform the verification checks they already perform – such as fraud screening, address validation, or subscription eligibility – into reusable, on‑chain credentials. For instance, an e‑commerce retailer that runs an address verification service can issue a VC confirming that a user’s shipping address is valid and deliverable. Once that VC exists on Moca Chain, any other partner in the network (a logistics provider, a digital wallet, or a ticketing platform) can accept it without repeating the verification, saving time and reducing operational costs. On the other side, businesses can accept credentials issued by trusted peers, accelerating user onboarding and unlocking personalized experiences based on verified data. A streaming platform, for example, could accept a VC from a telecom operator that proves a user subscribes to a premium mobile plan, thereby granting immediate access to a bundled entertainment offering without requiring the user to re‑enter payment details or endure another KYC flow. This two‑way flow not only diminishes the duplication of effort but also encourages data minimization: each party stores only the credentials they need to issue, rather than maintaining sprawling databases of personal information. Over time, as more participants contribute credentials, the network’s collective knowledge base grows, enabling richer, more contextual services while preserving user privacy through selective disclosure.

From a privacy standpoint, Moca Chain’s credential model aligns with emerging regulatory expectations such as GDPR’s data minimization principle and the forthcoming EU Digital Identity Wallet framework. Because credentials are cryptographically sealed, a verifier can confirm a claim (e.g., ‘over 21’) without learning the exact birth date, address, or any other superfluous detail. Moreover, users retain the ability to disclose only a subset of a credential’s attributes through selective disclosure protocols, revealing precisely what is necessary for a given transaction. For example, an agent seeking to rent a car might prove that the user holds a valid driver’s license and is over 25, without sharing the license number or the holder’s home address. This selective disclosure capability is built into the VC format and is supported by AIR’s SDKs, making it straightforward for developers to implement privacy‑preserving flows. Additionally, the user‑centric storage model ensures that the individual, not a centralized database, is the custodian of their identity assets. If a user wishes to stop sharing a particular credential, they can simply withdraw it from their wallet; the on‑chain record remains, but relying parties will see it as revoked if the issuer has updated the revocation registry, or they will simply cease to accept it if the user no longer presents it. This shift from data hoarding to data sharing on demand reduces the attack surface for breaches and gives users a tangible sense of control over their digital footprint.

The true power of Moca Chain emerges when it comes to defining and enforcing agent permissions. Traditional API keys or OAuth tokens often grant broad scopes that are difficult to constrain after issuance, leaving users vulnerable to overreach. In contrast, AIR allows users to attach explicit policy statements to the credentials they share with an agent. These policies can specify monetary limits (e.g., ‘maximum transaction amount USD 200 per day’), merchant categories (e.g., ‘only travel‑related purchases’), time windows, or even contextual constraints such as ‘only between 9 am and 6 pm local time.’ When an agent attempts to invoke a service, the relying party checks not only the authenticity of the user’s identity credential but also verifies that the requested action complies with the attached policy. If the policy is violated, the transaction is rejected, even if the agent’s identity is sound. Because policies are expressed as machine‑readable rules (often using standards like ODRL or REL), they can be evaluated automatically by the verifier’s backend, enabling real‑time enforcement without human intervention. Moreover, users can update or revoke these policies at any time by issuing a new credential or a revocation notice, instantly altering the agent’s permissible behavior across all connected services. This dynamic, fine‑grained control transforms agents from potentially omnipotent scripts into trustworthy assistants whose actions are transparently bounded by the user’s expressed intent.

The launch mainnet is already backed by a diverse consortium of early adopters that signals strong cross‑industry interest. Partners span consumer platforms (SK Planet, Biletinial, Oyunfor), fintech and crypto services (Inveo Kripto, Plume, Nansen), loyalty and engagement programs (Open Campus, OneFootball), and even high‑end brands such as Automobili Lamborghini. Each participant brings a distinct set of credentials they can issue or consume: telcos can provide proof of subscription or device ownership; banks can attest to KYC status and account balances; retailers can verify purchase history or loyalty tier; entertainment platforms can confirm membership or ticket holdings. This variety creates a network effect where the value of holding a credential rises with the number of places where it can be used. For developers, the presence of established partners reduces the risk of building on a nascent chain, as there are already real‑world use cases to reference and potential customers to target. For enterprises, joining the ecosystem offers a pathway to reduce onboarding friction, lower identity‑verification costs, and access new customer segments that prefer privacy‑preserving interactions. Moreover, the involvement of a marquee brand like Lamborghini showcases that even luxury markets see verifiable credentials as a way to deliver exclusive experiences — such as granting an agent‑driven concierge service access to private showrooms — without exposing the client’s full personal profile.

Looking at the broader market, the rise of agentic commerce is projected to generate billions of dollars in transaction volume over the next five years, driven by advancements in large language models, reinforcement learning, and seamless API integrations. Yet, industry surveys consistently cite trust and authorization as the primary barriers to widespread adoption. Businesses fear that unleashing AI agents could lead to unauthorized purchases, data leaks, or regulatory violations, while users worry about losing control over their financial and personal data. Moca Chain’s approach directly addresses these concerns by offering a verifiable, portable, and revocable trust layer that separates the question of ‘can the agent act?’ from ‘may the agent act in this specific way?’ This separation mirrors the evolution of internet security, where transport‑layer security (TLS) handled confidentiality and authentication, while application‑level scopes (OAuth, OpenID Connect) managed authorization. By moving authorization into the credential itself, Moca Chain enables a more granular, user‑centric model that can coexist with existing authentication systems. Furthermore, as regulators begin to scrutinize AI‑driven financial services – think of the SEC’s focus on AI‑based trading advisors or the CFPB’s interest in automated lending – having an auditable, on‑chain trail of who authorized what and when could prove invaluable for compliance. Early movers who adopt verifiable credentials may therefore gain a competitive advantage not only in user experience but also in regulatory readiness.

For organizations looking to prepare for an agent‑enabled future, the first step is to inventory the identity checks they currently perform and assess which of those can be turned into verifiable credentials on Moca Chain. This might include KYC outcomes, address validation, fraud‑risk scores, or subscription status. Engaging with the AIR SDKs early will allow developers to prototype credential issuance and verification flows in a sandbox environment before committing to mainnet deployment. Second, define clear permission policies for any AI agents you intend to deploy. Use standard policy languages (ODRL, REL) to express limits on transaction amounts, merchant categories, time windows, and data disclosure, then bind those policies to the credentials you share with the agent. Third, consider becoming a credential issuer within the Moca ecosystem; by doing so you not only create a new revenue stream (e.g., charging partners for verification services) but also strengthen the network effects that make the platform more valuable. Fourth, if you are a consumer or a developer building agent‑driven applications, start experimenting with a personal wallet that supports Moca Chain VCs, practice selective disclosure, and become comfortable with revoking and updating credentials as your needs change. Finally, monitor the evolving partner landscape – the current list of collaborators is just the beginning. As more sectors join, the utility of holding a verifiable credential will increase exponentially, making early adoption a strategic move for anyone who wants to stay ahead in the shift toward autonomous, trust‑mediated digital interactions.