Skip to main content
Step rerun needs a provider API key because Sovara sends the edited LLM request to the same provider family as the recorded step. Replay keys are separate from your shell environment and belong to your organization: every project in it uses the same keys, and Sovara’s own tooling models use them too. --project-id only says which organization to write to, and accepts a project ID, an unambiguous ID prefix, or an exact project name. Changing a key asks for the organization admin role on the hosted platform, and for admin of one of the organization’s projects on a self-hosted deployment; a local install does not ask. Store a key once, then use sovara rerun without passing that key again. For project-independent model and credential management, use sovara org models. Both command families use the same saved keys.

​
List configured keys

The output shows provider names and masked previews. It does not print raw API keys.

​
Set a key from an environment variable

Common provider names include: Use the provider name shown in the recorded step when in doubt.

​
Set a key from stdin

The CLI intentionally does not accept raw keys as command-line arguments, because command-line arguments can be saved in shell history or process lists.

​
Remove a key

​
Validation

When possible, Sovara validates a replay key before saving it. If validation fails, the key is not saved. Check the provider name and make sure the key has permission to call the model family used by the recorded step.

​
Supported replay providers

Direct step rerun works for providers Sovara can call with a normal API key or bearer token. Anthropic, OpenAI, Gemini, Azure OpenAI, Palantir Foundry, and many OpenAI-compatible providers fit that model. Providers that require cloud request signing or service-account credentials may still be inspectable but not directly rerunnable from sovara rerun.