Read balances and contract state, submit signed transactions, and react to new blocks without running your own nodes. GraphOps RPC works with familiar EVM libraries over HTTPS and WebSocket, and supports Bitcoin RPC over HTTPS.
- Best for
- Wallets, dapps, bots, and backends that read chain state or submit transactions.
- Interface
- JSON-RPC over HTTPS; WebSocket for EVM
- Plan for
- Explicit block consistency, retries, batching, and any application-side indexing.
Choose RPC when
Use RPC when your application needs direct node calls or already uses libraries such as viem,
ethers, or web3.py. You control how calls are combined and how results are stored.
For an indexed GraphQL data model, choose Subgraphs. For an ordered stream feeding your own database, choose Substreams.
What you can build
Each pattern uses standard EVM JSON-RPC methods and works with viem, ethers, or web3.py.
Your application decides how requests combine and where results are stored.
Consistent reads at one block
Price a pool or value a position from several eth_call reads pinned to the same block.
Event history in bounded ranges
Build a transfer history with eth_getLogs, one resumable block range at a time.
Transaction submission and receipts
Broadcast a transaction you signed, store its hash, and poll for the receipt.
Live events over WebSocket
React to new heads and matching logs, and backfill any gap after a reconnect.
Bitcoin applications can call Bitcoin Core-compatible methods over HTTPS; see Bitcoin endpoints.
What you run and what GraphOps runs
Supported networks
Use the live network catalog to choose an EVM or Bitcoin endpoint and check archive coverage.
Choose your network and copy its endpoint.
Integration paths
EVM RPC supports both HTTPS and WebSocket transports. Bitcoin RPC currently supports HTTPS.
| Transport | Use it for |
|---|---|
| HTTPS | Single requests, batch requests, reads, transaction submission, and polling filters. |
| WebSocket | Subscriptions such as new heads, logs, pending transactions, and syncing updates. |
Authenticate requests with an organization-scoped API key. Use header authentication for clients that can attach headers, or route-token authentication for WebSocket clients and HTTPS clients that cannot attach custom headers. See Authentication.
Production behavior
Separate latest reads can observe different chain states. If a workflow compares several values,
select a block first and reuse its number or hash for every call. Choose a finalized block when
you need stable results more than the newest data.
Calls and subscription events consume credits at their current rates. Plan for shared request and concurrency limits across your organization.