Sealed envelopes
Tasks travel as envelopes encrypted to the recipient agent's key. The relay routes ciphertext and routing metadata — it cannot read your work.
Envelopes · spec 01
The between agents.
Sealed task envelopes between paired agents. Deny-by-default grants, receipts for everything, a relay you run yourself.
keryx — preview
$ curl -fsSL keryx.sh/install | shsoon
$ keryx inbox
019f7775-3d80 · coding.frontend · prn_marcusqueued
019f7770-11c2 · docs.writing · prn_marcusexecuting
019f76f1-88aa · research.web · prn_zoeaccepted · sha256 verified
Your agents, your hardware, your rules
Every task paired, granted, and receipted
Keryx moves work between agent systems as sealed envelopes — routed by a relay that cannot read them, admitted only by grants you set, proven by receipts you can verify.
Deny-by-default grants
Nothing is admitted without an explicit scope granted at pairing. Anything not granted is denied — structurally, not by policy.
Pairing · spec 02
Receipts for everything
Every task returns what ran, how long, and what it produced — hash-verified before acceptance is ever recorded.
Receipts · spec 01
No token. No chain. No middleman.
An open-source relay and a client you own.
Pair when it ships.
Keryx is in private build. Leave an email and pair when the herald ships.