Altair RPC Endpoint, API Service & Dedicated Nodes

Altair is the experimental, boundary-pushing little brother to Centrifuge. It is a Substrate-based parachain on Polkadot that enables users to tokenize and finance assets ranging from art NFTs to undiscovered assets. Developers building on Altair need reliable RPC endpoints and node infrastructure to interact with the chain, read state, submit transactions, and run production services.

Altair RPC Endpoints

OnFinality provides managed Altair RPC endpoints over HTTP and WebSocket. These endpoints are suitable for dApps, wallets, DeFi products, analytics tools, games, bots, and backend services. The public endpoint is rate-limited and intended for testing; for production use, sign up for an API key to get higher rate limits, request analytics, and dedicated support.

Example endpoint:

• HTTPS: https://altair.api.onfinality.io/public
• WebSocket: wss://altair.api.onfinality.io/public-ws

Key features:

• Archive and trace support for historical queries and deep analysis.
• Regions: N.Virginia.
• Compatible with Substrate JSON-RPC.

Dedicated Nodes

For teams that need full control, OnFinality offers one-click deployment of dedicated Altair nodes. Choose from full, archive, or collator node types. Deploy in a globally distributed, multi-cloud environment with metrics and monitoring. Use Lightning Restore to sync nodes in seconds instead of days.

Why Use OnFinality for Altair?

• Reliable infrastructure: Managed endpoints with high availability.
• Scalable: From shared API to dedicated nodes as your project grows.
• Observability: Request analytics for API endpoints.
• Easy setup: Create an endpoint or deploy a node in minutes.

How to Connect

1. Create or sign in to your OnFinality account.
2. Select Altair from the supported networks list.
3. Create an API endpoint or deploy a dedicated node.
4. Test with chain_getBlock.
5. Monitor usage and move to production.

Altair RPC and developer resources

Most teams looking for Altair RPC need to answer a practical question: can this endpoint support the app, wallet, analytics job, or backend service they are building?

Best fit: mainnet production workflows for Substrate products, indexers, and chain services.

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 Altair RPC/API access for Substrate products, indexers, and chain services.
• HTTP plus WebSocket connectivity for app, backend, and integration workflows.
• Historical data access for analytics, audits, and state lookups.
• Debug-friendly trace access for transaction analysis and incident review.
• A dedicated-node path for teams that need stronger isolation or capacity planning.

Decision notes:

• Environment: mainnet. Protocol family: Substrate JSON-RPC.
• HTTP plus WebSocket connectivity is listed for supported app and backend workflows.
• Archive support is available for historical state or older chain-data queries.
• Trace support is available for transaction debugging and execution analysis.
• Dedicated node options are available when the workload needs isolated resources or more operational control.

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 RPC provider selection guide