Stellar API, RPC Service & Dedicated Nodes

OnFinality provides managed Stellar RPC endpoints and dedicated node infrastructure for developers building on the Stellar network. Whether you are creating payment applications, wallets, or backend services, OnFinality offers reliable blockchain connectivity with observability and scaling options.

What is Stellar?

Stellar is an open-source blockchain designed for fast, low-cost cross-border payments and asset tokenization. It connects financial systems worldwide, enabling near-instant settlement with minimal fees. The network is maintained by the non-profit Stellar Development Foundation and supports a wide range of use cases including remittances, stablecoins, and decentralized finance.

Why Use Stellar RPC?

Stellar RPC provides real-time access to network data, allowing developers to query the blockchain, submit transactions, and interact with smart contracts (Soroban). It is essential for building non-custodial wallets, monitoring network activity, and integrating Stellar into existing financial infrastructure. OnFinality simplifies this by offering managed endpoints that handle node maintenance, scaling, and monitoring.

Stellar RPC Endpoints on OnFinality

OnFinality offers Stellar RPC endpoints with HTTP and WebSocket transport. Developers can create an API key through the OnFinality dashboard and connect using standard JSON-RPC methods. Endpoints are available in multiple regions, including N.Virginia, and support archive data for historical queries. For production workloads, OnFinality provides dedicated nodes with isolated resources and enhanced reliability.

Dedicated Nodes for Stellar

For teams requiring full control and higher throughput, OnFinality offers dedicated Stellar nodes. These nodes are isolated, providing consistent performance and access to all RPC methods. They are ideal for high-volume applications, exchanges, and institutional users who need predictable latency and uptime.

How to Connect to Stellar on OnFinality

1. Create or sign in to your OnFinality account.
2. Select Stellar from the supported networks list.
3. Create an API endpoint or deploy a dedicated node.
4. Test the endpoint using the example method chain_getBlock.
5. Monitor request usage, errors, and limits via the dashboard.

OnFinality handles node synchronization, updates, and infrastructure management, allowing you to focus on building your application.

When to Use Stellar Infrastructure

Choose OnFinality when your team needs Stellar infrastructure for payment apps, wallet workflows, Soroban-related services, backend systems, and dedicated node operations.

If you are comparing infrastructure requirements, start with dedicated nodes or the RPC provider selection guide.

Stellar RPC and developer resources

A useful Stellar RPC page should make the connection path, supported capabilities, and production planning trade-offs clear before a developer opens the dashboard.

Best fit: mainnet production workflows for Web3 products, integrations, and app backends.

What builders usually check first:

• Read blocks, storage, events, and governance or staking data from Substrate-based chains.
• Support wallets, indexers, parachain apps, collators, validators, and analytics services.
• Plan node infrastructure when the workload needs isolated resources or chain-specific operations.

Supported capability notes:

• Authenticated Stellar RPC/API access for Web3 products, integrations, and app backends.
• Flexible HTTP and WebSocket access for app, backend, and integration workflows.
• Archive-capable workflows when the product needs older chain state.
• Managed node options for workloads that outgrow shared endpoint access.

Decision notes:

• Environment: mainnet. Protocol family: Substrate JSON-RPC.
• Flexible HTTP and WebSocket access is listed for supported app and backend workflows.
• Archive support is available for historical state or older chain-data queries.
• Dedicated node options are available when the workload needs isolated resources or more operational control.
• Available regions listed by the network spec include N.Virginia.

A quick connection check usually starts with chain_getBlock, then moves into the exact methods your wallet, dashboard, bot, indexer, or backend service needs.

Planning the next step:

• Shared RPC is usually enough for early integration, prototypes, and moderate app traffic.
• Consider dedicated nodes when traffic becomes sustained, workloads are latency-sensitive, or isolation and monitoring become operational requirements.

Next steps:

• Create or manage RPC endpoints
• Review RPC pricing
• Explore dedicated nodes
• Read the Stellar RPC guide