Matchwise is now using Google's A2A

Last month I published a Javascript/Typescript A2A SDK including client and service libraries. I'm a firm believer in dogfooding your own products, so last week I converted Matchwise to use the A2A libraries I have published.

A2A is a lower level protocol and doesn't support multi-tenancy (the ability of one agent to represent many different users) so a little glue was required:

• A2A sits below authentication, so I layered on top the Agentic Profile authentication library. This allowed the use of public key cryptography for universal authentication.
• A2A is not multi-tenant. The client authenticates, but the server is just "the server". For many services, the server can represent any of thousands of users (e.g. an email system, or text messaging). To solve this problem I added an "envelope" (stored in the metadata) for each A2A Message that indicates which user an A2A message is intended for.
• I revised the Agentic Profile schema to better align with A2A (e.g. message.content now supports Part[])

Overall, it was a fun conversion and allowed me to dig deep into how A2A works.

This also paves the way for me to create more demo agents in the Agentic Profile A2A SDK, which is the next step in opening up the Agentic Economy. My hope is agents can be quickly developed with the SDK and then added to the Matchwise (or any other) agent marketplace to provide individualized service. For example, if you don't like how well the Matchwise dating agent is working, you can up-level to a better performing one from the open market.

If you have any questions please connect with Mike Prince on LinkedIn.

Thanks!