Can I use my own AI provider API keys with VibeControls?

Yes. VibeControls[1] is designed around a Bring Your Own Key (BYOK) model for AI orchestration across 16+ providers and harnesses.

As detailed in the VibeControls BYOK use case guide[2], API credentials live directly in the individual agent's configuration on your machine rather than in a central platform vault. Secret fields are write-only once saved.

Supported setups include:

• Direct provider keys: Anthropic (Claude), OpenAI Codex, Google Gemini, Cursor, OpenRouter, and MiniMax.
• Custom endpoints & self-hosting: Any OpenAI-compatible endpoint with a custom base URL (e.g., Groq, Together, Mistral) and Ollama with custom host overrides for local models or private GPU boxes.
• CLI-native harnesses: Tools that authenticate through their own binaries (such as Aider, Amp, GitHub Copilot, Goose, or Plandex) use their native configuration files on disk.

Because harness sessions run directly against your own inference endpoints, they run on your own inference bill and are not charged against platform AI credits (which apply only to the built-in workspace assistant).

Concept illustration(opens in a new tab) Illustration of the concept, not a screenshot of the actual product — AI Provider Keys, Autonomy and Credits[3]

To set up provider keys, manage autonomy levels, and configure execution gates, explore the AI Provider Keys, Autonomy and Credits concept[3] or manage your fleet in the VibeControls agent app[4].