What is the Solana RPC URL?

The Solana Mainnet Beta RPC URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/solana. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io. The WebSocket endpoint is wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/solana.

Is the Solana RPC free?

Every new BoltRPC account starts with a free trial that covers Solana, with no credit card required. The current trial terms and plan prices are on the [pricing page](/pricing). Solana's own public endpoints are free but rate-limited per IP and not intended for production traffic.

How much does a Solana RPC endpoint cost per month?

BoltRPC plans bill in request units, with the current prices and the weight of every Solana method published on the pricing page. A read-heavy app pays for what it calls and the calculator shows the monthly figure before you commit.

Is Solana EVM compatible?

No. Solana uses its own runtime and account model. It does not support eth_* JSON-RPC methods or Solidity contracts. Use @solana/web3.js for JavaScript, solana-py for Python or the solana-client crate for Rust, all of which work unchanged with the BoltRPC endpoint.

Does BoltRPC serve Solana Mainnet or Devnet?

The endpoint serves Solana Mainnet Beta, the production cluster. Point your Connection at the BoltRPC URL instead of clusterApiUrl("mainnet-beta") and everything else stays the same.

What is the difference between slots and blocks on Solana?

A slot is a roughly 400 millisecond window in which a leader may produce a block. Not every slot produces a block. Chain state is addressed by slot number: getSlot returns the current slot, getBlock fetches the block for a given slot.

Does BoltRPC support WebSocket for Solana?

Yes. BoltRPC provides WebSocket endpoints for Solana at wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/solana. All native subscriptions work: accountSubscribe, programSubscribe, logsSubscribe, slotSubscribe and signatureSubscribe.

Why is getProgramAccounts more expensive than other calls?

getProgramAccounts scans every account a program owns, which can be millions of accounts on a busy DEX or token program. That is why it carries a higher request-unit weight than getAccountInfo. Narrow it with filters (dataSize, memcmp) and dataSlice, or switch to programSubscribe to receive changes instead of rescanning.

Why does getBlock or getTransaction return error -32015?

Since Solana mainnet epoch 1035 (2026-09-15) blocks carry version-1 transactions next to legacy and v0. Pass "maxSupportedTransactionVersion": 1 in the config object of getBlock and getTransaction; without it the node answers -32015 for any block or transaction that contains a v1 transaction. logsSubscribe streams need no change.

Solana RPC Endpoint

Solana workloads lean on getProgramAccounts, logsSubscribe and relentless polling at 400 ms slots. Dedicated capacity keeps heavy read patterns flowing on every plan.

JSON-RPC 2.0WebSocket

Start free trial Contact sales

LIVE LATENCY

28ms

LIVE

gateway round-trip · sampled every second

IN PRODUCTION AT Chainlink

Your endpoint, ready in one line.

Drop this URL into your RPC client, HTTP library or wallet config. No SDK install required.

HTTPS

https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/solana

WEBSOCKET

wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/solana

Replace YOUR_API_KEY with your API key. Get a free key →

Pick your stack.

Copy-paste examples for the libraries you already use. Swap the API key, hit run.

import { Connection } from "@solana/web3.js";

const connection = new Connection(
  "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/solana",
  { commitment: "confirmed", wsEndpoint: "wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/solana" }
);

const slot = await connection.getSlot();
console.log("Current slot:", slot);

import asyncio
from solana.rpc.async_api import AsyncClient

async def main():
    async with AsyncClient("https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/solana") as client:
        slot = await client.get_slot()
        print("Current slot:", slot.value)

asyncio.run(main())

import { Connection } from "@solana/web3.js";

const connection = new Connection(
  "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/solana",
  { wsEndpoint: "wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/solana" }
);

// One notification per slot, no polling. Every notification is billed at the method weight.
connection.onSlotChange((slot) => {
  console.log("Slot", slot.slot);
});

curl https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/solana \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","id":1,"method":"getSlot"}'

Connect your dApp, trading bot or indexer to Solana Mainnet Beta with BoltRPC. Solana is the non-EVM chain where a slot lands every 400 milliseconds and one getProgramAccounts call can scan an entire program, so published per-method request-unit pricing matters more here than on any other network. Solana is included on every plan and in the free trial.

Chain at a Glance


Cluster	Mainnet Beta
Protocol	Solana JSON-RPC over HTTPS, PubSub over WebSocket
Slot time	~400 ms
Gas token	SOL
Smart contracts	Programs (Rust, Anchor), account model
EVM compatible	No (no `eth_*` methods, no ethers.js or viem)

What Solana is Built For

Solana is a high-throughput Layer 1 that runs a single global state with parallel transaction execution. Blocks arrive roughly every 400 milliseconds and fees are a fraction of a cent, which is why the busiest consumer apps, DEX aggregators, perpetuals venues and NFT launches live here. The architecture is different from every EVM chain BoltRPC serves: state lives in accounts owned by programs, there is no eth_call and clients speak Solana’s own JSON-RPC API through @solana/web3.js, solana-py or the Rust client. Solana’s traffic pattern is also different. Applications poll getAccountInfo and getMultipleAccounts continuously, scan programs with getProgramAccounts and hold long-lived WebSocket subscriptions. The public endpoints are rate-limited per IP by design, so anything past a prototype needs a dedicated endpoint that sustains that volume without throttling.

Common Use Cases on Solana

DEX aggregators and trading bots Routing and arbitrage engines read pool state on every slot and stream fills over logsSubscribe. Continuous polling at 400 ms cadence is the workload the endpoint is sized for.

NFT mints and token launches A mint compresses a day of traffic into minutes: candy-machine reads, getSignatureStatuses polling and sendTransaction bursts from thousands of wallets at once. Dedicated capacity keeps the mint page responsive while the public endpoints are saturated.

Wallets and payment backends Balance displays, token account lookups and deposit detection run getTokenAccountsByOwner and getSignaturesForAddress for every user session. Reliable reads are the difference between a balance that updates and a support ticket.

Indexers and analytics Program indexers replay getBlock with maxSupportedTransactionVersion set and keep programSubscribe open for live updates. Published request-unit weights let you budget the backfill before you run it.

Built for teams that ship on Solana.

Included on every plan and in the free trial

Solana is a standard BoltRPC network. The free 2-week trial covers it, every paid plan covers it and the endpoint is live the moment you create a key.

Published request-unit weights for heavy methods

getProgramAccounts, getBlock and getSignaturesForAddress cost more than a getSlot and the weight of every Solana method is on the pricing page. You can see the bill for a polling loop before you write it.

Native WebSocket subscriptions

accountSubscribe, programSubscribe, logsSubscribe, slotSubscribe and signatureSubscribe run on the same key over wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/solana. Watch every account a program owns instead of polling it.

Dedicated capacity for 400 ms slots

Solana produces 150 slots a minute. Bots, aggregators and wallets that read at that cadence need an endpoint that answers at that cadence, without per-IP throttling and without a queue behind other tenants.

Built for launch-day traffic

Token generation events, NFT mints and volatility spikes multiply read volume in minutes. BoltRPC is built for high-throughput workloads, so the spike is a billing line, not an outage.

ISO 27001:2022 certified infrastructure

The endpoint runs on infrastructure certified to ISO/IEC 27001:2022 and operated by a team with years of production node operation, with automatic failover.

Full JSON-RPC coverage.

Every standard Solana method you would expect. Archive-only methods are available on request for qualifying plans.

STANDARD18

getAccountInfogetMultipleAccountsgetProgramAccountsgetBalancegetTokenAccountBalancegetTokenAccountsByOwnergetBlockgetBlockHeightgetBlockTimegetBlocksgetSlotgetSlotLeadergetLatestBlockhashsendTransactionsimulateTransactiongetTransactiongetSignaturesForAddressgetSignatureStatuses

Solana, explained.

Common questions about connecting to Solana over BoltRPC.

Ask a question →Read the docs

: The Solana Mainnet Beta RPC URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/solana. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io. The WebSocket endpoint is wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/solana.
: Every new BoltRPC account starts with a free trial that covers Solana, with no credit card required. The current trial terms and plan prices are on the pricing page. Solana's own public endpoints are free but rate-limited per IP and not intended for production traffic.
: BoltRPC plans bill in request units, with the current prices and the weight of every Solana method published on the pricing page. A read-heavy app pays for what it calls and the calculator shows the monthly figure before you commit.
: No. Solana uses its own runtime and account model. It does not support eth_* JSON-RPC methods or Solidity contracts. Use @solana/web3.js for JavaScript, solana-py for Python or the solana-client crate for Rust, all of which work unchanged with the BoltRPC endpoint.
: The endpoint serves Solana Mainnet Beta, the production cluster. Point your Connection at the BoltRPC URL instead of clusterApiUrl("mainnet-beta") and everything else stays the same.
: A slot is a roughly 400 millisecond window in which a leader may produce a block. Not every slot produces a block. Chain state is addressed by slot number: getSlot returns the current slot, getBlock fetches the block for a given slot.
: Since Solana mainnet epoch 1035 (2026-09-15) blocks carry version-1 transactions next to legacy and v0. Pass "maxSupportedTransactionVersion": 1 in the config object of getBlock and getTransaction; without it the node answers -32015 for any block or transaction that contains a v1 transaction. logsSubscribe streams need no change.
: Yes. BoltRPC provides WebSocket endpoints for Solana at wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/solana. All native subscriptions work: accountSubscribe, programSubscribe, logsSubscribe, slotSubscribe and signatureSubscribe.
: getProgramAccounts scans every account a program owns, which can be millions of accounts on a busy DEX or token program. That is why it carries a higher request-unit weight than getAccountInfo. Narrow it with filters (dataSize, memcmp) and dataSlice, or switch to programSubscribe to receive changes instead of rescanning.

Ship on Solana this week.

An API key in under 60 seconds, Solana plus 35+ other chains, and a team that answers when you write.

Start free trial View pricing