Per-Integration Guide

Each integration requires specific credentials. Here's where to find them.

ChatGPT

ChatGPT uses a device-login flow instead of an API key. The session is encrypted on the server and used only for AI-node and Copilot runs you start. Usage counts against your own ChatGPT account. Image generation is not available through ChatGPT in Solaris AI; use OpenRouter for AI image output.

For connect steps, reconnecting, where to use it, limits, and troubleshooting, see the dedicated ChatGPT Integration guide.

Grok

Grok uses the same kind of device-login flow as ChatGPT, with no one-time setting to enable first: sign in on xAI's site with a one-time code and your Grok account. The session is encrypted on the server and used only for AI-node and Copilot runs you start. Usage counts against your own Grok account. Image generation is not available through Grok in Solaris AI; use OpenRouter for AI image output.

xAI allowlists its API surface, so a valid Grok login can still be refused API access with a 403. When that happens, paste an xAI API key from console.x.ai instead: the connect dialog offers Have an xAI API key? Use it instead, and the key is validated before it is saved.

For connect steps, the model lineup, reasoning behavior, limits, and troubleshooting, see the dedicated Grok Integration guide.

Venice AI

Venice requires a funded Venice account before keys become live. A brand-new key generated on a $0 balance is created without any error, but it stays inactive until you add USD balance on Venice's side. AI nodes using such a key will fail at runtime, even though the key looks valid in Connections.

Note: This funding goes to Venice, not to Solaris AI. Solaris AI is fully BYOK; you pay Venice directly for the inference you run.

1. Go to venice.ai/settings/api.
2. Add any USD balance to your Venice account. Once your USD balance is greater than $0, the Venice dashboard flips to an API ACTIVE badge in the Overview section.
3. Click Generate Key (in the Quick Start panel) or New API Key (top right) to create your key.
4. Copy the key and paste it into a new Venice AI credential under Connections in Solaris AI.

If you generated a key before adding USD balance to your Venice account, you do not need to regenerate it. Just top up the Venice account; the same key activates on the next call.

Alchemy

An Alchemy credential can hold two separate tokens, and you only need the one(s) for what you are building. Both are entered on a single Alchemy credential in Connections.

• API key (required for the Alchemy node): create a Solana app at dashboard.alchemy.com and copy its key. This powers every Alchemy data operation (RPC, prices, balances, NFTs, and DAS). When you add a key, Solaris AI validates it against the live Solana RPC, so a mistyped key is rejected before it is saved.
• Auth Token (optional, only for the Wallet Activity trigger): an account-level token, separate from any app's API key. Get it in the Alchemy dashboard under Webhooks: the Auth token is in the page header with a Copy button. The page redirects to the create flow until your account has at least one webhook, so create one first; the token is account-level and the same for every webhook. Enter it in the credential's advanced options. With it, Solaris AI creates and manages the Address Activity webhook for your watched wallets automatically.

A credential needs at least one of the two. A credential that has only an Auth Token is trigger-only: its token is used to auto-provision Wallet Activity webhooks, but it is disabled in the Alchemy data node's credential picker, because data reads require an API key.

Most Alchemy operations work on the free plan with no extra setup: Token Balances runs on Alchemy's Portfolio Data API, and Prices and the raw RPC operations run on the Node API. The Assets operations (NFT and digital-asset reads) use the Solana Digital Asset Standard (DAS) API, which is a gated Beta: it is not one of the self-serve services in the Alchemy dashboard, so there is no toggle to turn it on, and access is request-only. If a DAS operation fails with "Unable to complete request at this time" (error -32001), DAS is not available on your account; to request it, email Alchemy Data Services at data-services-product@alchemy.com. You do not need DAS for wallet balances: use Token Balances (Portfolio API) or Token Accounts by Owner (raw RPC).

Jupiter

A Jupiter API key is required for all operations except SOL transfer. Add a Jupiter credential in the Connections page. Transfer uses your Privy wallet directly and does not need an API key.

GMGN

GMGN credentials are API keys issued after you upload an Ed25519 public key to GMGN. Solaris AI can generate the keypair locally in your browser to make this easier.

1. Open Connections, expand GMGN, and click Add key.
2. Use Generate keypair to create the Ed25519 keypair in your browser, or bring your own public key.
3. Open gmgn.ai/ai?chain=sol&tab=api_management, create an API key, and paste the public key when GMGN asks for it.
4. Copy the API key GMGN returns and paste it into Solaris AI.

Solaris AI does not store the generated private key. The current GMGN node is read-only, so the private key is not needed after the API key is created.

Pump.fun

Pump.fun read operations (getCoin, getTopRunners, etc.) need no credential. On-chain operations - buy, sell, createToken (token launch), claimFees, and claimCashback - use your embedded Privy wallet for transaction signing. createToken additionally generates a one-shot mint keypair in-memory to co-sign the launch transaction (never persisted).

Phoenix Flight

Phoenix Flight is the Ellipsis Labs perps DEX where Solaris AI is a registered builder. The platform is in private beta, so every fresh Privy wallet must be whitelisted once with an invite code before any Live signed op (placing/cancelling orders or moving collateral). Paper-mode Phoenix signed ops do not require activation because they never sign or broadcast.

Phoenix activation is NOT a credential. Unlike API-key integrations, invite codes are single-use per wallet and don't belong in a persistent credential row. Activation is handled inline in the Phoenix node config dialog: open any Phoenix node, pick a signed op, flip it to Live, and an "Activate Phoenix Flight access" panel appears at the bottom. Enter your code, pick the code type (access or referral), click Activate. Once activated, the panel disappears forever across every Phoenix node in every workflow for that wallet, and no invite data is ever stored on the node, in workflow exports, or in a credential.

Read-only Phoenix ops and paper-mode signed ops don't require activation. See the Phoenix node page for the full per-op behavior.

Request a code at x.com/PhoenixTrade.

CoinGecko plan types

CoinGecko credentials include a planType field:

• demo - free tier, limited endpoints
• analyst/lite/pro - paid tiers with more data

Set this in the credential config so the node knows which endpoints are available.

Next steps

• Node Reference - see what each node does with these credentials