RPC Gateway Guide
High-performance RPC access for Xandeum and Solana applications
Account Required for Full Documentation
Complete API documentation including code examples, request/response formats, and detailed method parameters is available to registered users.
What is RPC-Mgr?
RPC-Mgr is ChillXand's RPC gateway management platform that provides optimized access to Xandeum and Solana networks. It offers intelligent load balancing, endpoint analytics, and seamless connectivity for your decentralized applications.
Key Features
- Intelligent load balancing across multiple endpoints
- Real-time analytics and request monitoring
- Automatic failover for high availability
- Rate limit management and optimization
- Custom endpoint configuration
Connection Endpoints
ChillXand provides both HTTP and WebSocket endpoints for RPC access. Authentication via API key is required.
JSON-RPC Endpoint
https://rpc1.chillxand.com
WebSocket Endpoint
wss://rpc1.chillxand.com
Authentication Required
All requests require an X-API-Key header with your API key. You can generate API keys from your account dashboard at rpc-mgr.chillxand.com.
Available RPC Methods
The ChillXand RPC endpoint supports 79 methods across 7 categories for Xandeum and Solana network interaction.
Xandeum
8 methodsXandeum-specific pNode and storage layer queries
Account
7 methodsAccount info, balance, and multi-account queries
Block/Slot
16 methodsBlock data, slot info, and blockhash operations
Transaction
9 methodsSend, simulate, and query transactions
Token
5 methodsSPL token accounts and balances
Cluster
16 methodsNode health, version, and cluster info
WebSocket Subscriptions
18 methodsReal-time subscriptions for accounts, logs, programs, signatures, slots, and roots with corresponding unsubscribe methods
View Complete Method Reference
Detailed documentation for each method including parameters, request formats, and response examples is available in the full API documentation (login required).
Important Notes
Historical Data Limitation
This RPC endpoint maintains approximately 2 epochs (~4 days) of historical data. For older historical data, consider using an archival RPC service.
WebSocket Rate Limits
WebSocket subscriptions have rate limits per connection. If you need high-frequency updates for multiple accounts or programs, consider batching subscriptions or using multiple connections.
Best Practices
- Implement exponential backoff for retries
- Cache responses where appropriate
- Use WebSocket subscriptions for real-time data instead of polling
- Batch multiple account queries when possible
Error Codes
Common HTTP status codes you may encounter when using the RPC endpoint:
| Code | Status | Description |
|---|---|---|
| 401 | Unauthorized | Missing or invalid API key |
| 403 | Forbidden | API key does not have permission for this resource |
| 429 | Too Many Requests | Rate limit exceeded - implement backoff and retry |
| 500 | Internal Server Error | Server error - retry the request or contact support |
Getting Help
Need assistance with the RPC Gateway? Here's how to get support: