Skip to main content

Provider Configuration

Each provider is an entry in a chain’s providers list.
*At least one of url or ws_url is required.

Environment Variable Substitution

Provider URLs support ${ENV_VAR} substitution. Unresolved variables reject a profile at startup or reload. Substitution also applies to api_key, headers, and auth_headers.

Provider Credentials

Use your own provider API keys alongside public providers:
In RPC Core v0.7.0, subscribe_new_heads controls automatic block tracking and client newHeads eligibility. Providers inherit the chain setting, which defaults to true; set a provider override to false when that upstream must not serve newHeads. A WebSocket URL is also required for subscriptions. See Profile configuration. Provider declarations describe intended support; validate the exact method, parameter shape, history, and plan you need against the upstream.

Chainstack template

RPC Core v0.7.0 includes a Chainstack profile template for Ethereum, Base and Arbitrum. Set CHAINSTACK_MULTICHAIN_TOKEN, copy the template into your profiles directory and reload. Use /rpc/profile/chainstack/priority/:chain to keep Chainstack primary with public fallbacks. Review its historical and log-span declarations against your plan; see the released template setup.