1.9k★by kermankohli
routemesh-rpc – OpenClaw Skill
routemesh-rpc is an OpenClaw Skills integration for coding workflows. 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.
Skill Snapshot
| name | routemesh-rpc |
| description | 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. OpenClaw Skills integration. |
| owner | kermankohli |
| repository | kermankohli/routemesh-crypto-rpc |
| language | Markdown |
| license | MIT |
| topics | |
| security | L1 |
| install | openclaw add @kermankohli/routemesh-crypto-rpc |
| last updated | Feb 7, 2026 |
Maintainer

name: routemesh-rpc description: 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. metadata: {"openclaw":{"homepage":"https://routeme.sh","requires":{"anyBins":["python3","python"]},"primaryEnv":"ROUTEMESH_API_KEY"}}
RouteMesh RPC (JSON-RPC)
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, optionalparams)
Quick start
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 '[]'
Usage pattern
Prefer calling via the helper script so output stays consistent and you don’t accidentally break JSON encoding.
Script arguments
--chain-id: EVM chain id (string or int, e.g.1,137,42161)--api-key: optional; falls back toROUTEMESH_API_KEY--method: JSON-RPC method (e.g.eth_getBlockByNumber,eth_call)--params: JSON string for params (default[])--url: optional base URL (defaulthttps://lb.routeme.sh)
Common examples
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"]'
Notes / error handling
- RouteMesh returns standard JSON-RPC responses (
resultorerror) 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_KEYout of logs, issues, and commits.
No README available.
Permissions & Security
Security level L1: Low-risk skills with minimal permissions. Review inputs and outputs before running in production.
Requirements
- OpenClaw CLI installed and configured.
- Language: Markdown
- License: MIT
- Topics:
FAQ
How do I install routemesh-rpc?
Run openclaw add @kermankohli/routemesh-crypto-rpc in your terminal. This installs routemesh-rpc into your OpenClaw Skills catalog.
Does this skill run locally or in the cloud?
OpenClaw Skills execute locally by default. Review the SKILL.md and permissions before running any skill.
Where can I verify the source code?
The source repository is available at https://github.com/openclaw/skills/tree/main/skills/kermankohli/routemesh-crypto-rpc. Review commits and README documentation before installing.
