---
title: "FAQ"
description: "Frequently asked questions about BlockReq"
url: "https://blockreq.com/docs/support/faq/"
---

# FAQ

## General

### What is BlockReq?

BlockReq is a Web3 RPC infrastructure platform that provides blockchain node access through a simple API.

### Do I need to run my own node?

No. Create an endpoint and use its RPC URL and credential.

### Is there a free tier?

Yes. Eligible accounts receive **3M Requests** with a 30-day validity window. No credit card is required to start.

---

## Billing & Request Counting

### What is Request Counting?

Request Counting meters distinguishable customer **Requests**, then applies method multipliers to **Requests used**. See [Request Counting](https://blockreq.com/docs/pricing/request-counting/index.md) for HTTP, batch, and WSS rules.

### What happens when I run out of prepaid Requests?

With **PAYG** enabled, additional Requests used accrue at **$3.90 per 1M**. Without Requests remaining and without PAYG capacity, authenticated calls may be rejected. You can:

1. Wait for the next free grant window if eligible.
2. Buy a self-service Request Pack from the Dashboard.
3. Top up Wallet balance and enable PAYG.

### Do unused Requests roll over?

- **Free grant**: valid for its 30-day lot window.
- **Request Packs**: valid for 60 or 90 days from activation, depending on the pack.
- **PAYG**: usage accrues while enabled; it is not a prepaid rollover balance.

### How do I check my balance?

Open the Dashboard. **Requests remaining** and **Wallet balance** are shown separately on billing and endpoint surfaces.

---

## Technical

### Which chains are supported?

See [Supported Networks](https://blockreq.com/docs/build/supported-networks/index.md).

### Do you support WebSocket?

Yes. A WSS subscribe or unsubscribe request counts once. Each delivered EVM `eth_subscription` event or Solana subscription message counts once. Ping/pong and undelivered notifications count zero.

### Do JSON-RPC errors count?

For authenticated HTTP, execution exceptions such as revert still count. HTTP method not found and other non-execution JSON-RPC application errors do not. Authentication or policy rejection, `429`, and gateway `5xx` count zero. WSS request and notification counting is unchanged.