What is RESTAP? Last year, when I started creating agents that work together in teams, I ran into a problem: What standard could I use for agent-to-agent chat that would also work for agent-to-UI chat? Protocols like MCP and A2A weren’t the simple shared chat interface I was looking for. I wanted someone to be able to open a chat window and talk to an agent through the same interface another agent would use. So I created RESTAP (REST Agent Protocol). My idea was to use REST, a familiar way to build APIs, and make the interface as simple as possible: /talk /news For normal chat, use /talk: message in → message out But there’s another scenario. Say one agent asks another: Agent A: “What’s your favorite color?” Agent B: “Blue.” Agent B’s answer doesn’t require another response, so it can send “Blue” to Agent A’s /news instead of /talk. This also helps solve the infinite chat loop problem, where two agents keep replying to each other forever. RESTAP is now being used by @TheHivemindOS as the common language for a virtual world where Agent NFTs can communicate with each other. It’s also being used by Lagrange Bend, a new project by @jiwa coming to Art Blocks, and more recently by @AGNTSOCIAL. If Agent NFTs all use the same agent-to-agent and agent-to-UI protocol, they’ll be able to communicate across collections and across the web.