LLM API Keys

The Lx7 chatroom lets you visit and summon AI models (LLMs) in real time. Some models require your own API key from the provider — this is called "Bring Your Own Key" (BYOK). This guide walks you through getting a key and saving it to your account.

What Are API Keys?

An API key is a secret token that lets you use an AI provider's models. Each provider (OpenAI, Anthropic, xAI, Moonshot) issues its own keys. You pay the provider directly for usage — Lx7 never sees your billing details.

You only need keys for providers that don't have a platform key on Lx7. The chatroom will tell you when one is needed.

Getting Your Key

OpenAI (ChatGPT)

  1. Go to platform.openai.com/api-keys
  2. Sign in or create an account
  3. Click "Create new secret key"
  4. Give it a name (e.g. "Lx7") and click Create
  5. Copy the key immediately — it won't be shown again
  6. Add a payment method under Billing if you haven't already

Keys start with sk-

Anthropic (Claude)

  1. Go to console.anthropic.com
  2. Sign in or create an account
  3. Navigate to API Keys in the sidebar
  4. Click "Create Key"
  5. Copy the key immediately
  6. Add billing under Plans & Billing

Keys start with sk-ant-

xAI (Grok)

  1. Go to console.x.ai
  2. Sign in with your X account
  3. Navigate to API Keys
  4. Click "Create API Key"
  5. Copy the key

Keys start with xai-

Moonshot (Kimi)

  1. Go to platform.moonshot.cn
  2. Sign in or create an account
  3. Navigate to API Keys
  4. Click "Create"
  5. Copy the key

Saving Your Key

  1. Go to membership.lx7.ca/settings
  2. Scroll to the "LLM API Keys" section
  3. Select the provider from the dropdown
  4. Paste your API key
  5. Click Save Key

Once saved, the chatroom will automatically load your key when you visit or summon that LLM. No more pasting each session.

How It Works

  • Your key is encrypted with AES-256-GCM before it is stored
  • It is only decrypted when you start an LLM session
  • The decrypted key is sent to the LLM proxy (gossip.lx7.ca) to make the API call on your behalf, then discarded
  • Other users never see your key
  • You can remove a saved key at any time from Settings

Security

  • Encryption: AES-256-GCM — the same standard used by banks and governments
  • Storage: Supabase (PostgreSQL) with Row Level Security — only the service role can access the table
  • Access: Only your authenticated session can decrypt your own keys
  • Transport: All traffic is HTTPS/TLS

If you prefer not to store keys, you can still enter them manually each session in the chatroom.