The fmsg specification only describes host-to-host communication protocol semantics and message definitions. Implementors need to agree on transport, port bindings, encryption etc. to interoperate. Further, other functionality such as retrieval of messages, user identity and access management, is undefined by the specification. So a full fmsg setup includes other components which could vary between deployments and use-case. For instance an enterprise identity management system could be integrated on one host, and a custom user management system on another host.
This page indexes common standards for a fmsg host to follow and services augmenting a host.
Each standard is prefixed with a unique identifer following the format: "FMSG-###", where "###" is a 3 digit number.
| Standard | Short Description |
|---|---|
| FMSG-001 | TCP+TLS Transport and Binding Standard |
| FMSG-002 | Address lookup, quota and usage accounting, and optional provisioning HTTP API |
| FMSG-003 | HTTP API spec client to perform CRUD operations on messages for a specific address |
| FMSG-004 | A2A protocol binding over fmsg |
| FMSG-005 | Emoji reactions to messages, carried as terminal fmsg messages |
| FMSG-006 | Ephemeral indicators such as composing a reply, as unacknowledged UDP datagrams |
| FMSG-007 | Model Context Protocol binding: how an MCP server gives an AI agent an fmsg address |