--- schema: 1 type: video title: >- When AI Agents Pay and Sellers Monetize: Building x402 Apps on AWS — Anil Nadiminti, AWS description: >- Card rails put a floor under every transaction: a 25 cent minimum with a percentage on top. Anil Nadiminti's point is that when an agent pays a tenth of a cent for a single API call, that floor costs roughly 250 times the thing being bought, which is why the subscription model cannot simply be pointed at agents. Meanwhile the traffic has already turned over. He puts bot traffic past human traffic on the open web, with the large majority of it coming from AI agents, leaving sellers to choose between blocking it, which forfeits discovery, citations and licensing revenue, or absorbing it, which means carrying the infrastructure cost and losing attribution. His framing for the way out is that the human moves from in the loop to out of it, and the payment becomes the credential. The AWS pieces land on both sides of that. On the buy side, AgentCore Payments gives an agent a wallet, a connector layer built to be protocol agnostic, and per session spending limits with an expiry. Two design choices carry the security argument. Imported wallet keys sit in a KMS backed store the agent cannot read, and the payment path is decoupled from the agent loop entirely, on the reasoning that skills and inputs can be poisoned and payment has no business running on a nondeterministic path. On the sell side, bot detection at the edge classifies over 650 bot types, verifies them by signature and infers whether a request is for training or for search, which lets a publisher price by path, by whether the bot belongs to a known partner, and by intent, without touching the origin. Speaker info: - https://x.com/super_intel_bot - https://www.linkedin.com/in/nadiminti Timestamps: 0:00 - A paywall built for humans, and traffic that is not 1:08 - Bot traffic passes human traffic 2:58 - The seller's dilemma: block bots or absorb them 6:36 - Why a 25 cent floor kills a microcent payment 7:31 - The x402 flow, end to end 9:23 - AgentCore Payments, and setting spend limits 12:12 - Why the agent never holds the private keys 13:05 - Decoupling payments from a poisonable agent loop 14:57 - Bot detection, and reading intent 15:51 - Monetizing AI traffic at the edge 17:42 - Pricing by path, by identity, by intent 18:38 - What the volume looks like today --- Watch along with the corrected transcript, summary, timestamps and resources on this talk's official AIE page: https://ai.engineer/talks/qTZirYu9pr0-youtube-8b0be9cbd99450da9cf4 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/when-ai-agents-pay-and-sellers-monetize-building-x4-3f169c652171 markdown: >- https://liquidgold.cc/channel/aidotengineer/video/when-ai-agents-pay-and-sellers-monetize-building-x4-3f169c652171.md llms: null parent: 'https://liquidgold.cc/channel/aidotengineer.md' channel: aidotengineer updated: '2026-10-24T04:11:33.532Z' language: null children: [] videoId: qTZirYu9pr0 durationSeconds: 1241 publishedAt: '2026-09-01T18:00:14.000Z' searchChunks: - ordinal: 0 text: null startSeconds: 68 endSeconds: 78 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=68' heldReason: rights - ordinal: 1 text: null startSeconds: 78 endSeconds: 189 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=78' heldReason: rights - ordinal: 2 text: null startSeconds: 78 endSeconds: 189 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=78' heldReason: rights - ordinal: 3 text: null startSeconds: 189 endSeconds: 200 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=189' heldReason: rights - ordinal: 4 text: null startSeconds: 200 endSeconds: 400 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=200' heldReason: rights - ordinal: 5 text: null startSeconds: 200 endSeconds: 400 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=200' heldReason: rights - ordinal: 6 text: null startSeconds: 200 endSeconds: 400 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=200' heldReason: rights - ordinal: 7 text: null startSeconds: 400 endSeconds: 410 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=400' heldReason: rights - ordinal: 8 text: null startSeconds: 410 endSeconds: 453 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=410' heldReason: rights - ordinal: 9 text: null startSeconds: 410 endSeconds: 453 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=410' heldReason: rights - ordinal: 10 text: null startSeconds: 453 endSeconds: 463 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=453' heldReason: rights - ordinal: 11 text: null startSeconds: 463 endSeconds: 566 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=463' heldReason: rights - ordinal: 12 text: null startSeconds: 566 endSeconds: 578 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=566' heldReason: rights - ordinal: 13 text: null startSeconds: 578 endSeconds: 736 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=578' heldReason: rights - ordinal: 14 text: null startSeconds: 578 endSeconds: 736 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=578' heldReason: rights - ordinal: 15 text: null startSeconds: 736 endSeconds: 748 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=736' heldReason: rights - ordinal: 16 text: null startSeconds: 748 endSeconds: 796 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=748' heldReason: rights - ordinal: 17 text: null startSeconds: 796 endSeconds: 808 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=796' heldReason: rights - ordinal: 18 text: null startSeconds: 808 endSeconds: 897 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=808' heldReason: rights - ordinal: 19 text: null startSeconds: 897 endSeconds: 908 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=897' heldReason: rights - ordinal: 20 text: null startSeconds: 897 endSeconds: 908 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=897' heldReason: rights - ordinal: 21 text: null startSeconds: 908 endSeconds: 951 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=908' heldReason: rights - ordinal: 22 text: null startSeconds: 951 endSeconds: 961 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=951' heldReason: rights - ordinal: 23 text: null startSeconds: 961 endSeconds: 1070 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=961' heldReason: rights - ordinal: 24 text: null startSeconds: 1070 endSeconds: 1081 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=1070' heldReason: rights - ordinal: 25 text: null startSeconds: 1081 endSeconds: 1125 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=1081' heldReason: rights - ordinal: 26 text: null startSeconds: 1125 endSeconds: 1135 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=1125' heldReason: rights - ordinal: 27 text: null startSeconds: 1135 endSeconds: 1241 watch: 'https://liquidgold.cc/watch/qTZirYu9pr0?t=1135' heldReason: rights --- # When AI Agents Pay and Sellers Monetize: Building x402 Apps on AWS — Anil Nadiminti, AWS Card rails put a floor under every transaction: a 25 cent minimum with a percentage on top. Anil Nadiminti's point is that when an agent pays a tenth of a cent for a single API call, that floor costs roughly 250 times the thing being bought, which is why the subscription model cannot simply be pointed at agents. Meanwhile the traffic has already turned over. He puts bot traffic past human traffic on the open web, with the large majority of it coming from AI agents, leaving sellers to choose between blocking it, which forfeits discovery, citations and licensing revenue, or absorbing it, which means carrying the infrastructure cost and losing attribution. His framing for the way out is that the human moves from in the loop to out of it, and the payment becomes the credential. The AWS pieces land on both sides of that. On the buy side, AgentCore Payments gives an agent a wallet, a connector layer built to be protocol agnostic, and per session spending limits with an expiry. Two design choices carry the security argument. Imported wallet keys sit in a KMS backed store the agent cannot read, and the payment path is decoupled from the agent loop entirely, on the reasoning that skills and inputs can be poisoned and payment has no business running on a nondeterministic path. On the sell side, bot detection at the edge classifies over 650 bot types, verifies them by signature and infers whether a request is for training or for search, which lets a publisher price by path, by whether the bot belongs to a known partner, and by intent, without touching the origin. Speaker info: - https://x.com/super_intel_bot - https://www.linkedin.com/in/nadiminti Timestamps: 0:00 - A paywall built for humans, and traffic that is not 1:08 - Bot traffic passes human traffic 2:58 - The seller's dilemma: block bots or absorb them 6:36 - Why a 25 cent floor kills a microcent payment 7:31 - The x402 flow, end to end 9:23 - AgentCore Payments, and setting spend limits 12:12 - Why the agent never holds the private keys 13:05 - Decoupling payments from a poisonable agent loop 14:57 - Bot detection, and reading intent 15:51 - Monetizing AI traffic at the edge 17:42 - Pricing by path, by identity, by intent 18:38 - What the volume looks like today --- Watch along with the corrected transcript, summary, timestamps and resources on this talk's official AIE page: https://ai.engineer/talks/qTZirYu9pr0-youtube-8b0be9cbd99450da9cf4 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/when-ai-agents-pay-and-sellers-monetize-building-x4-3f169c652171 · 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.