Outcome#
You select an available AI route without assuming the lab pays, understand the cost and data boundaries, and keep credentials out of Git and prompts.
Concept#
Models, providers, agents, interfaces, and tool protocols are different components. Account ownership, billing, model access, and data terms can change independently.
Worked Example#
The components are classified correctly and no credential appears in a file, prompt, screenshot, or Git diff.
A correct example uses these decisions:
- What is OpenRouter in this stack? A provider or gateway for model access, routing, billing, and limits.
- Where may an API key be stored? In the supported operating-system keychain or approved secret store.
Common Trap#
Calling OpenRouter an agent, confusing a model with an IDE, or pasting an API key into settings tracked by Git.
If Blocked#
Use the offline route. Purchasing access is never a recovery requirement. For technical symptoms, use AI-agent troubleshooting.
Useful references:
Understand Before Accepting AI Output#
Budget limits reduce financial exposure but do not prove data approval, correctness, or safe execution. You remain responsible for charges on a personal account and for every accepted command and diff.