Skip to content

Sealed sharing

Encrypted credential sharing for AI agents, explained

Short answer

Argoned sealed sharing encrypts one password or API key in your browser, uploads only the encrypted result, and gives you a sealed link for an AI agent or a person, plus a separate access code that unlocks it.

The credential is decrypted only in the browser where the access code is typed. The link opens once and expires at the time you choose, at most 7 days.

By Argoned Last reviewed

A phone sharing a link

Four steps

How a sealed link works, in four steps

A sealed link moves one credential from your vault to the place it is used, encrypted for the whole journey.
A password field on a monitor

  1. Seal it

    Open the login or key in your vault and tap Share on the field. Your browser encrypts it before anything leaves your device.

  2. Send the sealed link

    Give the agent or person the link, and keep the access code apart from it. The link alone opens nothing.

  3. Open it where it is used

    You, or the person receiving it, type the access code on the Argoned page. The credential is decrypted in that browser tab only.

  4. It closes after use

    After one opening, or at expiry, the sealed link returns nothing. You can cancel it earlier in your vault under Session → Shared links.

The facts

Sealed link facts: encryption, expiry and limits

Encryption, access code, expiry, openings and limits of an Argoned sealed link, with the values the vault uses today.
How an Argoned sealed link behaves
WhatDetail
Encryption In your browser: Argon2id turns the access code into a key, and AES-256-GCM seals the value
Access code Generated in your browser: four groups of four characters, case-sensitive
Expiry 1 hour, 24 hours, 48 hours or 7 days (default 48 hours)
Openings Opens once, then stops working
What you can share One field at a time: password, secret, PIN, API key, token, passphrase, private key and SSH key fields
Size Up to 4 KB of text
Receiver No account needed; any modern browser
After reveal The value is cleared from the page after a minute without activity
Cancel In your vault under Session → Shared links, before it is opened
Plans Included on Free and Pro; sealed links do not count towards your items

Our server

What our server stores, and what it never gets

The short list of what our server keeps for each sealed link, and the two things it never receives.
A shield in front of servers

For each sealed link, our server keeps only what it needs to hand out the encrypted value and enforce your limits:

  • The encrypted value, its salt and the key-derivation settings.
  • The expiry, how many times it may be opened and has been opened, and its status.
  • Which vault item and kind of field it came from, and an optional label you type. Do not put secrets in the label.
  • When it was created and opened, and a hashed IP address from the most recent access.

It never gets the credential in plain text. When you copy the link and the code yourself, it never gets the access code either.

With an agent

How to share a credential with an AI agent

How to pass a sealed link to an AI agent, what the agent can see, and when to send it to a person instead.
An AI agent working on a screen

Paste only the link into the chat. When the agent reaches the Argoned page and asks for the access code, type it yourself, for example by taking over the agent’s browser. Keep the code out of the chat.

What the agent sees: today the credential is opened on the Argoned page the agent is looking at, so a browser agent can read it at that moment. It is never in plain text in your chat, your email or on our servers.

When another person runs the agent, send the sealed link to that person instead. They open it in their own browser and sign in through the agent’s secure sign-in form, if it has one.

Limits

What sealed sharing does not do yet

Sealed sharing is new and deliberately narrow. These are the gaps we know about and have not closed yet.
  • It does not hide the credential from an agent that is looking at the page where it is opened.
  • There is no approval step for each use and no history of uses yet.
  • Scripts, MCP servers and automations cannot open a sealed link on their own; a person opens it in a browser.
  • We have not published a list of tested agents yet.
  • The code has not been independently audited. It is public under the MIT licence.

FAQ

Questions

Short answers about why the access code is separate, how hard it is to guess, sharing with two people and what happens at expiry.
Two people beside a large question mark
Why is the access code separate from the link?

So the link alone opens nothing. If a chat, inbox or log keeps the link, it still cannot be opened without the code, which you send another way or type yourself.

How hard is the access code to guess?

It is 16 randomly generated, case-sensitive characters. Argon2id makes every guess slow, and opening attempts on our server are rate-limited.

Can I send one sealed link to two people?

No. It opens once. Create one sealed link per person or agent, so you can cancel each one on its own.

What happens when a sealed link expires?

The link stops working and returns nothing. Create a new one if the task still needs the credential.

Sources

A person beside a locked laptop

Your agent needs a login. Send it sealed.

Seal a login or API key in your browser and send a link instead of the password.

Create a free vault All AI agent guides

£0 · Free plan, no card needed · Encrypted in your browser