Skip to main content
Secrets are the core unit of storage in aivault. Each secret holds an encrypted value that is never returned to callers — only injected by the broker during proxied requests.

list

List secrets (metadata only, no values).

create

Create a new encrypted secret. If the name matches a registry provider’s vaultSecrets, the secret is pinned to that provider and the credential + capabilities are auto-provisioned.

Registry matching

When the secret name matches a registry provider’s vaultSecrets key (e.g. OPENAI_API_KEYopenai), the system:
  1. Pins the secret to that provider (immutable)
  2. Auto-creates the credential with the correct auth strategy
  3. Enables all capabilities defined in the registry entry
For multi-secret providers (e.g. Trello needs TRELLO_API_KEY + TRELLO_TOKEN), the credential auto-provisions once all required secrets are present.

update

Update secret name or aliases (not the value — use rotate for that).

rotate

Rotate a secret’s encrypted value. Re-encrypts with a new DEK.
The old value is discarded and the new value is encrypted with a fresh DEK. An audit event is logged.

delete

Revoke and delete a secret.
This also removes any credential and capability bindings that depended on this secret.

attach-group / detach-group

Attach or detach a secret from a workspace group.

import

Bulk import secrets from KEY=VALUE pairs.
Each entry is processed as if you ran secrets create individually — registry matching, pinning, and auto-provisioning apply. Next: Credentials