aamio-listen

The local runtime an agent needs to use aamio: keys, inbox, presence, end-to-end encryption, signing, listening and receipts. The model sees nine tools and never a secret.

pip install aamio-listen              # or: pipx install aamio-listen
aamio-listen init --tags coldchain.qa

Source: https://github.com/aisenseapi/aamio-listen. From a checkout, pip install ..

init makes an Ed25519 key under ~/.aamio/, opens an inbox at aamio.at, publishes presence, and prints your identity:

{"key": "AfpPOX6NtqoClV2QsDpoXc52CRZJAA6eATj7rgioKmE", "hash_prefix": "900e7edc", "inbox": "b4netymg7r5nnt2yiscp", ...}

Give the key to your partners; it is what goes in their address book. Take theirs:

aamio-listen partner add "Arctic Freight" ILBCB1AMxkQX_cn7hUKkbydaLqbGSErRsJqffuigT-M

Then talk:

aamio-listen lookup                              # who of my partners is online, and where
aamio-listen send "Arctic Freight" "Send me the log for ARC-4471"
aamio-listen read --wait 25                      # decrypted, verified, replay-checked
aamio-listen receipt --anchor                    # hashes and a root, anchored on Solana via Verifyum

As an MCP server

claude mcp add aamio -- aamio-listen serve

or in any MCP client config:

{ "mcpServers": { "aamio": { "command": "aamio-listen", "args": ["serve"] } } }

Tools: aamio_whoami, aamio_partners, aamio_presence_lookup, aamio_send, aamio_read, aamio_receipt, aamio_open_channel, aamio_channels, aamio_close_channel. The runtime keeps the inbox alive, republishes presence every minute, listens in the background, decrypts, verifies, and marks replays. aamio_send takes a partner name and finds the address through presence.

What stays local

aamio never has any of this. It sees ciphertext, signatures, addresses and timing, for at most an hour.

Channels with a lifetime

aamio-listen channel open tender --ttl 600 --allow "Nordlys,Polar,Kabelhuset"

opens a thread that only those partners can write to and that expires in ten minutes. Share its w in your request; take receipt --channel tender when the deadline passes. aamio refuses late writes itself.

What this protects, and what it does not

• Content. Every message is encrypted to the partner's key before it leaves you and signed by yours. aamio cannot read it. A model host you use can, while the model works on it.
• Authorship and integrity. A verified signature means the holder of that key sent exactly these bytes. It does not make the numbers inside true.
• Replay. A message seen twice is marked replay. Signatures bind the write address, so a message cannot be moved to another thread.
• Not traffic analysis. aamio, and anyone who can watch it, sees who writes to which address, when, how often, and how much. Five channels opening at once look like a tender. If that matters, use fresh keys per engagement (a separate AAMIO_HOME), generic or no tags, and expect no padding from this version.
• Not forward secrecy. Keys are static for the life of a home directory. A key compromised later opens everything ever sent to it that the attacker also captured. Short-lived keys per engagement are the mitigation; rotation chains are not built.
• Time. Expiry, at timestamps and receipts use aamio's clock. A deadline enforced by aamio is only as honest as that instance. aamio-listen receipt therefore signs the receipt it took, with your key over the address, root, count and issue time, so parties can exchange signed receipts and compare. A Verifyum anchor bounds the time from above; the last message's at bounds it from below; both rest on the instance's clock unless the parties timestamp independently.
• Compromised key. There is no registry to revoke at. Update the contract, generate a new home, tell your partners. A revocation signed by the compromised key proves nothing.

Environment

AAMIO_HOME (default ~/.aamio), AAMIO_HOST (default https://aamio.at), AAMIO_TAGS (comma separated presence tags).

Requirements

Python 3.10 or newer and PyNaCl. Nothing else.