APIs ZeroTrade can work with across AI, Solana, exchanges, brokers, data, alerts, and research

Key setup: Create a dedicated project API key in the OpenAI platform.

Safe permissions: Use for Oracle explanations, briefings, anomaly triage, and schema-validated advisory output only.

Key setup: Create a GroqCloud API key from the Groq console.

Safe permissions: Use for fast classification and summary tasks; never mix it with venue credentials.

Key setup: Create an xAI API key from the xAI Console when this advisory route is enabled.

Safe permissions: Use for market-context synthesis and research notes; do not send secrets in prompts.

Key setup: Create an Anthropic key from the Claude developer console.

Safe permissions: Use only for non-execution research, summaries, and briefings.

Key setup: Create a Google AI Studio API key for Gemini-style advisory routing.

Safe permissions: Keep it scoped to AI work and rotate it if it appears in logs or screenshots.

Key setup: Create a Mistral API key from the Mistral console.

Safe permissions: Use for advisory and classification lanes only.

Key setup: Create a DeepSeek platform key when this research route is enabled.

Safe permissions: Use for research and non-execution analysis only.

Key setup: Create an OpenRouter key if you want customer-selected model routing.

Safe permissions: Apply usage budgets and never route trading secrets through model prompts.

Key setup: Create a bot with BotFather and store the bot token plus approved chat IDs.

Safe permissions: Treat the bot token like a password and restrict commands to approved chats.

Key setup: Create a signed webhook token or endpoint secret for the specific workflow.

Safe permissions: Verify signatures and rate-limit inbound command surfaces.

Key setup: Use a provider-specific SMTP/app password rather than the main mailbox password.

Safe permissions: Limit delivery scope to alerts, reports, and account notices.

Key setup: Create an IonQ Quantum Cloud API key only for the optional Quantum research lane.

Safe permissions: Quantum output is advisory research and cannot approve live orders.

Key setup: Create Alpaca paper credentials first, then add live credentials only when ready.

Safe permissions: Keep paper and live keys separate and avoid permissions outside the selected workflow.

Key setup: Use the broker API access path supported by the account and region.

Safe permissions: Start with account and paper-style permissions before live order authority.

Key setup: Create a Tradier API token for the approved account environment.

Safe permissions: Use only the permissions required for the configured broker workflow.

Key setup: Create an IG API key from the account's API/developer settings.

Safe permissions: Check account eligibility and keep live dealing disabled until paper review is complete.

Key setup: Create an OANDA REST API token in the customer account.

Safe permissions: Use practice credentials first and check regional eligibility before live use.

Key setup: Create a Polygon.io market-data API key for snapshots and historical data.

Safe permissions: Market-data keys should not be confused with broker dealing authority.

Key setup: Create a Twelve Data API key for quote, candle, and indicator workflows.

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

Key setup: Create a Finnhub API token from the Finnhub dashboard.

Safe permissions: Use for market data and news/context feeds, not order authority.

Key setup: Create an Alpha Vantage key for reference data and indicator checks.

Safe permissions: Respect free/paid rate limits and keep it out of client-side code.

Key setup: Create a Tiingo API token for historical and reference datasets.

Safe permissions: Use for data retrieval only.

Key setup: Create a Financial Modeling Prep API key for market and fundamentals data.

Safe permissions: Use as a data provider, not as a trading venue.

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: Use this for provider-specific market data, private webhooks, or approved internal keys.

Safe permissions: Document the purpose before saving and never store seed phrases or account passwords.