Skip to main content
Generate keys in the Dashboard → API Keys.
Treat your API key like a password. Never commit it to source control, never expose it in client-side code, never paste it into a chat session.

​
Get your API key

Sign in

Go to llmquantdata.com and sign up (or log in).

Create an API key

Open the Dashboard → API Keys → Create API key. Copy it once — it won’t be shown again.

Store as env var

Add it to your shell profile (~/.zshrc, ~/.bashrc) for persistence. Both MCP and HTTP usage below read from this single source.

​
How to use it

Every supported MCP client (Claude Code, Cursor, Codex, Gemini CLI, Claude Desktop) reads the key from LLMQUANT_API_KEY. For JSON config files, paste the actual key value in the env block.See MCP Server setup for the per-client commands.
example: Cursor / Claude Desktop config snippet

​
Error codes

​
Rate limits

Rate limits vary by plan. If you exceed your limit you will receive a 429 response. Contact us to discuss higher limits.
An MCP runtime that retries silently on 429 can burn credits fast. Inspect the agent’s tool-call log when debugging unexpected billing.

​
Replace or revoke a key

To replace a key, create a new one in Dashboard → API Keys, update your environments, then revoke the old key. Requests that use a revoked key return 401.
Before revoking the old key, update LLMQUANT_API_KEY in every environment that uses MCP — your shell profile, your CI secrets, your team’s onboarding templates.