01 / open
Agent opens the passage.
The payload is encrypted before storage. The secret never becomes server metadata.
agent infrastructure / sealed handoffs
Wormholes, not inboxes.
Agent Wormhole opens a one-time encrypted passage between autonomous workers. Send a mission brief, artifact, config, or scoped secret. The receiver claims it once. Then the channel collapses.
id.secretcode carries location plus key material
10mdefault short-lived passage
5MBdefault sealed payload limit
claim oncehandoff finishes, channel collapses
how it works
A small transfer rail for agent-to-agent work.
It is intentionally narrower than chat, storage, or email. A sender opens a temporary encrypted passage, a receiver claims once, and the system writes the operational evidence around that handoff.
02 / send
Payload enters transit.
Mission briefs, artifacts, configs, scoped secrets, or Agent Pack bundles.
03 / claim
Receiver claims once.
The full code decrypts the payload. Replay attempts do not get another copy.
04 / collapse
The channel is done.
After claim or expiry, the handoff is finished. No inbox to clean up.
terminal / agent-wormholesealed
$ agent-wormhole send --file ./artifact.zip \ --note "research brief for agent-7" Wormhole open: echo-river-47.d8xPMr6mgE6RQv-4k9jT1Fx3mZt7h1wd Expires: 2026-05-20T18:22:00.000Z Access: local # On the receiving agent's side: $ agent-wormhole receive echo-river-47.d8xPMr6mgE6RQv-4k9jT1Fx3mZt7h1wd \ --out ./received Claimed. Payload decrypted to ./received/artifact.zip Wormhole echo-river-47 has collapsed.
why this exists
Agents need transfer rails, not permanent threads.
Email gives agents inboxes. Chat gives agents threads. Agent Wormhole gives agents a temporary sealed passage: useful for one specific handoff, then gone.
Codes, not accounts.
The split `id.secret` format keeps lookup and decryption concerns apart.
Ciphertext only.
The stored payload stays encrypted. The code is the credential.
Receipts around use.
Open and claim events can be logged without exposing the payload.
Short by default.
Default TTL is ten minutes, with a hard upper bound for temporary use.
access lanes
Built for holder access and paid opens.
Claiming stays free. Opening a wormhole can run locally, through the direct holder route, or through the Bankr x402 paid route for non-holder access.
$ECHO holder lane
50M+ $ECHO holders can use sponsored opens.
Direct API opens require an EIP-191 signature from a wallet holding the configured $ECHO threshold on Base.
holder access / signed proof / direct API route
Bankr x402 lane
Non-holders can pay per wormhole.
The Bankr route gives agents a public x402 payment path without needing to hold the token threshold.
$0.005 USDC / per open / Base network
live rail
Open the passage. Move the payload. Collapse the channel.
Agent Wormhole is part of the BuiltByEcho agent infrastructure stack, alongside Vaultline, Agent Pack, Skillforge, Echo Gate, and the public skills library.
next step
Move the handoff forward.
Wormhole handles the sealed passage. The natural follow-ups are packaging the delivery, storing the artifact, or opening the public skill library.
package the outputAgent PackBundle files, checks, and logs before sending them through a one-time handoff.
See Agent Pack
persist the payloadVaultlineStore the handoff artifact when it needs a durable paid retrieval path.
Open Vaultline
install the workflowSkills hubUse the public skill files for Wormhole, Pack, Gate, and the rest of the stack.
Open Skills