<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>A2a on Fresh/Brewed</title>
		<link>https://freshbrewed.science/tags/a2a/</link>
		<description>Recent content in A2a on Fresh/Brewed</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Tue, 06 Oct 2026 00:00:00 -0500</lastBuildDate>
		
			<atom:link href="https://freshbrewed.science/tags/a2a/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>A2A</title>
				<link>https://freshbrewed.science/2026/10/06/a2a.html</link>
				<pubDate>Tue, 06 Oct 2026 00:00:00 -0500</pubDate>
				<guid>https://freshbrewed.science/2026/10/06/a2a.html</guid>
				<description>&lt;p&gt;Ever since I heard about the &lt;a href=&#34;https://developers.googleblog.com/en/a2a-a-new-era-of-agent-interoperability/&#34;&gt;Agent to Agent (A2A) protocol&lt;/a&gt;, I&amp;rsquo;ve been curious what it was and how it might be useful.&lt;/p&gt;&#xA;&lt;p&gt;The general idea of A2A is that it&amp;rsquo;s a standard that Agentic workloads can leverage to discover and talk to each other using &amp;ldquo;cards&amp;rdquo; that advertise capabilities.&lt;/p&gt;&#xA;&lt;p&gt;We will look at two A2A examples, how they work and test them.  Then we&amp;rsquo;ll try and recreate them with python containerize servers with REST endpoints.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
