<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>aaif on Alan Blount | Member of Technical Staff / TPM at Google</title><link>http://zeroasterisk.com/tags/aaif/</link><description>Recent content in aaif on Alan Blount | Member of Technical Staff / TPM at Google</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 20 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://zeroasterisk.com/tags/aaif/index.xml" rel="self" type="application/rss+xml"/><item><title>Where A2A Fits in the Open Agent Ecosystem</title><link>http://zeroasterisk.com/2026/08/where-a2a-fits-in-the-open-agent-ecosystem/</link><pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate><guid>http://zeroasterisk.com/2026/08/where-a2a-fits-in-the-open-agent-ecosystem/</guid><description>Where A2A Fits in the Open Agent Ecosystem Co-authored with Angie Jones on the Agentic AI Foundation blog, August 20, 2026
A2A defines how one independent agent works with another: negotiating scope, keeping a task going over time, asking for more input, and streaming intermediate updates, while the remote agent decides how to do the work behind its endpoint. Commerce is a concrete example. UCP defines an A2A binding for checkout, and AP2 carries verifiable payment authorization inside the same interaction.</description></item></channel></rss>