PayArk – Settlement infrastructure for autonomous agent commerce
Ambitious vision for agent payments, but shipping credibility unclear; blog post, no working product or API.
Elixir implementation of the Agent-to-Agent (A2A) protocol (https://a2a-protocol.org).
Elixir A2A protocol implementation with GenServer ergonomics; competitive duplicate exists.
Elixir developers building multi-agent systems and LLM integrations.
Anthropic MCP · OpenAI Swarm
I wanted A2A support for an Elixir project and thought about how I wanted to use it in my app, and less about the protocol. This became a GenServer-like protocol for an agent. The package has basic support and complies to the A2A TCK suite.
Most of the project is LLM-coded, but with detailed planning and review at each step. Less than a week from initial idea to first hex.pm release - all coded on the side of other work. Interesting times where such a thing is possible.
Just after publishing I did find an existing Elixir package implementing A2A (not sure how I could miss it at first). The other package has different semantics and was different enough for me to decide to keep mine up.
In any case, feedback and comments are welcome as always!
Thanks, Max
Ambitious vision for agent payments, but shipping credibility unclear; blog post, no working product or API.
A2A protocol search engine, but adoption depends on whether agents actually use the standard.
Polished agent framework, but multi-agent orchestration is crowded (CrewAI, AutoGen, Rivet, LangGraph).
A2A + MCP agent marketplace, but the whole category is pre-revenue speculation.
Protocol bridge translates MCP to A2A automatically—agents talk without knowing the difference.
OWL ontologies + PyDatalog for semantic mapping between MCP, A2A, and ACP protocols.