RPC providers: do I need a paid endpoint?
The bot needs a Solana RPC endpoint to read data and send burns. This guide explains when the default shared RPC is enough and when a paid RPC makes sense.
Short answer
- You do not need a paid RPC for tests or low volume burns.
- You likely need a paid RPC if you have high traffic, heavy automation, or strict uptime needs.
RPC modes in the form
| RPC mode | What happens | Who should choose this |
|---|---|---|
| Default shared RPC | Uses a backend-managed shared endpoint | Best for pilots and low volume |
| Own paid RPC | Uses your provider endpoint and quota | Best for high volume and reliability |
What to enter for a paid RPC
- RPC URL (required): Full HTTPS endpoint from your provider.
- API key (optional): If your provider requires it.
- Rate limits: Ensure your plan can handle your volume.
Risks of weak RPCs
- Throttling during high load
- Slow confirmations or failures
- Inconsistent user experience
Quick decision
- Choose default shared if you are early stage or low volume.
- Choose own paid RPC if you need predictable performance and uptime.