API keys

Create a key#

When the account service is available, open Account → API keys, create a key, and give it a descriptive name. Copy it into a secure location and check the account interface for any key-specific permissions or restrictions.

Store it securely#

Treat the key like a password. Use an environment variable or a secret manager. Do not place it in source code, share it in screenshots, or commit it to a public repository.

On macOS or Linux, set a key in the current terminal session:

export CODING_PLAN_API_KEY="your-api-key"

On Windows PowerShell:

$env:CODING_PLAN_API_KEY = "your-api-key"

These commands affect the current terminal session; opening a new terminal requires setting the variable again.

Replace an exposed key#

If a key has been exposed, revoke it in Account → API keys when the feature is available. Create a replacement and update each application that uses the old key. Never post the key when asking for help.

Troubleshooting#

A 401 response usually means the key is missing, invalid, or revoked. Check that the correct key is being sent to the intended service endpoint. A key from the official DeepSeek platform and a key from this independent service may not be interchangeable.