API keys

API keys are the primary credentials for Aikey365 API calls and can also be used to isolate environments and enforce access controls.

Naming

Use clear names such as:

dev-local
staging-service
prod-backend
claude-code-personal

Implemented controls

The current Aikey365 key schema includes:

• enabled / disabled status
• remaining and used quota
• unlimited quota mode
• expiration
• group selection
• model restrictions
• IP allowlists
• cross-group retry
• smart or manual routing
• routing preferences and candidate channel lists
• failover and maximum attempts

Advanced controls may be hidden or restricted depending on permissions and current configuration.

Model restrictions

For a key dedicated to one workload, restrict the available models to what that workload actually needs.

IP allowlists

They work best for services with stable egress addresses. Dynamic, serverless, or multi-region environments should verify egress behavior before enabling a strict allowlist.

Secrets

export AIKEY365_API_KEY="sk-..."

Use secret storage in production. Never commit real keys to source control or print them in logs.

Verify

curl https://aikey365.com/v1/models \
  -H "Authorization: Bearer $AIKEY365_API_KEY"