Skip to main content
PulseScanner.io

High-speed RPC for your wallet

Public endpoints are shared, throttled and slow when the chain is busy. A plan gives you your own private endpoint for PulseChain, fast enough to leave in your wallet as the network you use every day.

See plans
  1. Get a plan

    Connect your wallet in the portal and buy a term. A key is minted with it.

  2. Copy your RPC link

    It is this address with your own key on the end of it.

    https://api.pulsescanner.io/rpc/<your key>
  3. Paste it into your wallet as a network

    Add a network by hand and fill in these five fields.

    Network name
    PulseChain
    New RPC URL
    https://api.pulsescanner.io/rpc/<your key>
    Chain ID
    369
    Currency symbol
    PLS
    Block explorer URL
    https://pulsescanner.io
  4. Done

    Your wallet now reaches PulseChain through your own endpoint instead of a shared one.

For developers

Anything already written against the Etherscan-style HTTP API works here as a drop-in: the same module and action parameters, the same key conventions, the same response envelopes. Underneath it is a wider surface built for PulseChain — one envelope, keyset cursors, and figures this indexer computes rather than proxies.

73 operations · build 2.0.0-dev · read the docs

Plans

The plans, their rate and volume limits, the endpoint groups each one opens, and the features each one carries.
PlanStarter$15 / monthLite$49 / monthStandard$199 / monthAdvanced$299 / monthProfessional$399 / month
Rate and volume
Requests per second35102030
Call units (CU) per day100,000100,000200,000500,0001,000,000
CU per month (daily × 30)up to 3,000,000up to 3,000,000up to 6,000,000up to 15,000,000up to 30,000,000
Endpoints
Wallet JSON-RPCincludedincludedincludedincludedincluded
Etherscan-compatible surfaceincludedincludedincludedincludedincluded
Blocks and transactionsincludedincludedincludedincludedincluded
Tokens, pools and marketsincludedincludedincludedincludedincluded
Token holders and pool statisticsnot includedincludedincludedincludedincluded
Wallet activityincludedincludedincludedincludedincluded
Wallet analyticsnot includedincludedincludedincludedincluded
Consensus layerincludedincludedincludedincludedincluded
Search and network statsincludedincludedincludedincludedincluded
Features
On-demand tracingnot includednot includednot includedincludedincluded
WebSocket connectionsnot included251025
Log query range5,000 blocks10,000 blocks10,000 blocks20,000 blocks50,000 blocks

99% monthly uptime SLA: if the API's availability falls below 99% in a calendar month, the downtime is credited back to your plan at 2×, automatically.

A call unit (CU) is the API's metering unit; each endpoint costs a fixed number of units per request — see the cost list in the docs.

Every plan comes with an API key, and every data call travels with it. Starter covers the standard endpoint groups; Lite and up add the heavy ones.

Keyless: /health, /openapi.json, /v2/plans — plus the account routes the portal signs in with, since that is how a key is obtained. Everything else is a data call and carries a key.

Rate, volume and every endpoint mark on this table are read from the plan record and from each route's own minimum tier. The monthly prices are the published figures. The portal reads the tier table straight out of the billing contract at the moment you look at it, so the figure it charges is the contract's own — a number copied onto a page could only go stale.

Plans can be purchased on our IPFS portal

Get your key today →