# Credentials (/docs/credentials)

How Solaris AI Flow stores and uses your API keys securely.



Credentials are encrypted API keys and tokens stored in your account. They let nodes authenticate with external services without hardcoding secrets into workflows.

Why credentials are separate [#why-credentials-are-separate]

* **Reusability** - one credential works across all workflows that need it
* **Security** - encrypted at rest, never exposed in workflow exports or marketplace clones
* **Rotation** - update a key once, all workflows pick up the change

Supported platforms [#supported-platforms]

| Platform    | Auth type        | Used by                                                                        |
| ----------- | ---------------- | ------------------------------------------------------------------------------ |
| OpenRouter  | API key          | AI nodes                                                                       |
| Birdeye     | API key          | Birdeye node                                                                   |
| Helius      | API key          | Helius node                                                                    |
| CoinGecko   | API key          | CoinGecko node                                                                 |
| Dune        | API key          | Dune node                                                                      |
| DefiTheOdds | API key          | DefiTheOdds node                                                               |
| Telegram    | Bot token        | Telegram node                                                                  |
| Discord     | Webhook URL      | Discord node                                                                   |
| Jupiter     | API key + wallet | API key required for all ops except transfer. Wallet needed for swap/transfer. |

**Phoenix Flight is intentionally absent.** Phoenix uses a one-time per-wallet invite activation, not a persistent credential. Activate via the inline panel inside any Phoenix node's config dialog. See the [Phoenix node page](/docs/nodes/defi/phoenix) and [Per-Integration Guide](/docs/credentials/integrations#phoenix-flight) for details.

Encryption [#encryption]

All credential values are encrypted server-side before storage. When you view a credential, values are masked (only last 4 characters shown). The decrypted key is only accessed by the execution engine at runtime.

Scope [#scope]

Credentials are per-account. Any workflow you own can use any credential you've added. Credentials are never included in marketplace clones - buyers must supply their own.

Connections page layout [#connections-page-layout]

Connections are grouped by platform category:

* **AI Models** - OpenRouter
* **Blockchain** - Birdeye, Helius, Jupiter, Dune, DefiTheOdds, CoinGecko
* **Messaging** - Telegram, Discord

Expand a platform to add, edit, or delete keys. A connected badge shows when at least one key exists for that platform.

Next steps [#next-steps]

* [Adding Credentials](/docs/credentials/adding) - step-by-step CRUD
* [Per-Integration Guide](/docs/credentials/integrations) - where to get each key
