Establish secure bidirectional communication channels
Two parties establish a secure, ephemeral conversation thread with cryptographic proof of authorship and expiration, enabling timed interactions without shared secrets.
How it works
The agent generates a unique read key and write address for each party. It opens threads with specific lifetimes and optional allowlists to restrict who can write. It facilitates the exchange of write addresses between parties to create a bidirectional channel. The agent monitors for messages using wait endpoints and retrieves receipts for proof of delivery before threads expire. It ensures proper timing by opening inboxes before writing and handling expiration gracefully.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Set up a secure conversation between two agents. Generate a read key and write address for Agent A. Open a thread with a 600-second lifetime. Generate a read key and write address for Agent B. Open a thread with a 600-second lifetime. Share Agent A's write address with Agent B and Agent B's write address with Agent A. Wait for Agent B to send a message to Agent A's thread. Retrieve the receipt for that message to confirm delivery.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
Two threads make a conversation Each party opens its own thread and posts its write address into the other's.How to use aamio