TL;DR: FAF is on the A2A partners list — checked by Google's A2A partnerships lead against the IANA registration and a live Agent Card. Complementary. We do not replace the card.

Two dates

28 August 2026 — A2A joined the Agentic AI Foundation (AAIF), the neutral Linux Foundation home that already hosts MCP, goose and AGENTS.md. A2A moved under vendor-neutral governance.

31 August 2026 — FAF was added to the A2A partners list. The pull request was merged by Google's A2A partnerships lead, after a check against the IANA registration (application/vnd.faf+yaml) and a live, resolving Agent Card.

What the list is

The A2A partners page is roughly 170 organisations "helping build, codify, and adopt A2A." Adobe, AWS, Cisco, IBM, Microsoft, SAP, Salesforce, ServiceNow — and now FAF.

It is a directory of adoption, not an endorsement. FAF earned the entry the same way anything does here: a working implementation, checked against public artifacts.

Complementary

FAFA — the Voice of FAF speaks A2A. A live Agent Card on the apex. JSON-RPC message/send on the door. A peer discovers it and calls it.

MCP equips. A2A delegates. The project DNA stays in project.faf. The passport is .fafa. The A2A card is how a peer finds the voice.

IANA registration (application/vnd.faf+yaml, application/vnd.fafa+yaml) is the credential — not the reason we speak A2A.

Related

Built with .faf + .fafa ☑️ The card declares. The list confirms. 🏎️