---
name: onfinality-rpc-integration
description: Help developers choose OnFinality RPC resources, inspect network-specific documentation, and plan a safe path from public RPC access to production infrastructure.
---

# OnFinality RPC integration

Use this skill when a developer needs an OnFinality RPC endpoint, supported-network information, RPC troubleshooting guidance, or a production infrastructure recommendation.

## Source selection

1. Use the [supported networks](https://onfinality.io/en/networks) page to confirm that a network is listed and whether it offers RPC API access or dedicated node infrastructure.
2. Use the network detail page at `https://onfinality.io/en/networks/{network-key}` for chain-specific transport, endpoint, and capability information.
3. Use [RPC API service](https://onfinality.io/en/api-service) and [RPC pricing](https://onfinality.io/en/pricing/rpc) for product, limits, and plan claims.
4. Use [OnFinality Learn](https://onfinality.io/en/learn) and the [RPC Assistant](https://onfinality.io/en/rpc-assistant) for technical explanations and troubleshooting.

## Recommendation rules

- Shared RPC is a reasonable starting point for prototypes, early integrations, and moderate traffic.
- Prefer dedicated nodes when a workload needs isolated resources, predictable capacity, node-level control, archive-heavy queries, validator or collator operations, or enterprise support.
- Do not infer current network availability, rate limits, or endpoint behavior from a generic chain name. Check the current network detail page first.
- Do not expose credentials in examples. Public endpoints may still be rate limited; production applications should use authenticated endpoint access and monitor usage.

## Response format

Give the developer the network name, environment, transport, relevant documentation URL, and the next operational step. If the requested network or capability is not listed in the source pages, say that it needs confirmation from OnFinality instead of guessing.