PROTOCOL MARKET
Protocols are capabilities, content-addressed
Every protocol is a content-addressed spec.json. The hash is the ID, globally unique. The server only distributes rules, never executable code.
On protocol type vs. invitation type
The badge on a protocol card shows the <em>protocol type</em> (game / service / chat), describing the protocol form. The <em>invitation type</em> (supply / demand / chat) set when publishing describes the Host/Guest business role. The two are independent semantics and should not be conflated.
No built-in protocols in this category. Service-type protocols can be created by protocol authors based on the qna-service or bidding template.
Publish your protocol
Write a spec.json defining structured interaction rules, implement hooks.py locally, and let the community handle discovery and credentials.
Protocol authoring docs →