BSC Mainnet
Chain ID 56
https://bsc-rpc-public.chainpulse.cc/Root path defaults to mainnet; /mainnet and /rpc/mainnet also work.
Low-latency BSC node access for Web3 applications. Pay only for successful requests and fund your balance with USDT.
curl https://bsc-rpc-public.chainpulse.cc/ \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'Mainnet
https://bsc-rpc-public.chainpulse.cc/
Testnet
https://bsc-rpc-public.chainpulse.cc/testnet
Public RPC
Try BSC mainnet and testnet without signing up. Public access is rate-limited per IP; for higher limits, create a free API key.
Chain ID 56
https://bsc-rpc-public.chainpulse.cc/Root path defaults to mainnet; /mainnet and /rpc/mainnet also work.
Chain ID 97
https://bsc-rpc-public.chainpulse.cc/testnetOr use /rpc/testnet on the same host.
curl https://bsc-rpc-public.chainpulse.cc/ \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'Only successful JSON-RPC results are charged.
Track calls, latency, success rate, and spend.
Wallet authentication and hashed, rotatable API keys.
Use dedicated BSC mainnet and testnet endpoints.
Transparent pricing
Pricing is set per 1,000 successful JSON-RPC responses. Failed requests never reduce your balance.
0.0000 USDT
per 1,000 successful requests
Production-grade access for live applications
0.0000 USDT
per 1,000 successful requests
Cost-efficient access for development and testing
Documentation
Connect your wallet, fund your balance with USDT, create an API key, then point your JSON-RPC client at the network endpoint. Successful calls require available balance.
Sign a one-time message to create a secure session.
Fund your account with BEP-20 USDT so successful RPC calls can be billed.
Generate a key in the console and store it securely.
POST to /rpc/mainnet/{apiKey} or /rpc/testnet/{apiKey}. Failed requests are free; successful ones require balance.