Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Call RouteMesh's unified JSON-RPC endpoint (lb.routeme.sh) for any EVM chainId using a helper script. Use when you need to fetch onchain data (eth_* methods), debug RPC responses, or demo RouteMesh routing for a chain/method.
Call RouteMesh's unified JSON-RPC endpoint (lb.routeme.sh) for any EVM chainId using a helper script. Use when you need to fetch onchain data (eth_* methods), debug RPC responses, or demo RouteMesh routing for a chain/method.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
This skill standardizes how to call RouteMeshβs unified RPC endpoint: Endpoint: POST https://lb.routeme.sh/rpc/{chainId}/{apiKey} Body: JSON-RPC 2.0 (jsonrpc, id, method, optional params)
Set your API key (recommended): export ROUTEMESH_API_KEY="rm_...your_key..." Make a request (example: Ethereum mainnet, eth_blockNumber): python3 "{baseDir}/scripts/routemesh_rpc.py" \ --chain-id 1 \ --method eth_blockNumber \ --params '[]'
Prefer calling via the helper script so output stays consistent and you donβt accidentally break JSON encoding.
--chain-id: EVM chain id (string or int, e.g. 1, 137, 42161) --api-key: optional; falls back to ROUTEMESH_API_KEY --method: JSON-RPC method (e.g. eth_getBlockByNumber, eth_call) --params: JSON string for params (default []) --url: optional base URL (default https://lb.routeme.sh)
Get the latest block (Polygon): python3 "{baseDir}/scripts/routemesh_rpc.py" \ --chain-id 137 \ --method eth_getBlockByNumber \ --params '["latest", false]' Get chain id (any EVM chain): python3 "{baseDir}/scripts/routemesh_rpc.py" \ --chain-id 8453 \ --method eth_chainId \ --params '[]' eth_call (Base). data must be hex-encoded calldata: python3 "{baseDir}/scripts/routemesh_rpc.py" \ --chain-id 8453 \ --method eth_call \ --params '[{"to":"0x0000000000000000000000000000000000000000","data":"0x"}, "latest"]'
RouteMesh returns standard JSON-RPC responses (result or error) and may also use HTTP error codes. If you get a JSON-RPC error.code, refer to RouteMesh RPC error code docs in this repo: docs/reference/Reference/get_new-endpoint.md. Keep ROUTEMESH_API_KEY out of logs, issues, and commits.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.