Create an API Key

An API key identifies your Potato API account when a tool sends requests through the relay. Create one after registering and signing in to the console.

Keep Your Key Private

Treat your API key like a password. Anyone with the key may be able to use your quota.

• Before You Begin
• Creation Steps
• Save the Key
• Security Recommendations
• Modify Token Settings
  • Editable Settings
  • Modification Steps
• Environment Variable Examples

Before You Begin

Make sure you have:

• A Potato API account that can sign in to the console.
• Enough balance or quota for the model you want to use.
• The model name you plan to call from your tool.

Creation Steps

1. Sign in to the PotatoAPI platform.
2. Open Token Management.
3. Click Add Token.
4. Create the token you need. If you are not sure which group to use, leave the user group unset first. If the dashboard or monitoring page provides group guidance, choose the group that matches the model status, token description, and rate multiplier.
5. Save the token, then copy the generated key immediately.

Model Restriction

Leave the model restriction list empty unless you clearly understand how it affects access. For most new users, an empty list is the simplest and safest configuration.

Save the Key

After creation succeeds, store the key somewhere secure right away.

# Example key only. Replace it with your actual key.
sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Never Commit Keys

Do not paste API keys into public screenshots, issue reports, chat messages, or code repositories. Mask the middle section when asking for configuration help.

Security Recommendations

Recommendation	Why It Matters
Do not share the key	It can consume your quota.
Do not commit it to a repository	Git history is hard to clean completely.
Store it in environment variables	Tools can read it without hard-coding secrets.
Rotate it regularly	Limits the impact of accidental exposure.
Disable unused tokens	Keeps old integrations from continuing to run.

Modify Token Settings

After creating a key, you can adjust token settings from the console.

Editable Settings

Setting	Use It For
Token name	Give each token a clear display name, such as Trae laptop or Claude Code server.
Quota limits	Set unlimited quota, a daily/monthly limit, or a total cap.
Rate limits	Control requests per minute, requests per hour, or concurrent requests.
Enable / disable	Temporarily stop a token without deleting it.

Modification Steps

1. Sign in to the console.
2. Find the token you want to modify.
3. Click Edit.
4. Change the related settings.
5. Save the changes.

Important Notes

• Setting changes take effect immediately.
• Some tools may need to be restarted before they read the new configuration.
• Changing the token group may require creating a new key.
• Keep the key available for later tool configuration.

Environment Variable Examples

Use the variable name required by the tool you are configuring. The examples below show ANTHROPIC_AUTH_TOKEN, which is commonly used by Claude-compatible tools.

Windows PowerShell

$env:ANTHROPIC_AUTH_TOKEN="YourKey"

macOS / Linux

export ANTHROPIC_AUTH_TOKEN="YourKey"