{"version":"1.0","type":"rich","provider_name":"Acast","provider_url":"https://acast.com","height":250,"width":700,"html":"<iframe src=\"https://embed.acast.com/$/69ab3b7c7036d739021982df/6a0b5bf9cdab12b21ca54a9a?\" frameBorder=\"0\" width=\"700\" height=\"250\"></iframe>","title":"Six protocols emerged. Three decide which agents survive.","description":"<p>What's really happening inside the agent protocol stack as Google I/O kicks off? The common story is that every new protocol is a must-have standard — but the reality is more complicated.</p><p><br></p><p>In this postcast, I share the inside scoop on the six agent protocols shaping how AI agents actually ship and how customers experience them:</p><ul><li>Why three protocols are becoming the real agent stack</li><li>How MCP, A2A, and AGUI map to core agent jobs</li><li>What separates a standard from a contested protocol</li><li>Where payment protocols collide with customer trust</li></ul><p><br></p><p>For builders and operators, the agentic substrate is a real lever on customer experience, but only if you stop chasing acronyms and start asking which protocols actually shape the workflow you're shipping.</p><p><br></p><p>Subscribe for daily AI strategy and news. For deeper playbooks and analysis: <a href=\"https://natesnewsletter.substack.com/\" rel=\"noopener noreferrer\" target=\"_blank\">https://natesnewsletter.substack.com/</a></p>","author_name":"Nate B. Jones"}