{"id":76428,"date":"2026-08-05T22:26:06","date_gmt":"2026-08-05T22:26:06","guid":{"rendered":"https:\/\/crowdfundjunction.com\/blog\/moca-network-ceo-explains-why-ai-agents-will-need-provable-identity\/"},"modified":"2026-08-05T22:26:06","modified_gmt":"2026-08-05T22:26:06","slug":"moca-network-ceo-explains-why-ai-agents-will-need-provable-identity","status":"publish","type":"post","link":"https:\/\/crowdfundjunction.com\/blog\/moca-network-ceo-explains-why-ai-agents-will-need-provable-identity\/","title":{"rendered":"Moca Network CEO Explains Why AI Agents Will Need Provable Identity"},"content":{"rendered":"

(Originally posted on : Bitcoin News )<\/b>
\n<\/p>\n

\n

Agents Move From Answering to Acting<\/h2>\n

Kenneth Shek is the Project Lead of Moca Network and Director of Projects Management at Animoca Brands. Shek\u2019s argument begins with a simple prediction: Artificial intelligence (AI) agents<\/a> will stop behaving like passive AI chatbots and start acting as digital representatives. \u201cThe way I think about this is very simple: every user will eventually have their own agent,\u201d Shek told Bitcoin.com News.<\/p>\n

The Moca Network<\/a> CEO added:<\/p>\n

\n

\u201cOnce that happens, the agent is not just a chatbot anymore. It is not just answering questions. It is doing things for you. It may spend your money, verify your data, redeem your rewards, use your airline status, or buy something on your behalf.\u201d<\/p>\n<\/blockquote>\n

That transition raises questions that ordinary passwords and application programming interface (API) keys were never designed to answer. API keys let one piece of software communicate with another, while delegated credentials grant limited access to an outside service. Neither mechanism, by itself, proves the complete relationship among the agent, the person behind it and the precise boundaries of its authority.<\/p>\n

\u201cYou cannot just give the agent your raw key,\u201d Shek said. \u201cYou cannot just give it a broad API credential and hope everything works out. That is too much power, and it does not answer the real questions. Who is behind the agent? Which user does it represent? What data is it allowed to verify? How much money can it spend? Where can it spend? For how long? And if something changes, can I revoke that permission?\u201d<\/p>\n

Businesses Start Screening for the Right Bots<\/h2>\n

The commercial internet has spent years trying to identify and block automated traffic through CAPTCHA tests, fraud systems and bot filters. Shek expects that model to change as businesses begin treating approved AI agents as potential customers rather than unwanted visitors.<\/p>\n

\u201cI have said before that the world is moving from screening out bots to screening for the right bots,\u201d he explained. \u201cBefore, websites used CAPTCHA to block bots. Now, many businesses actually want the right agents to come in, because those agents may become customers, buyers, or transaction flow. But the business still needs to know: Is this a good bot, who is behind it, and is it allowed to pay?\u201d<\/p>\n

Shek added that identity becomes the source of those answers. A trusted agent would need to prove that it is connected to a real user, that the user authorized a particular action and that the authorization remains valid. \u201cThat data source behind a good bot or bad bot is identity,\u201d he said.<\/p>\n

Users Set the Boundaries<\/h2>\n

Shek describes provable agent identity as \u201cidentity plus agent.\u201d Under that model, the user remains at the center, while the agent receives specific, revocable permissions to interact with payments, commerce, loyalty programs and personal data.<\/p>\n

\u201cThe agent can only act on those spokes if the user can define the policy,\u201d Shek remarked during the interview.<\/p>\n

Moca Network\u2019s AIR system is intended to add that policy layer to its existing identity infrastructure. According to Shek, an artificial intelligence (AI) agent<\/a> could receive permission to use or verify selected information without gaining permanent control over a user\u2019s accounts. \u201cThe agent can spend money, use data, and verify data on behalf of the user, but only in a safe, privacy-preserving, user-controlled way,\u201d he said.<\/p>\n

Everyday Transactions Expose the Identity Gap<\/h2>\n

\u201cIf I want my agent to buy a bottle of alcohol online, the supermarket needs to verify my age, even though the agent is the one doing the action,\u201d Shek noted. \u201cIf I want my agent to use my airline status for priority booking or points attribution, the airline needs to verify my loyalty status through the agent. If I want my agent to spend money, I need to control how much it can spend, where it can spend, when it can spend, and for how long.\u201d<\/p>\n

\u201cAll of that is still identity,\u201d he added. \u201cIt is just identity plus agent.\u201d<\/p>\n

Credentials Limit What Gets Revealed<\/h2>\n

Shek suggested that users could share information through full disclosure, selective disclosure or technology leveraging zero-knowledge proofs<\/a>. Full disclosure reveals the entire credential. Selective disclosure reveals only the fields needed for a transaction. A zero-knowledge proof allows someone to prove that a condition is true without exposing the underlying data.<\/p>\n

\u201cWhat AIR enables is a cross-app SSO which resolves into a single unified identity, and enables data to be shared by users from one app to another via verifiable credentials,\u201d Shek stated. \u201cAll data with explicit consent, revocable, and fully controlled by the users.\u201d<\/p>\n

Moca Extends Its Existing Identity Stack<\/h2>\n

Shek explained how Moca Network is building on its existing identity infrastructure.<\/p>\n

\u201cMachine identity is basically leveraging the already fully built enterprise-grade identity infrastructure,\u201d Shek elaborated, \u201cand adding principal-agent binding and policy and agent delegation management, which gives user control of what, how and when data agents could use to verify with applications or agents on behalf of the principal.\u201d<\/p>\n

Components that could transfer into agent identity include decentralized data storage for encrypted, continuously available user data; onchain issuance and verification for identity records and audit trails; and cross-chain interoperability across different blockchains and wallets, among numerous others.<\/p>\n

Permissioning Becomes the Deciding Test<\/h2>\n

\u201cThink a hub-and-spoke model,\u201d the Moca Network executive remarked. \u201cEverything starts from the user as the hub with all data controlled by the user. The spokes are the many agents the user would own. With AIR, the user could control which agent could verify what data, for how long, by which verifier.\u201d<\/p>\n

\u201cAll user data are accessible by the user only via the always-on decentralized data storage,\u201d Shek concluded, \u201cand users could choose to grant to and revoke from any data verifications, all cryptographically governed.\u201d<\/p>\n

The next test will be whether companies adopt interoperable credential standards, whether users understand and trust AI agent permission controls and whether businesses are willing to pay for repeated verification. As AI agents proliferate<\/a> and gain access to more financial services, personal records and commercial platforms, provable identity may determine whether they remain sophisticated assistants or become trusted participants in the wider economy.<\/p>\n<\/p><\/div>\n

Source link <\/a>
\n
<\/p>\n","protected":false},"excerpt":{"rendered":"

(Originally posted on : Bitcoin News ) Agents Move From Answering to Acting Kenneth Shek is the Project Lead of Moca Network and Director of Projects Management at Animoca Brands. Shek\u2019s argument begins with a simple prediction: Artificial intelligence (AI) agents will stop behaving like passive AI chatbots and start acting as digital representatives. \u201cThe […]<\/p>\n","protected":false},"author":19,"featured_media":76429,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0},"categories":[32],"tags":[],"_links":{"self":[{"href":"https:\/\/crowdfundjunction.com\/blog\/wp-json\/wp\/v2\/posts\/76428"}],"collection":[{"href":"https:\/\/crowdfundjunction.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/crowdfundjunction.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/crowdfundjunction.com\/blog\/wp-json\/wp\/v2\/users\/19"}],"replies":[{"embeddable":true,"href":"https:\/\/crowdfundjunction.com\/blog\/wp-json\/wp\/v2\/comments?post=76428"}],"version-history":[{"count":0,"href":"https:\/\/crowdfundjunction.com\/blog\/wp-json\/wp\/v2\/posts\/76428\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/crowdfundjunction.com\/blog\/wp-json\/wp\/v2\/media\/76429"}],"wp:attachment":[{"href":"https:\/\/crowdfundjunction.com\/blog\/wp-json\/wp\/v2\/media?parent=76428"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/crowdfundjunction.com\/blog\/wp-json\/wp\/v2\/categories?post=76428"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/crowdfundjunction.com\/blog\/wp-json\/wp\/v2\/tags?post=76428"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}