--- schema: 1 type: video title: >- Why Your AI Agent Needs a Wallet: USDC and Nanopayments — Harshal Bhangale, Circle description: >- Harshal Bhangale gave two identical agents the same job: plan a trip to the World Cup final, covering flights, hotels, resale ticket prices and what people said about getting to the stadium, then email him the summary and call him about it. One had a funded wallet. The other did not. The agent without one drafted the email into his inbox and could not send it, then admitted on screen that it had no way to place a call. The agent with one paid for the data it needed, sent the mail, and rang him on stage, where it also answered a follow up question about reaching the stadium from his hotel. Circle issues USDC, and Bhangale's answer for why a stablecoin company belongs at this conference is that paying is where agents stall. The economics are the whole argument. Agents consume in fractional amounts at high frequency, and a card fee near 3% cannot sit on top of a one cent call, which is exactly the size sellers are moving toward now that they can meter a slice of their data instead of selling a human a subscription. He cites roughly 24 million dollars transacted against paid API endpoints over x402 in thirty days, almost all settled in USDC. Blockchains alone do not fix it either. Gas exists to stop spam, but gas on a microtransaction swamps the transaction, and shared block space makes latency unpredictable. Circle's answer is to keep settlement off the chain: funds are deposited into a smart contract, the agent signs authorizations cryptographically, and the seller relays them for confirmation in a few hundred milliseconds. The wallet enforces the spending cap, not a human. Speaker info: - https://www.linkedin.com/in/harshaldbhangale Timestamps: 0:00 - Why a stablecoin company is at an AI conference 1:05 - Where agents actually stall 1:58 - From prompts to workflows to agents that pay 2:53 - x402 in one paragraph 4:48 - Why card fees break on a one cent transaction 5:41 - Demo: two agents, one with a wallet 9:34 - Guardrails in the wallet instead of human approval 11:53 - The agent that drafts an email it cannot send 14:19 - The phone call, live on stage 16:16 - Why gas fees and shared block space bite 17:10 - Nanopayments, and settlement in milliseconds --- Watch along with the corrected transcript, summary, timestamps and resources on this talk's official AIE page: https://ai.engineer/talks/xKzU_3riL6s-youtube-2b2f94fe3ee6849b4c02 Join our upcoming AI Engineer conferences (see https://ai.engineer landing page): - AIEi Shanghai, November 5–6 — the first for meeting top Chinese labs and engineers - AIE CODE in SF, November 10–12 — the top AI Coding conference returns - AIEi Sydney, December 7–8 — the first AIEi run alongside NeurIPS 2026 in Sydney --- canonical: >- https://liquidgold.cc/channel/aidotengineer/explore/video/why-your-ai-agent-needs-a-wallet-usdc-and-nanopayme-00f8753bb0e1 markdown: >- https://liquidgold.cc/channel/aidotengineer/video/why-your-ai-agent-needs-a-wallet-usdc-and-nanopayme-00f8753bb0e1.md llms: null parent: 'https://liquidgold.cc/channel/aidotengineer.md' channel: aidotengineer updated: '2026-10-24T04:11:38.746Z' language: null children: [] videoId: xKzU_3riL6s durationSeconds: 1252 publishedAt: '2026-09-01T17:30:10.000Z' searchChunks: - ordinal: 0 text: null startSeconds: 24 endSeconds: 68 watch: 'https://liquidgold.cc/watch/xKzU_3riL6s?t=24' heldReason: rights - ordinal: 1 text: null startSeconds: 68 endSeconds: 81 watch: 'https://liquidgold.cc/watch/xKzU_3riL6s?t=68' heldReason: rights - ordinal: 2 text: null startSeconds: 139 endSeconds: 182 watch: 'https://liquidgold.cc/watch/xKzU_3riL6s?t=139' heldReason: rights - ordinal: 3 text: null startSeconds: 182 endSeconds: 194 watch: 'https://liquidgold.cc/watch/xKzU_3riL6s?t=182' heldReason: rights - ordinal: 4 text: null startSeconds: 194 endSeconds: 296 watch: 'https://liquidgold.cc/watch/xKzU_3riL6s?t=194' heldReason: rights - ordinal: 5 text: null startSeconds: 296 endSeconds: 308 watch: 'https://liquidgold.cc/watch/xKzU_3riL6s?t=296' heldReason: rights - ordinal: 6 text: null startSeconds: 308 endSeconds: 341 watch: 'https://liquidgold.cc/watch/xKzU_3riL6s?t=308' heldReason: rights - ordinal: 7 text: null startSeconds: 578 endSeconds: 589 watch: 'https://liquidgold.cc/watch/xKzU_3riL6s?t=578' heldReason: rights - ordinal: 8 text: null startSeconds: 743 endSeconds: 859 watch: 'https://liquidgold.cc/watch/xKzU_3riL6s?t=743' heldReason: rights - ordinal: 9 text: null startSeconds: 981 endSeconds: 992 watch: 'https://liquidgold.cc/watch/xKzU_3riL6s?t=981' heldReason: rights - ordinal: 10 text: null startSeconds: 992 endSeconds: 1037 watch: 'https://liquidgold.cc/watch/xKzU_3riL6s?t=992' heldReason: rights - ordinal: 11 text: null startSeconds: 1048 endSeconds: 1252 watch: 'https://liquidgold.cc/watch/xKzU_3riL6s?t=1048' heldReason: rights - ordinal: 12 text: null startSeconds: 1048 endSeconds: 1252 watch: 'https://liquidgold.cc/watch/xKzU_3riL6s?t=1048' heldReason: rights - ordinal: 13 text: null startSeconds: 81 endSeconds: 127 watch: 'https://liquidgold.cc/watch/xKzU_3riL6s?t=81' heldReason: rights --- # Why Your AI Agent Needs a Wallet: USDC and Nanopayments — Harshal Bhangale, Circle Harshal Bhangale gave two identical agents the same job: plan a trip to the World Cup final, covering flights, hotels, resale ticket prices and what people said about getting to the stadium, then email him the summary and call him about it. One had a funded wallet. The other did not. The agent without one drafted the email into his inbox and could not send it, then admitted on screen that it had no way to place a call. The agent with one paid for the data it needed, sent the mail, and rang him on stage, where it also answered a follow up question about reaching the stadium from his hotel. Circle issues USDC, and Bhangale's answer for why a stablecoin company belongs at this conference is that paying is where agents stall. The economics are the whole argument. Agents consume in fractional amounts at high frequency, and a card fee near 3% cannot sit on top of a one cent call, which is exactly the size sellers are moving toward now that they can meter a slice of their data instead of selling a human a subscription. He cites roughly 24 million dollars transacted against paid API endpoints over x402 in thirty days, almost all settled in USDC. Blockchains alone do not fix it either. Gas exists to stop spam, but gas on a microtransaction swamps the transaction, and shared block space makes latency unpredictable. Circle's answer is to keep settlement off the chain: funds are deposited into a smart contract, the agent signs authorizations cryptographically, and the seller relays them for confirmation in a few hundred milliseconds. The wallet enforces the spending cap, not a human. Speaker info: - https://www.linkedin.com/in/harshaldbhangale Timestamps: 0:00 - Why a stablecoin company is at an AI conference 1:05 - Where agents actually stall 1:58 - From prompts to workflows to agents that pay 2:53 - x402 in one paragraph 4:48 - Why card fees break on a one cent transaction 5:41 - Demo: two agents, one with a wallet 9:34 - Guardrails in the wallet instead of human approval 11:53 - The agent that drafts an email it cannot send 14:19 - The phone call, live on stage 16:16 - Why gas fees and shared block space bite 17:10 - Nanopayments, and settlement in milliseconds --- Watch along with the corrected transcript, summary, timestamps and resources on this talk's official AIE page: https://ai.engineer/talks/xKzU_3riL6s-youtube-2b2f94fe3ee6849b4c02 Join our upcoming AI Engineer conferences (see https://ai.engineer landing page): - AIEi Shanghai, November 5–6 — the first for meeting top Chinese labs and engineers - AIE CODE in SF, November 10–12 — the top AI Coding conference returns - AIEi Sydney, December 7–8 — the first AIEi run alongside NeurIPS 2026 in Sydney --- Canonical: https://liquidgold.cc/channel/aidotengineer/explore/video/why-your-ai-agent-needs-a-wallet-usdc-and-nanopayme-00f8753bb0e1 · Channel: [AI Engineer](https://liquidgold.cc/channel/aidotengineer.md) > Search chunk text is held until public-source provenance is verified. ## Document chunks > Missing: no stored document chunks are available.