Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

On XMTP, AI agents can act as payment concierges. In this demo, devs can use Coinbase Developer Platform🛡️ & ens.eth to easily build messaging-based agents that: - let users load USDC onto wallets they control - send USDC as payments, right from chat ...all gasless & free on Base. (1/5)

38,664 Aufrufe • vor 1 Jahr •via X (Twitter)

10 Kommentare

Profilbild von XMTP
XMTPvor 1 Jahr

Let's go over how this works... With XMTP, devs can leverage MessageKit ( to build agents to use in highly secure, private XMTP messaging clients like @CoinbaseWallet & @family. This means secure, private agents for messaging, out of the box. (2/5)

Profilbild von XMTP
XMTPvor 1 Jahr

With @CoinbaseDev SDK devs can create programmable wallets that can perform gassless transactions on @base and let agents use these USDC-funded wallets-- all without any ETH required. This reduces the UX complexities of crypto, helping to scale agents to non-crypto users. (3/5)

Profilbild von XMTP
XMTPvor 1 Jahr

Because the agent identity (paymentagent.eth) is using @ensdomains, it's unspoofable on XMTP. Users can trust + prove they are interacting with the correct agent + wallet. This makes onchain identities even more valuable, as they can represent app + agent utility in XMTP. (4/5)

Profilbild von XMTP
XMTPvor 1 Jahr

Want to get started building agents, with verified identities that can make USDC payments on @CoinbaseWallet? Here are the links to the repos used. - - (5/5)

Profilbild von Raihan Khan #Diversion2k25
Raihan Khan #Diversion2k25vor 1 Jahr

@CoinbaseDev @ensdomains @base who wants to see a @circle integration with @xmtp_ message-kit 👀

Profilbild von seanwbren.eth
seanwbren.ethvor 1 Jahr

@CoinbaseDev @ensdomains @base Apple Pay could be used here to load the 10 usdc right?

Profilbild von chinmay.eth
chinmay.ethvor 1 Jahr

@CoinbaseDev @ensdomains @base is this compatible with ??

Profilbild von Nathan
Nathanvor 1 Jahr

@CoinbaseDev @ensdomains @base This feels like the next big thing. Based Agents is turning AI agents into something useful with token economies and the ability to evolve. It’s like the future of digital interaction is unfolding right here. Follow and join the revolution NOW!

Profilbild von Luka Isailovic
Luka Isailovicvor 1 Jahr

@CoinbaseDev @ensdomains @base You don’t need the load funds step anymore

Profilbild von gmworld.eth | james.base.eth
gmworld.eth | james.base.ethvor 1 Jahr

@CoinbaseDev @ensdomains @base Ai readable naming system 🔥

Ähnliche Videos

x402 made payments native to HTTP. I made USDC payments native to sound waves ✨ Not as a gimmick. As a proof. 1/ The setup: Coinbase Developer Platform🛡️'s x402 protocol embeds payments into HTTP. It's brilliant. But I started wondering, if we can pay over HTTP, what else can we use to pay? Spoiler: anything that supports 138 bytes 2/ The realization: x402 is built on EIP-3009 - a 2020 standard that lets you sign payment authorizations offline. Someone else submits it on-chain. The signature just needs to get from A to B. HTTP is one way. Sound is another. 3/ What I built: x402hz: two devices negotiate a payment through 2400Hz audio tones. - Seller beeps "pay me $0.001 USDC" (30 bytes) - Buyer's device decodes, signs the EIP-712 for the transferWithAuthorization locally, beeps back (108 bytes) - Seller settles on-chain Total: 36 seconds of beautiful noise. 4/ The bigger point: If payments can travel over sound, they can travel over: - QR codes - NFC - Bluetooth - Light pulses - Anything that carries 138 bytes The payment primitive is transport-agnostic. x402 picked HTTP. The next protocol might pick something weirder. 5/ What this proves: EIP-3009 separates three things: - Authorization (offline, cryptographic) - Transport (literally anything) - Settlement (on-chain) x402 nailed #1 and #3. x402hz proves #2 is wide open. 6/ Credit: Huge thanks to the Coinbase Developer Platform🛡️ x402 team for building the protocol. I just... took it off-road. 7/ Next steps Code is open source. Go make payments, travel over something ridiculous (repo in the comments). 138bytes. That's all you need.

Vitto Rivabella

40,536 Aufrufe • vor 9 Monaten

I’ve been watching x402 since Coinbase 🛡️ launched it in May 2025. I did a quick research pass. Here’s the snapshot ↓ Early integrations: • CoinGecko: x402 pay-per-use access for agents (shared by Coinbase Developer Platform🛡️). • Vercel: x402 AI starter template (x402 + modern AI stack demo). • Firecrawl: x402-powered search endpoint (pay per request). • Concordium: x402 + native age verification for agent payments. • Multiversᕽ: “agentic payments” built around x402 support. • AltLayer: building an “x402 Suite” for value exchange between agents. • Solana claims x402 has processed 35M+ transactions and $10M+ volume since launch. TL;DR x402 turns HTTP 402 “Payment Required” into a payment flow. A server returns a price for a request. The client pays in stables like USDC. Then the server returns the result. → Coinbase launched x402 via Coinbase Developer Platform (May 6, 2025). → Coinbase + Cloudflare announced the x402 Foundation (Sep 23, 2025). → Cloudflare added x402 support into its Agents SDK + MCP servers. Why? - AI agents need a clean way to pay for tools. - Data, compute, APIs, services. - No accounts, cards, or subscription screens. x402 is trying to make pay-per-request feel normal. Use cases that already make sense → Paid APIs Pay per call instead of subscriptions. → AI tool calls Pay per query, per inference, per task. → Agent-to-agent payments Software paying software automatically. → Micropaywalls Pay for one endpoint, one action, one piece of content. If this takes off, stablecoins stop being a story. They become how apps and AI agents pay for things online.

Stacy Muur

12,212 Aufrufe • vor 7 Monaten