How do I install the Routemesh Rpc skill?

Run npx skillmds@latest add modbender/routemesh-rpc in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Routemesh Rpc safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Routemesh Rpc?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Routemesh Rpc free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Routemesh Rpc?

modbender (@modbender) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Routemesh Rpc by modbender — Agent Skill

Name: Routemesh Rpc
Rating: 4.5 (4 reviews)
Author: modbender

Routemesh Rpc

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.

modbender Updated Sep 9, 2026 12 repo stars

File contents

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, optional params)

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 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)

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 (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.

---name: routemesh-rpcdescription: 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.--- # 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`, optional `params`) ## Quick start Set your API key (recommended): ```bash export ROUTEMESH_API_KEY="rm_...your_key..." ``` Make a request (example: Ethereum mainnet, `eth_blockNumber`): ```bash 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 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`) ## Common examples Get the latest block (Polygon): ```bash python3 "{baseDir}/scripts/routemesh_rpc.py" \ --chain-id 137 \ --method eth_getBlockByNumber \ --params '["latest", false]' ``` Get chain id (any EVM chain): ```bash python3 "{baseDir}/scripts/routemesh_rpc.py" \ --chain-id 8453 \ --method eth_chainId \ --params '[]' ``` `eth_call` (Base). `data` must be hex-encoded calldata: ```bash 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 (`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.

Frequently asked questions