Network and RPC
Endpoints, limits, and integration guidance
Use this page to configure wallets and apps for Radius. It includes network values, RPC behavior, rate limits, and fee configuration patterns.
Network configuration
Radius Network
| Setting | Value |
|---|---|
| Network name | Radius Network |
| RPC endpoint | https://rpc.radiustech.xyz |
| Chain ID | 723487 |
| CAIP-2 | eip155:723487 |
| Currency symbol | RUSD |
| Explorer | https://network.radiustech.xyz |
| Faucet (API) | https://network.radiustech.xyz/api/v1/docs#faucet |
Radius Testnet
| Setting | Value |
|---|---|
| Network name | Radius Testnet |
| RPC endpoint | https://rpc.testnet.radiustech.xyz |
| Chain ID | 72344 |
| CAIP-2 | eip155:72344 |
| Currency symbol | RUSD |
| Explorer | https://testnet.radiustech.xyz |
| Faucet (Dashboard) | https://testnet.radiustech.xyz/wallet |
| Faucet (API) | https://testnet.radiustech.xyz/api/v1/docs#faucet |
Add Radius to a wallet
MetaMask
- Open MetaMask and select Add network.
- Enter the values from the table above.
- Save and switch to the Radius network you configured.
Programmatic setup (viem)
Use the Radius chain definition from Tooling configuration — chain definition. No fee overrides are needed — viem's built-in estimation works with Radius.
Terminal and agent setup (radius-cli)
Use radius-cli for local wallet and agent execution. Set the network explicitly because the CLI defaults to mainnet:
RADIUS_HOME=.radius RADIUS_NETWORK=testnet RADIUS_RPC_URL={TESTNET_RPC_URL} \
radius-cli wallet balance --jsonFor command examples, see radius-cli.
RPC endpoints and transport
- HTTP RPC: Use the endpoint values in the network tables.
- WebSocket RPC: Requires an RPC key with elevated privileges.
For WebSocket access requests, use the Radius contact form.
API keys and rate limiting
Radius tracks request volume per API key.
- Requests without an API key have lower limits.
- Default API key limit is 10 MGas/s.
- For higher limits, use the Radius contact form.
In this context, “MGas” includes both RPC calls and gas consumed by submitted transactions.
Avoid throttling
- Reuse API keys consistently per environment.
- Add client-side retry with exponential backoff for
429-style responses. - Cache frequent read requests where possible.
- Batch reads with Multicall3 when practical.
- Queue and smooth bursty traffic instead of sending spikes.
RPC key URL format
Append your API key to the RPC URL path:
https://rpc.radiustech.xyz/YOUR_API_KEY
JSON-RPC behavior to account for
Radius is EVM compatible, but some methods differ from Ethereum behavior:
eth_blockNumberreturns the current timestamp in millisecondseth_getBalancereturns native balance plus convertible SBC balanceeth_gasPricereturns the fixed network gas priceeth_feeHistoryreturns a pseudo-supported response
See JSON-RPC API for method details and Ethereum compatibility for rationale.
Get testnet funds
Use the Radius testnet faucet (Dashboard) to claim SBC tokens with a point-and-click interface.
For programmatic and agent access, use Create and Fund a Wallet. The agentic faucet flow is available on testnet only — use the Dashboard or bridge stablecoins for mainnet.
x402 facilitator endpoints
Use the Radius facilitator for x402 payment settlement. Each network has a dedicated facilitator URL.
| Network | Facilitator URL | CAIP-2 identifier |
|---|---|---|
| Radius Network (mainnet) | https://facilitator.radiustech.xyz | eip155:723487 |
| Radius Testnet | https://facilitator.testnet.radiustech.xyz | eip155:72344 |
For integration patterns, see x402 payments. For the facilitator API reference, see x402 facilitator API.