An AI model must always use a paid API key. A free API key can expose user data. A developer must verify the API key location before any script runs.
By Pawan Nayar · from the LLOS AI Learning record
An AI model must always use a paid API key.
A free API key can expose user data. A developer must verify the API key location before any script runs.
A developer must never use a free-tier Google API key. Free tiers can use user data for training. This means user IP addresses could be exposed. Always use paid APIs. Examples include Anthropic, OpenAI, or a paid Google project. These services respect data privacy and copyright. Before a script makes its first API call, a developer must ask where the API keys are stored. Do not guess the file location. Currently, paid API keys are often found in `<workspace-root>/.env`. The key name is `GEMINI_API_KEY_PAID`. Always check the exact location. If a paid key is not found, the script must stop. It should never use an unknown API key. This prevents accidental data exposure.
A developer writes a new script that uses an AI model. The developer does not check the API key location. The script then uses a free-tier API key by mistake. This action could expose the user's private data to the AI model's training data.
Resolved from this lesson's own record — real definitions, not invented for this page.
More from the same record, pulled by shared topic — not written new for this page.
API keys, like those for OpenAI or Google, must be kept in one file. This file is typically named `.env`.
API keys are sensitive information. They should be kept secret.
A developer must always read the root `.env` file first. This file contains the paid API keys.
A developer must not put private rules in the main text of an AI prompt. These rules are called proprietary constraints.
An AI model must always use a paid API key. A free API key can expose user data. A developer must verify the API key location before any script runs.