Connecting keys

LoopCodeLab runs on your own accounts. You bring your own AI provider keys and service credentials, connect them in Settings, and LoopCodeLab stores them encrypted for your account with AES-256-GCM. There is no shared middleman billing, so every build spends against your own providers and you decide exactly what is connected.

Two ways to connect

Most coding agents accept either of two connection methods:

• An API key. Paste the key from your provider and LoopCodeLab uses it for planning, building, or review.
• A terminal or browser sign-in. Some agents connect through a subscription sign-in instead, such as a Claude, ChatGPT, Qwen, Kimi, or Grok plan. Settings shows the method each provider supports.

Every credential has a Test button. Use it to confirm a credential is valid before you rely on it, so a dead key never surprises you in the middle of a build.

Where to connect each type

Coding agent keysConnect Claude, Codex, Qwen, Kimi, Grok, and the other build agents.

Media & research keysImage, video, audio, and research providers for media builds.

GitHub tokenLet LoopCodeLab create a repository and push your build.

Google Play & FirebaseShip a mobile app and wire up a backend.

Apple & iOSSubmit an iOS build to App Store Connect.

Windows desktop & StorePackage a web app as a Windows installer or Store submission.

Note

Prices quoted across these pages are current as of writing and can change. Confirm the latest figure on each provider’s own pricing page before you plan around it.