Xcavate Solochain RPC

Xcavate

Xcavate Solochain

Xcavate Solochain RPC access for QA, smart contract testing, and wallet integration, with archive and trace support for pre-mainnet workflows.

Xcavate Solochain

Create RPC Endpoint

Xcavate Solochain RPC Endpoint

The below example uses the public API endpoint*. This endpoint is only suitable for testing. To avoid rate limiting and service interruption, sign up now to get your own API key.

Open In Polkadot JS

Example CURL

curl -H "Content-Type: application/json" -d '{"id":1, "jsonrpc":"2.0", "method": "chain_getBlock"}' 'https://xcavate-solochain.api.onfinality.io/public'

curl -H "Content-Type: application/json" -d '{"id":1, "jsonrpc":"2.0", "method": "chain_getBlock"}' 'https://xcavate-solochain.api.onfinality.io/public'

HTTPs

https://xcavate-solochain.api.onfinality.io/public

https://xcavate-solochain.api.onfinality.io/public

Websocket

wss://xcavate-solochain.api.onfinality.io/public-ws

wss://xcavate-solochain.api.onfinality.io/public-ws

* The public endpoint is rate limited

RPC API Service

RPC API Features

ArchiveTrace

PRICING

Calculate Your Costs

Only pay for what you need.

Monthly Response Units

Million Standard Requests

0100M200M300M400M

Total Cost

$49/ month

Recommended Plan: GROWTH

Continue with this plan

Xcavate powers an open ecosystem of dApps and SDKs that directly satisfy core human needs.

Xcavate is the operating system for human potential – an interoperable chain where every individual owns their identity, data, and economic rights, then uses in-app tools to build the exact application layer they need to climb from survival to self-actualisation.

Xcavate Solochain RPC resources

Xcavate Solochain helps teams validate integration work before a mainnet launch, so the important questions are endpoint access, supported methods, and how the test workflow maps to production.

Best fit: non-mainnet testing workflows for wallet testing, staging, and pre-production checks.

What builders usually check first:

Run contract, wallet, and backend checks before sending users to mainnet.
Keep QA and staging environments close to the production chain model.
Validate reads, writes, and event handling with low-risk test traffic.
Move from shared testnet access to mainnet or dedicated infrastructure when release traffic becomes predictable.

Supported capability notes:

Authenticated Xcavate Solochain RPC/API access for wallet testing, staging, and pre-production checks.
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 test-focused path for staging releases before moving traffic to mainnet.

Decision notes:

Environment: non-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.

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:

Use this network for integration confidence first: contract calls, wallet flows, event handling, and backend jobs.
Before launch, repeat the same checks against the target mainnet and review pricing or dedicated-node needs.

Next steps: