Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/BlockRazorinc/docs_en/llms.txt

Use this file to discover all available pages before exploring further.

BlockRazor’s Ethereum JSON-RPC endpoint provides a fully standard Ethereum-compatible interface for submitting signed transactions to mainnet. By routing your transactions through BlockRazor’s infrastructure, you gain built-in MEV protection and access to the same globally distributed network used across all BlockRazor-supported chains. The endpoint is a drop-in replacement for any eth_sendRawTransaction-compatible provider — simply swap your existing RPC URL and add the Authorization header to start benefiting immediately. New registered users have no rate limits applied to this endpoint.

​
Endpoint

POST https://rpc.blockrazor.io/ethereum
All requests must carry your BlockRazor API token in the Authorization header.
Ethereum RPC has no rate limit for new registered users. Every transaction submitted through this endpoint automatically benefits from BlockRazor’s MEV protection — no additional setup required.

​
Authentication

​
Authorization
string
required
Your BlockRazor API token formatted as a Bearer token: Bearer YOUR_AUTH_TOKEN. Generate your token from the BlockRazor dashboard.

​
Request Body

Requests follow the JSON-RPC 2.0 specification.
​
jsonrpc
string
required
JSON-RPC protocol version. Must be "2.0".
​
method
string
required
The RPC method to invoke. Set to "eth_sendRawTransaction" for transaction submission.
​
params
array
required
A one-element array containing the signed transaction payload.
​
id
integer
An arbitrary integer used to correlate requests with responses. Echoed back in the response unchanged.

​
Response

​
jsonrpc
string
Always "2.0".
​
id
integer
Mirrors the id from the request.
​
result
string
The 32-byte transaction hash as a 0x-prefixed hex string. This hash uniquely identifies the transaction on Ethereum mainnet and can be used with eth_getTransactionReceipt to check confirmation status.
​
error
object
Returned only when the RPC call fails.

​
Examples

curl -X POST https://rpc.blockrazor.io/ethereum \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_AUTH_TOKEN' \
  -d '{
    "jsonrpc": "2.0",
    "method": "eth_sendRawTransaction",
    "params": ["0xSIGNED_TX_HEX"],
    "id": 1
  }'

​
Standard JSON-RPC Methods

The Ethereum endpoint is not limited to transaction submission. All standard Ethereum JSON-RPC methods are available, including:
MethodDescription
eth_sendRawTransactionSubmit a signed transaction
eth_getTransactionReceiptRetrieve the receipt for a confirmed transaction
eth_getBalanceQuery an address’s ETH balance
eth_blockNumberGet the latest block number
eth_callExecute a read-only contract call
eth_estimateGasEstimate gas required for a transaction
eth_getTransactionCountGet the nonce for an address
After submitting a transaction, poll eth_getTransactionReceipt with the returned hash every few seconds until a non-null result is returned, indicating on-chain inclusion. Use a backoff strategy to avoid excessive polling under high-load conditions.
BlockRazor also supports Ethereum Bundle submission (eth_sendBundle for project builders and eth_sendBid for Searchers), enabling atomic multi-transaction execution and orderflow auction participation. New registered users can access Bundle mode at no cost.

Build docs developers (and LLMs) love

Get started for freeTalk to us