dip or in the API ever shows the value again.
A secret is a named, versioned value that Dippr stores encrypted. Its handle is secret:// followed by its name, such as secret://stripe-api-key. The handle is what you put in a request, a binding or a conversation with your agent. It is safe to paste anywhere because it is not the value.
Secrets is available in tenants that include the
secrets entitlement. Where it is not included, you can still see, rotate, disable, delete and unbind the secrets you already hold, but you cannot create, generate, request, bind, add destinations or grant access, and dip secret exits naming the entitlement for those. See Entitlements.What ships today
A secret that is bound to an app is stored and recorded as bound. Delivering a bound secret to a running app is not available yet, and neither are MCP tools for secrets, customer-managed encryption keys or external secret stores. The pages in this section say so wherever it matters.
Write-only means write-only
- No screen reads a value. The secret’s page shows its name, kind, status, versions and who holds which privilege. It does not show, mask or copy a value.
- No command reads a value.
dip secret listreports metadata only. There is nodip secret get. - A value you invent is shown once. The one exception is Generate: when Dippr invents a random value for you, it shows it a single time so you can copy it. Rotate the secret if you lose it.
- Replacing is allowed. You can rotate a secret to a new value at any time. You cannot read the old one back.
Names, handles and kinds
A name is 1 to 63 characters: lowercase letters, digits,-, _ and .. Names are unique among your tenant’s secrets that are not deleted.
Each secret has a kind, which is a label that helps people recognise it: api_key (API key), token, password, certificate or generic. The kind does not change how the value is stored.
A value can be up to 64 KiB. Your tenant can hold up to 200 secrets and 20 open requests for values at a time; the Secrets page shows how many you have used.
Statuses
A deleted secret leaves your lists straight away. See Delete and retention.
Versions and rotation
Every value you store is a version. Rotating a secret creates the next version and makes it the current one; the version it replaces is kept as the previous one while consumers move over. The secret’s page lists each version with a state:
Versions only move forward. There is no rollback to an earlier value. If two people rotate at the same moment, one rotation succeeds and the other is refused, so a rotation never silently overwrites another.
Custody
Custody says who holds the key that protects a value. Today every secret has Dippr-managed custody: Dippr holds a separate encryption key for your tenant, and your values are encrypted under it before they are stored. The secret’s page shows the custody in a Custody card and in the Secrets list filter. Customer-managed keys and external secret stores are not available yet.Destinations
A destination is a host a secret may be sent to, such asapi.example.com. The Destinations tab on a secret’s page lists them. Destinations are recorded and managed today; they take effect when delivery to apps arrives. A host is a bare name: no scheme, port, path or wildcard.
Delete and retention
Deleting a secret removes it from every list immediately and stops it being used. Its encrypted values are kept for 30 days and are then destroyed, unless a legal hold applies. The names of deleted secrets can be reused once the secret is gone from your lists.Who can do what
Three layers decide every action, and each can refuse on its own:- Your tenant must include Secrets.
- Your role must allow the action on secrets: see Roles matrix.
- For one particular secret, you must hold the right privilege on it: see Secret access.
Related
- Secrets in the console
- Request a value from someone
- Secret access
dip secret- Agent skills: the
altimate-secretsskill teaches your agent to ask instead of handle.