Niches · Secrets & credential vaults

Supply secrets to an agent running in CI, serverless or a container with no person present

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
10companies, fit with a limit
14companies carry the tag
12share of the category's work
4first-hand accounts

What counts as done

The job authenticates with its platform identity and no stored static token, gets every secret it needs before its first step, never blocks on an interactive prompt, and fails with a non-zero exit when access is missing.

Measured, for our own tests: that failure comes within 10 seconds. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: get secrets into the GitHub Action without storing them, load keys in Lambda, authenticate the container to the vault

Does the job, with a limit 10

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
1Password service accounts, SDKs and Environments MCP BB
AgileBits Inc. (doing business as 1Password)
Service account tokens are non-interactive, but they are stored static tokens. Credential Broker verifies an OIDC workload token, but it is public preview, needs Business, and still needs an integration key kept as a CI secret. source
Akeyless (SecretlessAI and MCP server) BB
Akeyless Security Ltd.
AWS IAM, Kubernetes and Universal Identity logins avoid a static token, but the free plan lacks OIDC, SAML and LDAP auth, and no doc states how the CLI exits when unauthenticated. source
AWS Secrets Manager A
Amazon Web Services, Inc. (Amazon Web Services EMEA SARL and other regional entities by account location)
On AWS compute the task or instance role reads secrets with no stored token, and Roles Anywhere covers off-AWS workloads with certificates. No doc gives a failure time for missing access, and off-AWS setups often fall back to a static key. source
Azure Key Vault BB
Microsoft Corporation
A managed identity gets a token for https://vault.azure.net with no stored credential on Azure compute. Off Azure needs a service principal secret or federation, and no doc gives a failure time. source
Doppler BB
Doppler Technologies, Inc.
Service account identities log in by OIDC from CI, EC2 or Kubernetes and get a short-lived token, on Team and Enterprise only. No failure time is stated, and acc-25 hit Lambda's 4 KB environment limit. source
Google Cloud Secret Manager BB
Google LLC (Google Cloud EMEA Limited and other regional entities by billing address)
On Google Cloud compute the attached service account reads secrets with no stored key, and off-cloud workloads can use workload identity federation or a key file. No doc gives a failure time for missing access. source
HashiCorp Vault + Vault MCP Server C
HashiCorp, Inc. (an IBM company)
Auto-auth covers AWS, Azure, GCP, Kubernetes, AppRole and others, so no static token is needed. No doc gives the time or exit code when access is missing. source
Infisical AA
Infisical, Inc.
Machine identities log in with OIDC, AWS, GCP, Azure, Kubernetes or Universal Auth, but acc-12 reports an expired session opens an interactive login that hangs, still open with no non-interactive flag. source
Phase B
Phi Security Inc.
External identities let AWS IAM and Azure managed identities authenticate without a stored token; no GCP or Kubernetes provider is listed, and no doc states the failure time when access is missing. source
Pulumi ESC BB
Pulumi Corporation
A workload exchanges its OIDC token for a Pulumi access token, 25 hours at most by default, and --non-interactive disables prompts. Organisation tokens through OIDC need Essentials or higher, and no failure time is stated. source

Doesn't do this job 2

Listings in the category that do something else, with the reason.

ListingWhy
Bitwarden Secrets Manager C
Bitwarden Inc. (terms name 8bit Solutions LLC, wholly owned by Bitwarden Inc.)
Machine accounts authenticate only with a stored access token in BWS_ACCESS_TOKEN; no OIDC, IAM or Kubernetes login is documented. source
Keeper Secrets Manager B
Keeper Security, Inc.
Devices authenticate with a stored Base64 configuration holding the client ID and keys, created from a one-time token; no cloud or Kubernetes identity login was found, and IP lock is on by default. source

What stops agents finishing

  • off-cloud runtime needs a static access key
  • CLI falls back to an interactive login
  • environment variable size limit on the platform

Around it

Before: infrastructure.deploy. After: code-sandboxes.run-command.

Where this comes from

Weight 12 of 100 in Secrets & credential vaults: 4 of 27 accounts (CI workload identity after the Claude Code action leak, Lambda 4 KB limit, Infisical interactive login hang, 1Password SDK with no user login)

The same as data: /api/v1/use-cases/secrets.headless-runtime.json, or the MCP tool get_use_case with id secrets.headless-runtime. Other jobs in this category: /api/v1/niches?category=secrets.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.