Glossary
| Term | Definition |
|---|---|
| Request Counting | How BlockReq counts distinguishable customer Requests and Requests used. |
| Requests | Customer JSON-RPC items and successfully delivered WSS events or notifications. |
| Requests used | Requests after the method multiplier is applied. |
| Requests remaining | Spendable prepaid Requests across active free-grant and Request Pack lots. |
| Request Pack | A one-time prepaid request lot (Starter, Growth, Professional, or Business) with its own validity window. |
| PAYG | Billing mode that accrues at $3.90 per 1M Requests used after prepaid Requests are exhausted. |
| Wallet balance | Settled USD value used to fund PAYG and eligible purchases; separate from Requests remaining. |
| Endpoint | A chain-specific RPC access point with credential and policy metadata. |
| API Key | A credential used to authenticate endpoint requests. |
| Chain | A blockchain network such as Ethereum Mainnet, Base, or BSC. |
| JSON-RPC | The request/response protocol used by supported blockchain nodes. |
| HTTPS | Secure HTTP transport for standard request-response RPC calls. |
| WSS | WebSocket Secure transport for persistent connections and real-time subscriptions such as eth_subscribe. |
| Archive Data | Historical blockchain state for deep-history reads. Availability depends on chain and route capability, not only the billing tier. |
| Rate Limit | Sustained and burst request limits from the effective plan. |
| Free grant | A 3M-Request lot with a 30-day validity window. |