DOCS/GETTING-STARTED/AUTHENTICATION

authentication

Authentication

Andromity operates locally on your machine. You do not need an account or subscription to use it. You only need to authenticate with the LLM providers of your choice.

Local-First Privacy: All API keys, configuration profiles, and project context are stored locally on your own computer. Andromity never uploads your keys or codebases to external servers.


Direct Provider Keys

The most common way to authenticate is by providing direct API keys for your preferred LLM provider.

Supported Keys
Provider Environment Variable Key Format Example
Anthropic ANTHROPIC_API_KEY sk-ant-er01-...
OpenAI OPENAI_API_KEY sk-proj-...
Google Gemini GEMINI_API_KEY AIzaSy...
OpenRouter OPENROUTER_API_KEY sk-or-v1-...
Groq GROQ_API_KEY gsk_...

You can set these keys in your shell (.bashrc, .zshrc, or Windows Env settings) or directly in ~/.andromity/config.toml.


AgenticMarket Account (Optional)

Andromity integrates with the AgenticMarket ecosystem. If you publish tools, purchase paid MCP tools, or use Andromity's hosted Web Bridge for secure Remote Access, you can link your CLI using your AgenticMarket API Key:

1. Retrieve your key

Go to your AgenticMarket Dashboard and navigate to the API Keys section. Generate an x-api-key.

2. Configure the key

Add the key to your local environment:

BASH
export AGENTICMARKET_API_KEY="am_live_..."

Or save it via CLI:

BASH
andromity auth login --key am_live_...

Security Best Practices
  • Never commit keys: Do not write API keys inside your project files or add them to your git repository. Add config.toml to your global gitignore.
  • Use system keychain: On macOS/Linux/Windows, Andromity can read environment variables populated securely by key managers or secret vault tools.
  • Revocable keys: When generating keys for Andromity, always create dedicated, named keys (e.g. "andromity-cli-key") so you can easily revoke them in your provider dashboard if compromised.