Gate endpoints and requests
Gate's Endpoints page lists the networks available to the selected active RPC key. Each card shows its network name, chain ID, HTTPS URL, provider, recent request count, and a status indicator. Filters show all networks, mainnets, or testnets.
Execution endpoint
The console builds the endpoint from the discovered chain endpoint and your key:
https://{CHAIN_ENDPOINT}/{RPC_API_KEY}Copy the URL from the console. The hostname is network-specific; do not substitute the Gate console address or assume that every environment uses the same endpoint names.
Send execution requests as JSON-RPC over HTTPS:
{
"jsonrpc": "2.0",
"id": 1,
"method": "eth_blockNumber",
"params": []
}Use a unique request ID to correlate the response. Hex quantities and hex-encoded byte strings follow Ethereum JSON-RPC conventions. A successful HTTP response can still contain a JSON-RPC error.
Discover chains programmatically
The console's chain discovery uses this authenticated endpoint:
curl --fail-with-body 'https://rpc.thyme.sh/v1/chains' \
-H "apikey: $GATE_API_KEY"Set GATE_API_KEY to an active RPC key. This is a discovery request, so it uses the apikey header; the execution URL copied from the console includes the key in its path.
The response contains a chains array. The console consumes these fields:
| Field | Meaning |
|---|---|
chain | Network identifier |
endpoint | Host/path used to construct the network's execution URL |
chainId or chain_id | Numeric chain ID; the console normalizes either spelling |
blockNumber or block_number | Optional reported block height |
syncing | Whether the endpoint reports syncing |
protocols | Advertised protocol list |
provider | Provider label |
Use the response or console for current availability. Static network metadata is not a supported-chain list. The current console exposes HTTPS URLs; do not derive a WebSocket URL by changing its scheme unless that transport is explicitly available for the endpoint.
Method compatibility
These are common categories of execution RPC calls. Confirm the selected endpoint supports the method and historical depth your application requires.
| Task | Typical methods |
|---|---|
| Identify the chain and current head | eth_chainId, eth_blockNumber |
| Read state | eth_getBalance, eth_getCode, eth_getStorageAt, eth_call |
| Inspect blocks and receipts | eth_getBlockByNumber, eth_getTransactionByHash, eth_getTransactionReceipt |
| Query contract events | eth_getLogs |
| Estimate a transaction | eth_estimateGas, eth_gasPrice, eth_feeHistory |
| Broadcast an already-signed transaction | eth_sendRawTransaction |
Debug, trace, archive, pending-state, batch, and subscription capabilities are not established by a successful eth_chainId call. Validate these requirements against the actual endpoint before relying on them. For logs, query bounded block ranges and narrow by contract and topics.
Use Lift's API for its advertised ERC-4337 and paymaster methods. A Gate execution endpoint and a Lift bundler endpoint serve different RPC method sets.
Interpreting status
The console displays syncing when chain discovery reports syncing. Otherwise, it displays degraded when the recent per-chain request error ratio exceeds 2%, and operational in the remaining cases.
This combines endpoint metadata with recent workspace traffic. An operational badge with little or no traffic is not an independent availability guarantee. Verify a fresh read and the expected chain ID when diagnosing connection problems.
Sending transactions safely
Keep signing in your wallet or server account client and submit the signed transaction to the intended chain. After a submission timeout, check the known transaction hash and account nonce before replacing or creating a new transaction. Repeating a business action with a new nonce can execute it twice.
RPC access does not pay the transaction's native gas. Use your account's balance or a separately supported sponsorship path.