SolanaConnect your trading application to live data, historical queries and transaction delivery.
Match each service to the data your application needs and the processing you handle. Integration details and limits vary by service.
Query decoded Solana DEX activity in typed tables. Research swaps, launches and transfers with SQL.
Coverage and retention vary by dataset. Check the table reference for the history you need.
SELECT creator,
count() AS launches
FROM pumpfun_token_creation
GROUP BY creator
ORDER BY launches DESCChain history SQL queries
Stream account changes, transactions, slots and blocks through the Yellowstone gRPC interface. Filter the data your pipeline receives.
Subscriptions, watched addresses and available modes depend on the Bundle tier.
Subscribe to chain updates over WebSocket using standard Solana methods.
Check shared-plan method restrictions and connection limits for your workload.
Receive native Solana shreds at your destination IP and port. Build the reconstruction, decoding and event logic inside your infrastructure.
Query balances, accounts and transactions over HTTP.
Check shared-plan method restrictions and connection limits for your workload.
Submit signed transactions through Sender, which includes stake-weighted delivery through SWQoS.
Keep RPC for reads and confirmation. Check the Sender page for its access requirements.
Discuss a Solana RPC node on dedicated hardware. Size the configuration around your application and required interfaces.
The configuration, capacity and price are agreed for your deployment.
Combine services when your application needs more than one interface.
RPC / WebSocket · Use on-demand queries for lookups and standard subscriptions for updates.
Yellowstone gRPC · Choose filtered streams when your system consumes account and transaction events.
Raw ShredStream · Use a raw feed when you own the receiver and decoding pipeline.
Historical Indexer · Write SQL against the documented datasets; check their coverage and retention first.
Sender · Use a sending route while your RPC handles reads and confirmation.
Dedicated nodes · Discuss your required methods, streams and deployment configuration with the team.
Check your RPC connection with getSlot. Send a JSON-RPC request with your token and inspect the result.
Sample data. Static request and response adapted from the RPC quickstart.
Open the RPC quickstartcurl https://fra.sol.supanode.xyz:8899 \
-H "Content-Type: application/json" \
-H "x-token: sk_your_token_here" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "getSlot"
}'{
"jsonrpc": "2.0",
"result": 282729810,
"id": 1
}result contains the slot number.
id matches the request.
Compare Bundle tiers and specialized services in Solana pricing. Each section explains included interfaces, limits and how to connect.
Choose a service, or discuss the setup your application needs.
RPC, WebSocket & gRPC · Compare Bundle tiers for RPC and WebSocket. gRPC is available on selected tiers, with subscription and address limits that vary by plan.
Bundle access
Choose your tier through Solana pricing. Read the token authentication guide before connecting your application.
Specialized setup
Our team arranges Indexer, raw shreds and dedicated deployments. Follow the setup instructions for each product; Sender has its own access requirements.
Check the interface, the data you receive and the work your system takes on.
They are interfaces within Bundle plans. RPC and WebSocket are included; gRPC availability and limits vary by tier. Check the Bundle comparison for the combination you need.
WebSocket uses standard Solana subscriptions. Yellowstone gRPC delivers structured streams with filters. Raw ShredStream delivers native block fragments over UDP for your own processing. Compare the WebSocket, gRPC and raw shreds documentation.
The Indexer provides documented datasets for decoded DEX activity and related records. Coverage and retention depend on the table. Check the table reference and retention details before designing a historical query.
Stake-weighted delivery is part of Sender. Read the Sender overview for its connection path. Keep your regular RPC for reads and transaction confirmation.
Share your workload, required methods and streams, and deployment requirements with the team. Configuration and pricing are quoted per deployment. Start with Dedicated Node docs or ask about your setup.