API key lifecycle

Keep one key per service, restrict it to the models and modalities it needs, and store the secret in a backend secret manager. The API-key dashboard is authenticated; documentation does not expose or simulate a real key.

Create a key

Sign in and open the API-key dashboard. Record the secret securely when it is shown. Do not paste a private key into a browser bundle, repository or support ticket.

Rotate and revoke

Replace or rotate the key using the dashboard controls, update the consuming service, verify a small permitted request, then revoke the old credential. For an exposed key, prioritize revocation. See authentication for the documented account and API boundaries.

Common errors

A 401 response calls for a credential check; 403 can indicate scope or permissions. A 402 response can indicate balance or spend policies. Do not print bearer headers while debugging. Read troubleshooting.

Verification and next steps

These instructions describe inspected repository contracts and safe integration boundaries. They do not prove live account access or external provider behavior. Continue with developer answers, API overview and verification limits.