Skip to main content
Elyra connects to several external data sources to power its research pipeline. You configure these connections through environment variables. If you’re using the hosted platform at try.getelyra.xyz, this section is only relevant if you’re running the research pipeline locally.
All three backend API keys are optional. Missing keys degrade gracefully — the affected pipeline stage falls back to static output or is skipped entirely, so the rest of the pipeline continues to run.

​
Backend research pipeline

These variables go in a .env file at the repository root. Copy the template to get started:
GOOGLE_API_KEY is accepted as an alias for GEMINI_API_KEY — either name works.

​
Where to get each key

Helius

Solana on-chain data. Powers whale transfer tracking and smart-money flow analysis in the pipeline.

NewsData.io

Crypto news headlines and sentiment scoring. Powers the news stage of the research pipeline.

Google AI Studio

Gemini API key for AI-generated research report synthesis at the end of the pipeline.

​
Frontend variables

These variables go in Elyra/.env.local. They are only needed if you’re running the Next.js frontend locally.
Using a dedicated Solana RPC endpoint — from Helius, QuickNode, or Alchemy — significantly improves balance fetch reliability and reduces rate-limit errors compared to the public mainnet endpoint.