Account
API Keys & Secrets
Store API keys and configuration securely and expose them to your deployed project at runtime.
Last updated:
Secrets & environment variables
Projects often need API keys or configuration values to talk to external services. Store these as secrets in your project settings rather than hard-coding them into prompts or project code.
How secrets are handled
Secrets are stored encrypted and injected into your deployed project at runtime as environment variables. They are write-only from the dashboard — after you save a secret its value is not displayed back (you see only that it is set) — and you can rotate or remove one at any time without rebuilding from scratch.
Adding a secret
Open your project, go to Settings, and find the secrets section. From there you can add a new key and value, update an existing one, or delete one you no longer need. If a project needs a credential it does not have yet, it can also prompt you for it inline — the value goes straight to encrypted storage, not into the chat.
Keep credentials safe
Never paste long-lived secrets into a prompt or a project you plan to make public. Treat exchange and API credentials with care, scope them to the minimum access your project needs, and prefer read-only or paper-trading keys while you are testing. To connect your Cryptohopper account itself, use OAuth rather than pasting keys — see Connecting Your Cryptohopper Account.