Sync to OpenAI Vault

OpenAI-hosted Agents API sandboxes can use vault credentials without receiving their real values. OpenAI's network proxy substitutes a credential only on requests to its approved HTTPS hosts. Seekrit can create and rotate those vault credentials from a selected environment.

Read Third-party sync first for the shared decryption grant, filtering, name mapping, and deletion behavior.

1. Create the connection

Create a vault in your OpenAI project, then create a project API key with api.vaults.read and api.vaults.write. The key must be able to access that vault. Enter the key in Sync → Add connection in the dashboard, or pipe it to the CLI:

printf '%s' "$OPENAI_PROJECT_KEY" \
  | seekrit sync connect --name openai-agent --provider openai-vault

Use a project key dedicated to this connection. Seekrit encrypts it before storing it, and only the sync engine can open the connection credential.

2. Bind an environment

Choose the vault ID and the exact HTTPS hostnames that may receive the credentials. --openai-hosts takes hostnames without schemes, ports, paths, or wildcards. Every credential in one binding gets the same host list. Use separate bindings and environments when different credentials need different host access.

seekrit sync verify openai-agent --provider openai-vault \
  --openai-vault vault_123 --openai-hosts api.github.com

seekrit sync enable --connection openai-agent --provider openai-vault \
  --openai-vault vault_123 --openai-hosts api.github.com \
  --app support-agent --env hosted --include 'GITHUB_TOKEN' \
  --acknowledge-decryption

Verification checks vault access and reads credential metadata; it never retrieves existing secret values. The binding's first push creates credentials with a secret_name matching each destination name. Later pushes update only credentials tagged with this seekrit binding's ID. A collision with another vault credential fails that name rather than overwriting it. Removing a name follows the binding's delete or retain setting; delete only removes a uniquely matched credential owned by this binding.

OpenAI reserves PATH, OPENAI_API_KEY, and names beginning with CODEX_ in hosted environments. Seekrit rejects those destination names during sync. Map them to other names if appropriate.

3. Attach the vault to a new session

Attach the vault ID to the Agents API session. The sandbox network policy must also allow each hostname used by a vault credential. Keep the vault's real values out of the session's env map: code running in the sandbox can read that map.

session = client.beta.agents.sessions.create(
    agent={"model": "gpt-6-astra", "instructions": "Use the configured tools."},
    environment={
        "type": "openai_hosted",
        "network": {
            "access": "restricted",
            "allowed_domains": ["api.github.com"],
        },
    },
    vault_ids=["vault_123"],
)

Check the OpenAI vault guide for how its placeholders are used in outbound requests. A value changed by seekrit sync is available to new sessions. OpenAI does not update an existing sandbox after a vault credential changes, so create a new session after rotation.

Troubleshooting

See also

• OpenAI Agents API — choose between native Vault and a proxy you operate
• Third-party sync — grants, name mapping, and deletion policy