API Reference
  1. MevX SaaS API
  2. EVM RPC & WebSocket

Send JSON-RPC over HTTP

post
https://api.mevx.io/saas/rpc/v1/

Execute JSON-RPC 2.0 requests against a MEVX-operated BSC node.

Supported Methods and CU Cost

All current package tiers share this conservative 34-method catalog. Each
successful response costs 10 CU; JSON-RPC errors are not billed.

MethodCU cost
eth_blockNumber10 CU
eth_call10 CU
eth_chainId10 CU
eth_createAccessList10 CU
eth_estimateGas10 CU
eth_feeHistory10 CU
eth_gasPrice10 CU
eth_getBalance10 CU
eth_getBlockByHash10 CU
eth_getBlockByNumber10 CU
eth_getBlockReceipts10 CU
eth_getBlockTransactionCountByHash10 CU
eth_getBlockTransactionCountByNumber10 CU
eth_getCode10 CU
eth_getFinalizedBlock10 CU
eth_getFinalizedHeader10 CU
eth_getRawTransactionByHash10 CU
eth_getStorageAt10 CU
eth_getTransactionByBlockHashAndIndex10 CU
eth_getTransactionByBlockNumberAndIndex10 CU
eth_getTransactionByHash10 CU
eth_getTransactionCount10 CU
eth_getTransactionReceipt10 CU
eth_getUncleCountByBlockHash10 CU
eth_getUncleCountByBlockNumber10 CU
eth_maxPriorityFeePerGas10 CU
eth_mining10 CU
eth_sendRawTransaction10 CU
eth_syncing10 CU
net_listening10 CU
net_peerCount10 CU
net_version10 CU
web3_clientVersion10 CU
web3_sha310 CU

Account/signing, Trace, Debug, transaction-pool, stateful-filter, broad log-scan,
proof/blob-sidecar, and unbounded multi-call methods are denied by default.
eth_sendRawTransaction only relays customer-signed transaction bytes. Methods outside this public catalog are unavailable and return JSON-RPC -32601.
HTTP does not support eth_subscribe or eth_unsubscribe.

Request Rules

  • Accepts one request or a batch of up to 100 requests
  • Maximum request body: 1 MiB; maximum upstream response: 10 MiB
  • Each batch element is authorized and billed independently
  • A batch of n elements counts as n requests against the rate limit
  • Notifications are executed and billed but produce no response
  • Your API key is never forwarded to the node

Error Codes

CodeMeaning
-32700Invalid JSON
-32600Invalid request or batch
-32601Method unavailable
-32603Internal error
-32005Quota exceeded
-32004Unauthorized credential
-32001Upstream unavailable
-32002Invalid upstream response
-32003Upstream response too large
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
enum
required

Canonical lowercase network slug. Chain access is granted by package tier, not per credential.

Allowed:
Body Params

A single JSON-RPC 2.0 request object, or an array of them for a batch.

A JSON-RPC 2.0 request. Omit id to send a notification: it is executed and billed, but returns no response.

string
enum
required

Protocol version. Must be exactly 2.0.

Allowed:

Correlation identifier echoed in the response. A string, a number, or null. Omit entirely to send a notification.

string
required

JSON-RPC method name. Availability depends on your package tier, the chain, and the transport.

params

Method parameters, as an array or an object. Omit when the method takes none.

Responses

204

The request contained only notifications, so there is no response body. The work was still executed and billed.

Updated about 2 months ago

Did this page help you?
Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated about 2 months ago

Did this page help you?