Pricing that works for everyone

In blockchain, an RPC (Remote Procedure Call) node is a remote server running a pre-installed blockchain node client, fully synchronized with its network peers. An RPC node reads and writes blockchain data, allowing its operator to access the full distributed ledger.

When using a private RPC node, dApp developers receive an API endpoint URL, activate it (if required), integrate it into their codebase, and begin sending requests to the blockchain.

Compute Units (CUs) measure the computational resources consumed by an API endpoint user. CU consumption depends on two key factors: the blockchain network the dApp is running on, and the specific API methods (commands) the dApp executes.

Requests per Second (RPS) is a bandwidth metric that indicates how many requests an API endpoint can process per second. High-traffic, data-intensive dApps require higher RPS limits to prevent request congestion.

Endpoints serve as secure connection points that authenticate users for connecting to blockchain nodes. By claiming an endpoint, the user confirms that they are authorized to connect to a specific testnet or mainnet.

GetBlock offers both free and paid packages with varying service limits: rate limits (RPS), Compute Units (CUs) allocation, number of simultaneous endpoints, and additional service parameters.

GetBlock accepts payments in both cryptocurrency and fiat. When choosing fiat, users authorize a credit or debit card. When paying with crypto, users complete a one-time transaction via QR code.

If your Compute Units (CUs) are nearly depleted, you can purchase additional packages directly from your GetBlock Account. To avoid running out, consider upgrading to a higher-tier package.