Agentic Multipass Show Private AI Agent Credentials for Midnight
Alex Pestchanker prototype dey designed to give AI agents identities wey person fit verify while e still keep selected information private. Mandates, spending limits, and agent certification dey inside the wider direction of the project.
By SongMarketCap
Alex Pestchanker show Agentic Multipass for Midnight LIVE, as e introduce one prototype to verify identity and authority of AI agents. The project dey use Midnight privacy technology to support credentials wey agents fit present when dem dey interact with other systems. Pestchanker describe the application as minimum viable product wey connect to the 1AM wallet, with credential issuance and one centralized registry for verification.
Agentic Multipass Define Six Elements of Agent Authority
The project dey face one problem wey fit show when AI agent get access to data, fit use tools, or fit execute transactions for person or organization. According to Pestchanker, prompts, API keys, and policies fit tell agent wetin to do, but dem no by themselves give another party independent and verifiable proof of who authorize the action. Agentic Multipass dey aim to give agents way to present information about their identity and authority to other agents or systems.
Pestchanker proposed framework identify six elements: the agent identity, the person or organization wey dey control am, im mandate, im capabilities, im limits, and the current status of im authority. Mandate dey describe the task or intention wey dem assign to the agent, while capabilities and limits dey define the tools wey e fit use and restrictions like spending thresholds. Status dey show whether authorization still valid or dem don revoke am. Together, these elements dey connect agent activity with the instructions and permissions wey im owner supply.
How Midnight Support Private Agent Credentials
For the model wey dem present for Midnight LIVE, person go grant authority to agent, and the agent fit then interact with the platform through Model Context Protocol, or MCP. The protocol dey connect AI applications with external tools and services. Agent fit present decentralized identifier and verifiable credential to another party, using design wey align with World Wide Web Consortium standards. Pestchanker explain say zero-knowledge technology go allow selected claims to dey verified without disclosing all the underlying information, like the identity of the person or organization wey dey behind the agent.
The project public repository describe research implementation with 1AM wallet connection on Midnight Preprod, credential issuance, identity status, and proof-related functionality. E identify dedicated credentials and proofs for mandates, capabilities, and limits as extensions to the current foundations. The repository still talk say the implementation na for experimentation and e never strong reach production.
[NEWSBREAK]
Midnight Passport and Agent Certification Plans
During the discussion, Charles Hoskinson ask whether Pestchanker don talk with the Midnight Passport team. Pestchanker reply say e bin want use Passport since im early work for Build Club, but e no ready that time. E plan to integrate am into Agentic Multipass and e describe the current implementation as proof of concept. Hoskinson still connect the discussion to insurance and to Midnight City proposed marketplace for agent skills.
Pestchanker outline potential commercial services, including identity plans, credentials, verification APIs, and certification model. Under the proposed model, agents fit dey tested against standards for particular field and receive credential if dem pass. E suggest say certification fit help document the steps wey owner don take to control agent, while e still acknowledge say questions about who go take responsibility for agent behavior never get final answer. Im next proposed identity step na to replace the current proof-of-concept approach with Midnight Passport.