Solana, crypto data, exchange, and onchain venue connectors

Key setup: Use a dedicated RPC endpoint from trusted infrastructure or your own node.

Safe permissions: Treat private RPC URLs as infrastructure secrets and never expose seed phrases.

Key setup: Create a Helius key or RPC endpoint for Solana chain and token data.

Safe permissions: Use for RPC/data access; wallet signing remains local and controlled.

Key setup: Create a QuickNode endpoint for production-grade chain access.

Safe permissions: Restrict endpoint access where possible and monitor rate usage.

Key setup: Create an Alchemy app/API key for chain-data workflows where configured.

Safe permissions: Use endpoint restrictions and keep URLs out of browser logs.

Key setup: Use Jupiter docs for quote, route, and swap-preparation workflows.

Safe permissions: A route quote is not approval; ZeroTrade risk-core still decides whether a draft can proceed.

Key setup: Create a Birdeye key for token, liquidity, and market-data workflows.

Safe permissions: Use for screening and data enrichment only.

Key setup: Use DexScreener's API/reference path for pair and liquidity screening.

Safe permissions: Use as a signal input, never as execution authority.

Key setup: Create a CoinGecko demo or pro API key for crypto market data.

Safe permissions: Use for prices, market data, and references only.

Key setup: Create a CoinMarketCap API key for market and reference data.

Safe permissions: Use for data enrichment only and respect plan limits.

Key setup: Create a Binance API key from API Management after enabling account security.

Safe permissions: Avoid withdrawal permission and use IP restrictions where possible.

Key setup: Create a Bybit API key from API Management.

Safe permissions: Use minimum permissions and keep funding/withdrawal access disabled.

Key setup: Create a Kraken key pair from Kraken Pro settings.

Safe permissions: Avoid funding permissions unless deliberately required and separately reviewed.

Key setup: Create Coinbase Advanced Trade API credentials for the correct portfolio.

Safe permissions: Keep transfer permissions off unless there is a specific, reviewed need.

Key setup: Create an OKX API key from account API settings.

Safe permissions: Use IP restrictions and avoid withdrawal permission.

Key setup: Create a KuCoin API key and passphrase from API Management.

Safe permissions: Use least privilege and keep withdrawal permissions disabled.

Key setup: Create a Bitget API key from the customer's own account API settings.

Safe permissions: Use IP restrictions and avoid withdrawal or transfer permissions.

Key setup: Create BitMEX API credentials for the selected testnet or production environment.

Safe permissions: Use testnet first and keep account/funds permissions separate from order permissions.

Key setup: Create Deribit API credentials with the minimum scopes required for the workflow.

Safe permissions: Use test environment first and keep withdrawal/funding scopes disabled.

Key setup: Use the Hyperliquid API wallet posture rather than exposing a master wallet key.

Safe permissions: Never store seed phrases; use approved agent/API wallets and strict nonce controls.

Key setup: Create keys at the underlying exchange; CCXT is a framework, not a key issuer.

Safe permissions: Exchange-specific permissions, rate limits, and testnet behavior still apply.