MolTrust is the trust infrastructure for the agentic economy.
As AI agents increasingly transact autonomously using stablecoins - via x402, Circle Gateway, Nanopayments, and A2A protocols - a fundamental question remains unanswered: which agent is allowed to pay what, under which constraints, and based on what track record?
MolTrust provides the cryptographic trust layer that sits above payment rails:
Standards & Regulation:
Developer Ecosystem:
MolTrust is operated by CryptoKRI GmbH, Zürich - a Swiss company building regulated trust infrastructure for the AI agent economy.
Before an AI agent initiates a stablecoin transfer via Gateway, x402, or Nanopayments, MolTrust validates the agent's identity, authorization envelope, and behavioral trust score through a requireScore() gate. This helps prevent unauthorized, sybil-controlled, or out-of-policy payments at the infrastructure layer - not after settlement. Enterprises deploying autonomous agents gain enforceable spending controls without modifying their payment flows.
MolTrust issues W3C-standard Decentralized Identifiers (did:moltrust:*) that give AI agents a single cryptographic identity usable across Base, Ethereum, Solana, and off-chain environments. These DIDs reference and extend onchain identity standards like ERC-8004, providing the portability required for agents that transact with digital dollars across multiple blockchains or bridge between chain-native and API-based services.
Every agent-to-agent or agent-to-service interaction can be recorded as an Interaction Proof Record (IPR): Merkle-batched, cryptographically signed by both parties, and anchored on Base L2. Regulated enterprises deploying stablecoin-paying agents gain a tamper-evident audit trail aligned with MiCA, the EU AI Act, and Singapore's IMDA Model AI Governance Framework - without building their own compliance infrastructure.
Replace implicit trust with signed, time-bounded mandates. The Agent Authorization Envelope (AAE) specifies what an agent may do (MANDATE), under what constraints (CONSTRAINTS), and for how long (VALIDITY) - all enforceable at the payment layer. This prevents runaway spending, scope drift, and unauthorized access in autonomous workflows, whether the agent is making a single payment or running a continuous agentic commerce loop.
This site contains content and information, including links to other sites and resources, that was prepared by third parties ("Third Party Content") who are not affiliated with Circle or any of its affiliates (collectively "Circle"). Circle makes no representations on the accuracy, suitability, or validity of Third Party Content. As such, Circle is neither responsible nor liable for any Third Party Content, including any errors, omissions, or delays, or for any actions taken in reliance upon any Thirds Party Content. Reference to any specific company, product, service, or website of any third party does not constitute an implied or express endorsement, recommendation, favoring or validation by Circle. All content provided is for educational and informational purposes only. Circle shall not be liable for any damage or loss relating to use of, or reliance upon, the Third Party Content.