FAQ
Common questions and answers about Soldexer
General Questions
What is Soldexer?
What is Soldexer?
Soldexer is a high-throughput data service for accessing Solana’s historical and real-time data. It processes 10MB+ per request with ~2-3 second latency, making it significantly faster than running your own node.
How does it work?
How does it work?
Soldexer uses a decentralized network of 2,900+ worker nodes (SQD Network) to index and process Solana data. You make API calls to request specific data, and Soldexer returns it filtered and transformed according to your needs.
What's the connection between SQD and Soldexer?
What's the connection between SQD and Soldexer?
SQD Network by SQD provides the decentralized infrastructure that powers Soldexer. The network’s 2,900+ worker nodes ensure reliable data processing and transparent architecture.
What's the pricing model?
What's the pricing model?
Soldexer stays free while in Open Beta. Learn more about pricing here: soldexer.dev/#pricing.
How does Soldexer compare to alternatives?
How does Soldexer compare to alternatives?
Here’s how Soldexer compares to other solutions:
| Capability | Soldexer | Geyser Node by Helius | Dune Analytics | Other Solutions (QuickNode, Alchemy) |
|---|---|---|---|---|
| Speed & Throughput | ✅ Pull 10MB+ per request with ~2s latency | ⚪ Real-time streaming, optimized for low latency but not bulk data requests | ⚪ SQL queries with variable execution times | ❌ Slower response times for high-volume queries; optimized for general-purpose RPC calls |
| Transformation & Filtering | ✅ Built-in composable pipelines at source level | ⚪ Requires custom plugin development for filtering | ⚪ SQL-based filtering, fixed to predefined SQL syntax | ❌ Limited filtering capabilities; requires external tools for advanced processing |
| Historical Access | ✅ Full archive (in progress) | ❌ Real-time only unless paired with external DB | ✅ Extensive historical access | ⚪ Some archive data available but often slower and less efficient for large-scale queries |
| Setup Complexity | ✅ Ready out-of-the-box via SQD portal | ⚪ Simplified with “Automatic Private Nodes” but needs DevOps for advanced setups | ✅ Easy to start, but limited flexibility | ⚪ Easy setup via managed services but lacks customization options |
| Scalability | ✅ Stateless, horizontally scalable | ⚪ Scalable with dedicated hardware but constrained by infrastructure costs | ⚪ Platform-dependent scalability | ❌ Limited scalability for high-frequency workloads; performance tied to pricing tiers |
| Architecture | ✅ Decentralized (via SQD Network) | ⚪ Centralized validator or custom hosting | ❌ Fully centralized platform | ❌ Fully centralized infrastructure reliant on proprietary APIs |
| Cost Efficiency | ✅ Open infra/transparent pricing | ❌ High infra/validator maintenance | ⚪ Free-to-query for basic use | ❌ Higher costs for enterprise-grade services; pay-as-you-go models can be expensive at scale |
| Developer Experience | ✅ Built for engineers: streaming, filtering, piping | ❌ DIY heavy, plugin extensibility requires expertise | ⚪ SQL-only, no programming extensibility | ⚪ Simplified APIs and dashboards but limited flexibility for custom solutions |
I have a few questions, where can I ask them?
I have a few questions, where can I ask them?
Join our Telegram community for direct support and discussions.
Technical Questions
How do I use the API reference?
How do I use the API reference?
Check our API reference section for endpoint documentation, request/response formats, and example calls. Each endpoint includes usage examples and parameter descriptions.
What programming languages and frameworks are supported?
What programming languages and frameworks are supported?
Soldexer provides a REST API that works with any programming language or framework that can make HTTP requests. See our API section to learn more.
How do I filter data for specific accounts or instructions?
How do I filter data for specific accounts or instructions?
Use our granular filtering system to target specific accounts, instructions, programs, or transaction types. You can combine multiple filters in a single request for precise data retrieval.
Are there rate limits or usage quotas?
Are there rate limits or usage quotas?
The public endpoint will serve up to 100 requests in any 10 second window to each unique IP.
Can I use Soldexer with my existing data pipeline?
Can I use Soldexer with my existing data pipeline?
Yes. Soldexer’s REST API and standardized data formats make it easy to integrate with existing ETL pipelines, databases, or analytics tools. Pipes are especially well-suited for being added to existing infrastructure. It’s also not too difficult to build a custom client specifically for your system, see e.g. this example by Cherry library.
FAQ
Common questions and answers about Soldexer
General Questions
What is Soldexer?
What is Soldexer?
Soldexer is a high-throughput data service for accessing Solana’s historical and real-time data. It processes 10MB+ per request with ~2-3 second latency, making it significantly faster than running your own node.
How does it work?
How does it work?
Soldexer uses a decentralized network of 2,900+ worker nodes (SQD Network) to index and process Solana data. You make API calls to request specific data, and Soldexer returns it filtered and transformed according to your needs.
What's the connection between SQD and Soldexer?
What's the connection between SQD and Soldexer?
SQD Network by SQD provides the decentralized infrastructure that powers Soldexer. The network’s 2,900+ worker nodes ensure reliable data processing and transparent architecture.
What's the pricing model?
What's the pricing model?
Soldexer stays free while in Open Beta. Learn more about pricing here: soldexer.dev/#pricing.
How does Soldexer compare to alternatives?
How does Soldexer compare to alternatives?
Here’s how Soldexer compares to other solutions:
| Capability | Soldexer | Geyser Node by Helius | Dune Analytics | Other Solutions (QuickNode, Alchemy) |
|---|---|---|---|---|
| Speed & Throughput | ✅ Pull 10MB+ per request with ~2s latency | ⚪ Real-time streaming, optimized for low latency but not bulk data requests | ⚪ SQL queries with variable execution times | ❌ Slower response times for high-volume queries; optimized for general-purpose RPC calls |
| Transformation & Filtering | ✅ Built-in composable pipelines at source level | ⚪ Requires custom plugin development for filtering | ⚪ SQL-based filtering, fixed to predefined SQL syntax | ❌ Limited filtering capabilities; requires external tools for advanced processing |
| Historical Access | ✅ Full archive (in progress) | ❌ Real-time only unless paired with external DB | ✅ Extensive historical access | ⚪ Some archive data available but often slower and less efficient for large-scale queries |
| Setup Complexity | ✅ Ready out-of-the-box via SQD portal | ⚪ Simplified with “Automatic Private Nodes” but needs DevOps for advanced setups | ✅ Easy to start, but limited flexibility | ⚪ Easy setup via managed services but lacks customization options |
| Scalability | ✅ Stateless, horizontally scalable | ⚪ Scalable with dedicated hardware but constrained by infrastructure costs | ⚪ Platform-dependent scalability | ❌ Limited scalability for high-frequency workloads; performance tied to pricing tiers |
| Architecture | ✅ Decentralized (via SQD Network) | ⚪ Centralized validator or custom hosting | ❌ Fully centralized platform | ❌ Fully centralized infrastructure reliant on proprietary APIs |
| Cost Efficiency | ✅ Open infra/transparent pricing | ❌ High infra/validator maintenance | ⚪ Free-to-query for basic use | ❌ Higher costs for enterprise-grade services; pay-as-you-go models can be expensive at scale |
| Developer Experience | ✅ Built for engineers: streaming, filtering, piping | ❌ DIY heavy, plugin extensibility requires expertise | ⚪ SQL-only, no programming extensibility | ⚪ Simplified APIs and dashboards but limited flexibility for custom solutions |
I have a few questions, where can I ask them?
I have a few questions, where can I ask them?
Join our Telegram community for direct support and discussions.
Technical Questions
How do I use the API reference?
How do I use the API reference?
Check our API reference section for endpoint documentation, request/response formats, and example calls. Each endpoint includes usage examples and parameter descriptions.
What programming languages and frameworks are supported?
What programming languages and frameworks are supported?
Soldexer provides a REST API that works with any programming language or framework that can make HTTP requests. See our API section to learn more.
How do I filter data for specific accounts or instructions?
How do I filter data for specific accounts or instructions?
Use our granular filtering system to target specific accounts, instructions, programs, or transaction types. You can combine multiple filters in a single request for precise data retrieval.
Are there rate limits or usage quotas?
Are there rate limits or usage quotas?
The public endpoint will serve up to 100 requests in any 10 second window to each unique IP.
Can I use Soldexer with my existing data pipeline?
Can I use Soldexer with my existing data pipeline?
Yes. Soldexer’s REST API and standardized data formats make it easy to integrate with existing ETL pipelines, databases, or analytics tools. Pipes are especially well-suited for being added to existing infrastructure. It’s also not too difficult to build a custom client specifically for your system, see e.g. this example by Cherry library.