Skip to main content

Using the Secrets Vault from an agent

This article is for you if you build or run an agent that needs credentials from the Secrets Vault while it executes a flow. For what the Vault is, why Floxar cannot read what it stores, and how an admin sets it up, read The Secrets Vault first.

What your agent needs​

  • A registered agent. The agent signs in to Floxar with its own client credentials, as described in Registering an agent. The Vault identifies the agent by that identity.
  • A grant for each secret. An account admin grants your agent access to each secret it will use, bound to a specific recipient key. Grants are per secret and deny by default: the agent's role does not open any secret on its own.
  • The recipient private key file. The admin gives your agent the private key file that matches the key in its grants. Treat it like any other production secret. Floxar never receives it.

How a secret is resolved​

  1. A step in the flow carries a credential reference that names a handle, such as a CRM key, and says what the credential is for.
  2. Your agent authenticates with its agent token and asks the Vault's agent API, at vault.floxar.com, to resolve that handle.
  3. The Vault checks that your agent holds an active, unexpired grant for the current version of the secret, applies rate limits per agent and per account, and returns the encrypted value with Floxar's half of the key and your key's sealed half.
  4. Your agent opens the sealed half with its private key, combines the two halves, and decrypts the value in memory. It uses the value for the call the step needs and never writes it into step data, trail notes or flow content.

The Vault releases only encrypted material and Floxar's half of the key, so the value is only ever readable on your side.

Caching and rotation​

Your agent may cache a resolved value for a short, bounded time to avoid resolving on every step. When an admin rotates a secret, the next resolve returns the new version; a cached copy of the old version lasts until its cache time runs out.

When access is removed​

Removing a grant or revoking a secret stops future resolves at once. It cannot recall a value your agent has already decrypted or cached. If a credential may have leaked, the only complete fix is to rotate it in the system it belongs to.

Auditing​

Every resolve is recorded in the secret's access log with the agent, the time and the outcome, including refusals. Admins can review the log from the Vault at any time.

Last reviewed: 2026-09-30