Join our workshop with @AskVenice tomorrow to learn how to build a wallet-aware AI assistant that turns natural language into safe, reviewable onchain actions.
📅 Wednesday, June 3
⏰ 2:00 PM ET
Live on X.
spent this stretch wiring Conduit onto @1shotapi's permissionless relayer, and seeing it click was the best part:
an AI agent paid for a service and covered its own gas in USDC- no ETH anywhere, no relayer infra to babysit.
Conduit now settles through the @1shotapi Permissionless Relayer. An agent can pay for a service and pay the gas in USDC, no relayer to run, no pre-funding.
How it works under the hood:
An agent hits a 402, and Conduit (our custom x402 facilitator for the erc7710 settlement method) builds the redemption. Because 1Shot recoups gas in stablecoin, each payment carries two delegations merged into one on-chain batch:
→ a bounded fee delegation- pays 1Shot's collector, capped, floored at the live quote
→ an intent-bound work delegation- our X402ReceiptEnforcer locks it to one recipient, one amount, one token, one request
So even the gas payment is bound. A compromised agent can't redirect either leg.
The user's account is upgraded to a @MetaMaskDev Smart Account via EIP-7702 - bundled into the same transaction the relayer submits. One tx: account upgrade + the payment, gas in USDC.
Settlement status comes from @1shotapi's Ed25519-signed webhooks, verified against their JWKS - then forwarded to integrators as clean events.
Build on Conduit, register a webhook, and you never touch the relayer, the chain, or the crypto.
Verified on Base Sepolia: the settlement tx is submitted by @1shotapi's relayer, gas paid in USDC. Mainnet next.
Built on @MetaMaskDev Smart Accounts + @1shotapi.
#x402 #erc7710 #eip7702 #erc7715 #agenteconomy #solidity #dev #metamask
Conduit now settles through the @1shotapi Permissionless Relayer. An agent can pay for a service and pay the gas in USDC, no relayer to run, no pre-funding.
How it works under the hood:
An agent hits a 402, and Conduit (our custom x402 facilitator for the erc7710 settlement method) builds the redemption. Because 1Shot recoups gas in stablecoin, each payment carries two delegations merged into one on-chain batch:
→ a bounded fee delegation- pays 1Shot's collector, capped, floored at the live quote
→ an intent-bound work delegation- our X402ReceiptEnforcer locks it to one recipient, one amount, one token, one request
So even the gas payment is bound. A compromised agent can't redirect either leg.
The user's account is upgraded to a @MetaMaskDev Smart Account via EIP-7702 - bundled into the same transaction the relayer submits. One tx: account upgrade + the payment, gas in USDC.
Settlement status comes from @1shotapi's Ed25519-signed webhooks, verified against their JWKS - then forwarded to integrators as clean events.
Build on Conduit, register a webhook, and you never touch the relayer, the chain, or the crypto.
Verified on Base Sepolia: the settlement tx is submitted by @1shotapi's relayer, gas paid in USDC. Mainnet next.
Built on @MetaMaskDev Smart Accounts + @1shotapi.
#x402 #erc7710 #eip7702 #erc7715 #agenteconomy #solidity #dev #metamask
@ConduitProtocol@MetaMaskDev Building @ConduitProtocol has been one of the most fun learning experiences of this @MetaMaskDev Cook-Off. Lots of late-night debugging, workshops, and experimentation turned into something we're genuinely excited about.
This @MetaMaskDev x @1shotapi hackathon has been such a fun builder experience and excited to ship to production.
Been learning a lot while building @ConduitProtocol 👀
The @MetaMask Smart Accounts Kit hackathon w/ @1ShotAPI and @AskVenice is open until June 15th.
Build with MetaMask Smart Accounts or Advanced Permissions to win up to $16k 🦊
Been deep in the @MetaMaskDev Smart Accounts + @1shotapi workshops, building @ConduitProtocol and testing different stuffs
Got some flows working end-to-end
email login → EIP-7702 smart account → an AI agent with a budget it physically cannot misuse, even if it's hijacked
We’ve been sitting in the @MetaMaskDev live workshops, taking notes on EIP-7702, the Delegation Framework, x402, and gas-abstracted relaying.
Huge insights from @TtheBC01, @UXlyChar, @ayushbherwani, and @francescoswiss.
This short demo does all of this in ONE transaction:
• embedded wallet (email login)
• EIP-7702 upgrades it into a MetaMask Smart Account
• a coordinator agent gets a scoped, revocable budget (@MetaMask Delegation Framework)
• it redelegates a narrow permission slice to a task agent for payment execution
Today, it’s all running end-to-end inside Conduit.
Conduit is a custom x402 facilitator for ERC-7710- x402’s newest and least-travelled settlement path.
On top of that, we built and deployed X402ReceiptEnforcer: an on-chain caveat that binds every payment to one exact request- recipient, amount, token, and intent- fixed before the agent ever runs.
So when the agent pays an x402 endpoint:
• Conduit verifies the request
• settles it through our relayer
• and bundles everything into a single EIP-7702 transaction:
- the account upgrade
- the bound payment
- and an on-chain receipt
all together.
Next step: routing redemption through the @1shotapi Permissionless Relayer and running Conduit’s facilitator on top of @1shotapi public relayer infrastructure.
From workshop notes → to a working agent payment rail.
@0xjordy@McOso_
#x402 #metamask #aiagent #1shotapi
We’ve been sitting in the @MetaMaskDev live workshops, taking notes on EIP-7702, the Delegation Framework, x402, and gas-abstracted relaying.
Huge insights from @TtheBC01, @UXlyChar, @ayushbherwani, and @francescoswiss.
This short demo does all of this in ONE transaction:
• embedded wallet (email login)
• EIP-7702 upgrades it into a MetaMask Smart Account
• a coordinator agent gets a scoped, revocable budget (@MetaMask Delegation Framework)
• it redelegates a narrow permission slice to a task agent for payment execution
Today, it’s all running end-to-end inside Conduit.
Conduit is a custom x402 facilitator for ERC-7710- x402’s newest and least-travelled settlement path.
On top of that, we built and deployed X402ReceiptEnforcer: an on-chain caveat that binds every payment to one exact request- recipient, amount, token, and intent- fixed before the agent ever runs.
So when the agent pays an x402 endpoint:
• Conduit verifies the request
• settles it through our relayer
• and bundles everything into a single EIP-7702 transaction:
- the account upgrade
- the bound payment
- and an on-chain receipt
all together.
Next step: routing redemption through the @1shotapi Permissionless Relayer and running Conduit’s facilitator on top of @1shotapi public relayer infrastructure.
From workshop notes → to a working agent payment rail.
@0xjordy@McOso_
#x402 #metamask #aiagent #1shotapi
Join us tomorrow for a live workshop on building recurring payments with x402. 🦊
Together, we'll learn how to:
- Create seamless payment experiences
- Automate transactions
- Build next-generation agentic payment flows
⏰ 11:00 AM ET
Live on X.
Alot of knowledge already been gained in this @1shotapi workshop
Will definitely apply it to our product we building for the @MetaMaskDev smart account and advanced permissions hackathon
Live in 30 minutes! ⏰
If you're participating in the Smart Accounts Kit Cook Off, you don't want to miss this @1shotapi workshop. https://t.co/WiDrOwDIru
We're planning to do a live stream coding session next Tuesday at 8:30am EST with @MetaMaskDev's @francescoswiss & @ayushbherwani focusing on how to leverage EIP-7710 in your apps in agents. Mark your calendars!
While building for the @MetaMaskDev + @1shotapi + @AskVenice hackathon over the weekend, we kept coming back to one question:
How do you safely give an AI agent access to your wallet?
Because today, giving an AI agent your wallet is basically a leap of faith.
You're trusting code that can be buggy, jailbroken, or quietly hijacked, with permission to spend your money.
We don't think that kind of trust should be required at all.
The usual answer is a spending cap:
“the agent can spend up to $X.”
But a cap doesn't stop a compromised agent from sending that entire $X to itself.
We are fixing this by locking every payment to one exact request before the agent even runs.
Built on @MetaMask Advanced Permissions:
The user signs a single scoped permission (ERC-7715).
A coordinator agent holds that root permission, then re-delegates smaller permissions to task agents, each one fused to a single purchase:
recipient, amount, token, all fixed on-chain.
Try to:
- pay the wrong address
- overspend
- replay a payment
→ the transaction reverts.
Not a wallet warning.
A hard on-chain failure.
And if anything ever feels suspicious, revoke the root permission once and every downstream agent instantly loses access.
@1shotapi handles settlement, sponsors gas in USDC, so users never need to touch ETH while hosting our own x402 7710 custom facilitator on the public relayer.
The result isn't a more powerful AI agent.
It's an agent that's finally safe to let loose, because betrayal isn't a risk you manage.
It's something the system makes impossible.
Built in the open with @MetaMaskDev + @1shotapi
#metamask #delegation #x402 #hackathon #solidity #ethereum
The interesting part of AI payments isn’t autonomy.
It’s constraint.
Conduit turns ERC-7710 permissions into enforceable payment rules:
→ one request
→ one scope
→ one bounded delegation chain
Built on @MetaMaskDev smart accounts with settlement via @1shotapi relayers.
Conduit Architecture👇
A custom x402 + erc7710 facilitator built on @MetaMaskDev smart accounts:
- advanced permissions (erc7715) authorize the payment
- a custom on-chain caveat binds it to one specific request
- @1shotapi's permissionless relayer settles it with gas in USDC