Getting Started
Dashboard Guides
Trading Guides
Need Help?
Join our community for support, updates, and trading discussions.
Network Requirements
ScreenerBot requires outbound internet access to function. This page lists all network connections for users with firewalls or corporate networks.
Connection Overview
How ScreenerBot Connects
ScreenerBot runs locally on your computer and makes outbound HTTPS connections to:
Market Data APIs
Fetch token prices, volume, liquidity from public APIs
Your RPC Endpoint
Direct blockchain data via your configured Solana RPC
Version Check
Simple GET to screenerbot.io (no data sent)
Required Endpoints
These domains must be accessible for core functionality. All use port 443 (HTTPS).
Core APIs - Must Whitelist
| Domain | Purpose | Method | Data Sent |
|---|---|---|---|
| api.dexscreener.com | Token prices, volume, liquidity, pool data | GET | Token addresses only |
| api.geckoterminal.com | Pool data, OHLCV candles, trending tokens | GET | Token/pool addresses only |
| api.rugcheck.xyz | Security analysis, risk scores, holder data | GET | Token addresses only |
| api.jup.ag | Swap quotes, unsigned transaction data | GET/POST | Swap request (amounts, mints)* |
| lite-api.jup.ag | SOL/USD price, token discovery | GET | None |
| screenerbot.io | Version check, Billboard tokens | GET | None |
| [Your RPC endpoint] | Blockchain data, transaction submission | POST/WSS | RPC requests, signed transactions |
* How Swap Signing Works: Jupiter/routers return unsigned transaction data. ScreenerBot signs the transaction locally on your computer using your private key, then submits the signed transaction to your RPC endpoint. Your private key never leaves your system.
Optional Endpoints
These provide additional data but are not required for core trading functionality.
Additional Data Sources
| Domain | Purpose | Can Disable? |
|---|---|---|
| api.coingecko.com | Additional token metadata, coin list | Yes - in discovery settings |
| api.llama.fi | DeFi protocol data | Yes - in discovery settings |
| coins.llama.fi | Token price fallback | Yes - in discovery settings |
| gmgn.ai | Alternative swap router | Yes - in swap settings |
Token Images & Media
Dynamic Image Sources (Cannot Whitelist All)
Token logos and NFT images are fetched from URLs stored in token metadata on the Solana blockchain. These sources are unpredictable as each project chooses where to host their assets.
Common image sources:
cdn.dexscreener.com- DexScreener logosipfs.io- IPFS gatewayarweave.net- Arweave gateway- Various project CDNs
If images are blocked:
- Token logos won't display in dashboard
- NFT images won't load
- Trading still works normally
- All data and prices still available
Recommendation: If you use a strict firewall or content blocker, either whitelist image content from crypto-related CDNs, or accept that some token logos may not display. This does not affect trading functionality.
RPC & WebSocket Connections
Your Configured RPC Endpoint
Your RPC endpoint is the primary connection to the Solana blockchain. ScreenerBot uses both HTTPS and WebSocket protocols.
HTTPS (Port 443)
Used for:
- • Account data queries
- • Transaction submission
- • Balance checks
WebSocket (WSS)
Used for:
- • Real-time transaction streaming
- • Account change notifications
- • Slot updates
Common RPC providers to whitelist:
*.helius-rpc.com*.quiknode.pro*.triton.one*.alchemy.comapi.mainnet-beta.solana.comPrivacy & Security
What ScreenerBot NEVER Transmits
Never sent anywhere:
- Private keys or seed phrases
- Wallet passwords
- RPC API keys (used locally only)
- Trading history to our servers
- Position data to our servers
Our server connection:
- Version check: GET request only
- Billboard: GET featured tokens
- No personal data transmitted
- No wallet addresses sent to us
- All trading via your RPC directly
Firewall Quick Reference
Copy-Paste Whitelist
Add these domains to your firewall's allow list (all use port 443/HTTPS):
# Required - Core Functionality api.dexscreener.com api.geckoterminal.com api.rugcheck.xyz api.jup.ag lite-api.jup.ag screenerbot.io # Optional - Additional Data api.coingecko.com api.llama.fi coins.llama.fi gmgn.ai # Your RPC (replace with your provider) # *.helius-rpc.com # *.quiknode.pro # Common Image CDNs cdn.dexscreener.com ipfs.io arweave.net
Corporate & VPN Considerations
Special Network Configurations
Proxy Configuration
ScreenerBot uses standard HTTPS connections. If your network requires a proxy, configure your system's proxy settings - the app will use them automatically.
VPN Usage
VPNs work normally with ScreenerBot. For best performance, choose a VPN server close to your RPC provider's data center to minimize latency.
Note: WebSocket connections (for real-time transaction streaming) may be blocked by some corporate firewalls. If you experience connection issues, check if WSS connections are allowed on your network.