Integrations
APIs ZeroTrade UK can work with for AI, broker-market data, alerts, and research
This page explains the connector map in plain English: what is live, what can be stored in the vault, and what is adapter-ready for broker-supported market workflows.
Plain English
Customers do not need every API key. Start with demo, replay, or paper mode, then add only the connectors required for the exact AI provider, market data source, broker, venue, alert path, or research lane being used. Live execution still needs deterministic risk approval.
Integration Status
What the labels mean
Already part of the current product path for the portal, local node, or advisory workflow.
The customer can store the key in the encrypted vault now; runtime use depends on the enabled mode and adapter.
A defined connector slot exists so the provider can be enabled cleanly without changing the product shape.
Used for advisory research and diagnostics, not direct live trading authority.
Connector Matrix
24 connector slots customers can understand before setup
The matrix separates encrypted key storage from live authority. A saved key does not mean an AI model can trade freely or that a broker route is live without the correct adapter, paper test, and risk configuration.
AI provider
7 supported slots
OpenAILive route
BYOK Oracle reasoning, structured explanations, briefings, and anomaly analysis.
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.
Create OpenAI keyGroqVault-ready
Fast optional AI routing for lightweight classification, summaries, and watch tasks.
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.
Create Groq keyxAI / GrokVault-ready
Optional market-context synthesis and broader advisory reasoning with a customer key.
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.
Open xAI setupAnthropic ClaudeAdapter-ready
Optional research, briefing, and analysis provider through the encrypted vault.
Key setup: Create an Anthropic key from the Claude developer console.
Safe permissions: Use only for non-execution research, summaries, and briefings.
Create Claude keyGoogle AIAdapter-ready
Optional Gemini-style model routing for research and advisory workflows.
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.
Create Google AI keyMistralAdapter-ready
Optional model provider for lower-cost advisory and classification tasks.
Key setup: Create a Mistral API key from the Mistral console.
Safe permissions: Use for advisory and classification lanes only.
Create Mistral keyDeepSeekAdapter-ready
Optional reasoning/model provider for research and non-execution analysis lanes.
Key setup: Create a DeepSeek platform key when this research route is enabled.
Safe permissions: Use for research and non-execution analysis only.
Create DeepSeek keyAI router
1 supported slot
OpenRouterAdapter-ready
Optional model-router key for customer-selected LLM routes where enabled.
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.
Create OpenRouter keyMobile alerting
1 supported slot
Telegram UplinkLive route
Phone alerts, status updates, daily briefs, and approved command-center messages.
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.
Create Telegram botAlerting
2 supported slots
WebhookVault-ready
Outbound or inbound webhook connector slot for approved notification workflows.
Key setup: Create a signed webhook token or endpoint secret for the specific workflow.
Safe permissions: Verify signatures and rate-limit inbound command surfaces.
Read webhook notesEmail SMTPAdapter-ready
Optional email delivery credentials for notices, reports, and operator alerts.
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.
Read email notesQuantum research
1 supported slot
IonQResearch lane
Optional ZeroTrade Quantum research jobs and portfolio probes; advisory only.
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.
Open IonQ docsBroker adapter
4 supported slots
AlpacaVault-ready
Paper/live broker API slot for supported stocks, ETFs, snapshots, orders, and positions.
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.
Open Alpaca docsInteractive BrokersAdapter-ready
Broker-market adapter slot for account, position, and order workflows where enabled.
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.
Open IBKR API docsTradierAdapter-ready
Broker API slot for equities/options workflows where enabled by the customer.
Key setup: Create a Tradier API token for the approved account environment.
Safe permissions: Use only the permissions required for the configured broker workflow.
Open Tradier docsIG MarketsAdapter-ready
UK broker-market connector slot for account and market workflows where approved.
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.
Open IG docsBroker / FX
1 supported slot
OANDAAdapter-ready
FX and CFD-style broker API slot where customer account permissions and region allow it.
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.
Open OANDA docsMarket data
6 supported slots
Polygon.ioAdapter-ready
Market-data API slot for equities, indices, forex, and instrument snapshots.
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.
Create Polygon keyTwelve DataAdapter-ready
Market-data API slot for candles, quotes, technical data, and watchlist support.
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.
Create Twelve Data keyFinnhubAdapter-ready
Market-data and news API slot for broker-market monitoring and briefs.
Key setup: Create a Finnhub API token from the Finnhub dashboard.
Safe permissions: Use for market data and news/context feeds, not order authority.
Create Finnhub keyAlpha VantageAdapter-ready
Market-data API slot for basic quotes, indicators, FX, equities, and macro references.
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.
Create Alpha Vantage keyTiingoAdapter-ready
Market-data API slot for equities, prices, and historical datasets where enabled.
Key setup: Create a Tiingo API token for historical and reference datasets.
Safe permissions: Use for data retrieval only.
Open Tiingo APIFinancial Modeling PrepAdapter-ready
Market-data and fundamentals API slot for watchlists and research surfaces.
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.
Open FMP docsCustom connector
1 supported slot
Custom ProviderVault-ready
Flexible encrypted slot for market-data APIs, private webhooks, or provider-specific keys.
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.
Read custom connector notesCustomer Rule
Use least-privilege keys and keep live authority separate
OpenAI, Groq, xAI, Claude, Gemini, Mistral, OpenRouter, and similar providers are for advisory work: classification, explanation, briefings, and research.
Broker and exchange keys should begin read-only or paper where possible. Withdrawal, transfer, funding, or broad permissions should not be enabled casually.
UK customers should check broker or financial-provider status directly with the FCA register or Firm Checker where applicable before live use.