Skip to main content
Darwin Vault is the optional credential store for repeated Actions. It gives an Action a scoped reference, not the underlying secret.
Darwin Vault APIs described on this page are a planned preview. They are not available in the production API or MCP tool set yet.

​
What the Vault can hold

Darwin Vault is designed for OAuth tokens, API keys, client credentials, passwords, TOTP seeds, SSH and private keys, certificates, and provider-specific secrets. Each item records its provider, owner, allowed use, consent, and revocation state without exposing secret material through list operations. One-time access is the default whenever the capability supports it. Saving requires an explicit user choice in the first-party Darwin flow. An AI cannot turn temporary access into persistent access through conversation text or a tool argument.
Vault items are encrypted at rest, excluded from model context, and redacted from logs, traces, analytics, webhooks, and Action results. List endpoints return display metadata and access state only.

​
Grant, reuse, and revoke

  1. The user saves or connects a credential.
  2. Darwin grants a specific AI or Action the minimum required scope.
  3. The runtime resolves the credential only for an authorized execution.
  4. The user can revoke the grant, disconnect the provider, or delete the item.
Deleting a Vault item prevents future resolution. It does not rewrite completed Action receipts or claim that a provider deleted its own records.

​
External vaults stay external

For a connected vault such as 1Password, Darwin stores the vault connection and an opaque item reference. It resolves the secret just in time and does not cache or mirror it into Darwin Vault. Availability, rotation, and deletion remain controlled by the external vault. Continue with Authenticate to use a one-time, Darwin Vault, or password-manager credential in an Action.
Last modified on September 22, 2026