Conduit Protocol

When AI agents start paying each other, what stops a compromised one from draining your wallet? Conduit makes every agent-to-agent payment cryptographically bound to a delivered service. Bad agent can't take your money. It can only spend it on what you asked for. The agent economy is real now. x402 has processed 100M+ payments. Agents are calling paid APIs, hiring sub-agents, settling in stablecoins. But every existing approach has the same flaw: once you delegate spending power to an agent, you're trusting it not to misbehave. Conduit is a caveat enforcer for the MetaMask Delegation Framework. Every time an agent tries to spend your money, it must present proof, an x402 payment receipt, that a real service was delivered for the exact amount, to the exact recipient. No receipt, no transfer. Agents can also re-delegate, hire sub-agents with scoped sub-budgets. Conduit's safety property survives every hop in the chain. One agent can spawn an entire workflow of specialists, each paid per-call. Your original permissions still hold at the root. Built for the @MetaMaskDev × @1shotapi hackathon at @HackQuest_ We just getting started. #metamask #metamaskdev #smartaccount #x402 #A2A #buildinpublic #hackathon #metamasksmartaccount #AIAgent #agent #developer #ethereum #eth #ethbase #solidity #dev #1shotapi #api

AI agents that pay autonomously, with both user safety rules and product rules enforced on-chain. That's what x402 + erc7710 unlocks. Conduit combines @MetaMaskDev advanced permissions with @1shotapi's permissionless relayer to make it real and fully open source conduit.hashnode.dev/conduit-buildi… #x402 #aiagent #metamaskdevs #metamask #metamasksmartaccount #relayer #solidity #ethereum #base #buildinpublic #hackathon

Building Conduit for this, the safety layer for the agent economy. When agents pay each other, what stops a compromised one from draining your wallet? Conduit binds every payment to a delivered service via a custom caveat enforcer on @MetaMask Smart Accounts. Build logs rolling out soon @MetaMaskDev

We were ~1 hour away from publishing an article claiming nobody implements x402’s third transfer method (erc7710). We were wrong. A last-minute correction from @ayushbherwani during the @MetaMaskDev hackathon workshop led us to a real facilitator implementation from @MetaMask, not listed in the x402 ecosystem indexes and not on our candidate map. That changed the conclusion completely, though Conduit will build its own x402 7710 facilitator on top of @1shotapi public relayer. The bigger lesson wasn’t technical. It was methodological: Ecosystem indexes are incomplete. Reference repos are incomplete. “Who actually ships this?” is not something you learn by reading docs alone. Real infra research means probing systems, following dead ends, and talking directly to the people building the stack. Full receipt, every dead lead, and the corrected facilitator landscape in the article below 👇 conduit.hashnode.dev/metamask-imple… #x402 #metamask #erc7710 #web3 #infrastructure #smartaccount #1shotapi #1shot #solidity #agent #a2a #ethereum #base

When AI agents start paying each other, what stops a compromised one from draining your wallet? Conduit makes every agent-to-agent payment cryptographically bound to a delivered service. Bad agent can't take your money. It can only spend it on what you asked for. The agent economy is real now. x402 has processed 100M+ payments. Agents are calling paid APIs, hiring sub-agents, settling in stablecoins. But every existing approach has the same flaw: once you delegate spending power to an agent, you're trusting it not to misbehave. Conduit is a caveat enforcer for the MetaMask Delegation Framework. Every time an agent tries to spend your money, it must present proof, an x402 payment receipt, that a real service was delivered for the exact amount, to the exact recipient. No receipt, no transfer. Agents can also re-delegate, hire sub-agents with scoped sub-budgets. Conduit's safety property survives every hop in the chain. One agent can spawn an entire workflow of specialists, each paid per-call. Your original permissions still hold at the root. Built for the @MetaMaskDev × @1shotapi hackathon at @HackQuest_ We just getting started. #metamask #metamaskdev #smartaccount #x402 #A2A #buildinpublic #hackathon #metamasksmartaccount #AIAgent #agent #developer #ethereum #eth #ethbase #solidity #dev #1shotapi #api

Join us on X in 1 hour to learn more about the @MetaMask Smart Accounts Kit hackathon w/ @1ShotAPI and @askvenice. 🦊

Found this great video from last year with @danfinlay talking about the vision for EIP-7710 and the design space it unlocks for onchain products. This was recorded before the explosion in agentic products, which we think is where delegated permissions really shine. youtube.com/watch?v=Twibpp…

@MetaMaskDev @MetaMask Thank you 🔥

@ConduitProtocol @MetaMask nice 🙌

@McOso_ @MetaMask Appreciate the response. I’ll document the build publicly as I go

@ConduitProtocol @MetaMask Can’t wait to see it!

@McOso_ The real unlock with 7710 isn’t single delegations, it’s chained redelegations, authority can pass agent-to-agent while original caveats still persist. Building a safety layer around that.

Calling all hackers! Now is a great time to build with 7710 permissions

Ready to shape the the future of Agentic AI? The @MetaMask Smart Accounts Kit Hackathon w/ @1ShotAPI and @askvenice is now live. 🦊 Build agentic experiences focused on permission sharing and UX for a shot at a $16K prize pool.

@1shotapi @MetaMaskDev Locked in and ready to ship 🔥🔥🔥

We're co-hosting the Dev Cook-off hackathon with @MetaMaskDev 🍳 $11,000 in prizes for builders pushing the limits of EIP-7710 smart accounts: → x402 + ERC-7710 payments → Autonomous agents → Multi-agent redelegation (A2A) → Gas abstraction with 1Shot Relayer No paymaster infra. No signup. Ship fast. Submissions close June 15. Full breakdown 👇

Fully locked in and ready to ship 🔥🔥

gm 🦊 devs The next @MetaMask hackathon drops soon. Stay tuned 👀