API keys
Understand key handling and the proposed account workflow.
On this page
Current availabilityPlanned key workflowStore a real key safelyReplace an exposed keyDiagnose authenticationCurrent availability#
Real keys cannot be created, revealed or revoked in this preview. The API keys page shows a sample prefix and disabled write actions. It contains no usable credential.
Planned key workflow#
After account services are connected, the intended flow is to name a key, choose its billing mode and expiry, then copy its full value once. Auto, Plan only and API credit only are design options; supported modes and model permissions must be confirmed for the deployed service.
Store a real key safely#
Use a tool's private credential store or an environment variable. Do not put a key in a URL, browser code, public repository or support note. The following commands contain placeholders only.
export DSSUB_API_KEY="YOUR_DSSUB_API_KEY"$env:DSSUB_API_KEY = "YOUR_DSSUB_API_KEY"Replace an exposed key#
With a live service, revoke the credential at its issuing provider, replace it in your tools and review affected usage. The local preview cannot revoke a real key issued elsewhere.
Diagnose authentication#
For a real endpoint, check the key's issuing service, selected model and account access. A 401 usually concerns missing, invalid or revoked credentials. A key from one provider is not automatically valid at another. See troubleshooting.
Guide updated November 5, 2026 · All tutorials