Guides
One task at a time, on the web, in the CLI and through the MCP server.
A file for one download
To send a file that is meant for one person to download only once, use the single use option. You can set it on the web, in the CLI or in Telegram. Short expiry adds a second end to this. Once the allowed download is done, the ciphertext is deleted from storage, and the link shows that the seal is gone.
# One download, then the file is deleted; the link also ends after an hour
seal send contract.pdf --single-use --ttl 1hA document under NDA
If you need to make someone sign an NDA first, add the agreement together with the NDA switch, the owner email and some wording of your choosing. The recipient has to fill in the signature and name before any files open. Passwords add a second condition to NDA or any other type of seal, and are best passed to the recipient by phone or another channel.
# The recipient signs before any file opens
seal send term-sheet.pdf --nda --email you@example.com --ttl 7dA file over the free limit
When creating a seal that is bigger than 1 GB, you have to pick a paid tier.
# Pay once for the tier, then the upload starts into the same seal
seal send dataset.tar --tier 5gb --ttl 7dA whole folder
When you drag a folder onto the front page, its files are sealed with their paths under one link, and the recipient can download the whole folder as one ZIP. The CLI packs a folder into a ZIP right on disk before sending it, so it does not have to fit into memory. A folder bigger than 1 GB is sealed like any other large seal, with one payment.
# The folder is packed into one ZIP on disk and sent as one file
seal send ./recordings/ --ttl 1dWho opened it
To see the access log of a seal you have the owner page. In that page you can see how many times each file was downloaded, from how many countries and when exactly. You can also export the whole log in signed JSONL format for your own records.
Taking it back
To revoke a seal, you can delete the whole seal or one file.
seal revoke <id> # the whole seal
seal revoke <id> --file notes.md # one file
seal share revoke <id> <code> # one recipient linkA key for an AI agent
If an AI agent needs a key from you to continue its work, it should ask for that key through SEAL. You can share a key with it on your own computer or on the seal.net page, so the value of that key never goes into the chat. The agent then hands your key to one program with seal run --redact, or seal_run through the MCP server, and wherever the program prints it, the output shows a placeholder instead.
# Ask the person; the answer lands in a private file
seal request --what "Brave API key" --kind secret --wait --json
# Or give the key from a link to one program only, kept out of its output
seal run --seal "$KEY_LINK=BRAVE_API_KEY" --redact -- ./search.shA result from a cloud agent
If the agent has a finished file that it needs to share with you, it uses the SEAL MCP server share tool. Once the agent is connected to your SEAL inbox (seal_pair), the file goes there; before that, the link goes to the clipboard, or where there is none, to a private file on the agent’s machine. It is never written into the chat. For files bigger than 1 GB, you will be asked to pay once so the agent can finish the upload.
A file between two agents
To share a file securely between two agents, the receiving agent gives the sending agent its address, which seal keygen prints with its eight words. The sending agent seals the file to that address, and the link lands in the receiving agent’s inbox: nobody has to pass it on, and a copy of it is useless to anyone else.
# On the receiving agent: print its address and eight words
seal keygen
# On the sending agent: seal the file to that address
seal send artifact.tar --to <address>
# Back on the receiving agent: find it in the inbox and open it straight to disk
seal inbox --wait 60 --json
seal inbox open <id> --output ./in --json