# RouteMesh

- [Getting Started](https://routeme.sh/docs/intro/getting-started.md)
- [Quick Start](https://routeme.sh/docs/intro/quick-start.md)
- [How it Works](https://routeme.sh/docs/intro/how-it-works.md)
- [Pricing Model](https://routeme.sh/docs/intro/pricing-model.md)
- [Updates](https://routeme.sh/docs/intro/updates.md)
- [Routing Strategies](https://routeme.sh/docs/intro/routing-strategies.md)
- [Data Quality](https://routeme.sh/docs/intro/data-quality.md)
- [Redundancy](https://routeme.sh/docs/intro/redundancy.md)
- [Request Behavior](https://routeme.sh/docs/intro/request-behavior.md)
- [WebSocket API](https://routeme.sh/docs/intro/websockets.md)
- [Debugging](https://routeme.sh/docs/intro/debugging.md)
- [MCP Server](https://routeme.sh/docs/intro/mcp-server.md)
- [Network Support](https://routeme.sh/docs/intro/network-support.md)
- [RPC Error Codes](https://routeme.sh/docs/intro/rpc-error-codes.md)
- [Overview](https://routeme.sh/docs/provider/overview.md)
- [Onboarding](https://routeme.sh/docs/provider/onboarding.md): How to join RouteMesh as a node provider — create your account and get connected.
- [Dashboard](https://routeme.sh/docs/provider/dashboard.md)
- [Routing](https://routeme.sh/docs/provider/pricing.md)
- [Plans](https://routeme.sh/docs/provider/plans.md)
- [Methods](https://routeme.sh/docs/provider/methods.md)
- [Nodes](https://routeme.sh/docs/provider/nodes.md)
- [Data quality](https://routeme.sh/docs/provider/data-quality.md)
- [Replay checks](https://routeme.sh/docs/provider/replay-checks.md)
- [Lag checks](https://routeme.sh/docs/provider/lag-checks.md)
- [When checks fail](https://routeme.sh/docs/provider/quality-checks-recovery.md)
- [Inspect](https://routeme.sh/docs/provider/inspect.md)
- [Market Share](https://routeme.sh/docs/provider/market-share.md)
- [Service health](https://routeme.sh/docs/api-reference/health/service-health.md): Public health endpoint used by load balancers and uptime checks.
- [List supported RPC chains](https://routeme.sh/docs/api-reference/chains/list-supported-rpc-chains.md): Returns the EVM chains supported over HTTP RPC, sorted by chain ID. Public endpoint, no authentication required. Returns an empty array when no chains are supported.
- [List supported WebSocket chains](https://routeme.sh/docs/api-reference/chains/list-supported-websocket-chains.md): Returns the EVM chains supported over WebSocket, sorted by chain ID. Public endpoint, no authentication required. Returns an empty array when no chains are supported.
- [JSON-RPC proxy](https://routeme.sh/docs/api-reference/rpc/json-rpc-proxy.md): Send a single JSON-RPC request or a JSON-RPC batch (array). Replace {apiKey} with your actual API key.
- [Public JSON-RPC proxy (no API key)](https://routeme.sh/docs/api-reference/rpc/public-json-rpc-proxy-no-api-key.md): Send a single JSON-RPC request or a JSON-RPC batch (array) to the public, anonymous free tier. No API key required. Rate-limited per IP. For higher volume, use an API key at /rpc/{chainId}/{apiKey}.
- [List my API keys](https://routeme.sh/docs/api-reference/api-keys/list-my-api-keys.md): Returns the authenticated customer's API keys. Excludes the secret key value; use X-Hint for identification.
- [Create API key](https://routeme.sh/docs/api-reference/api-keys/create-api-key.md): Creates a new API key for the authenticated customer. The secret key value is returned once — store it securely.
- [Update API key](https://routeme.sh/docs/api-reference/api-keys/update-api-key.md): Partially updates one of the authenticated customer's API keys by numeric ID. Omitted fields leave the stored value unchanged. Use the id from GET /api-keys.
- [Get usage data](https://routeme.sh/docs/api-reference/usage/get-usage-data.md): Returns customer-scoped usage aggregates. Supports filtering by time range, chain, API key, grouping, and granularity. By default returns summary and balance.
- [Submit chain request](https://routeme.sh/docs/api-reference/submissions/submit-chain-request.md): Public endpoint to request listing a new chain. Rate-limited to 5 submissions per IP per day. Optional X-Api-Key with an admin or agent management token skips the per-IP limit. Submitted RPC URLs are screened; at least one must qualify.
- [Submit node request](https://routeme.sh/docs/api-reference/submissions/submit-node-request.md): Public endpoint to request listing a new RPC node. Rate-limited to 3 submissions per IP per day. Optional X-Api-Key with an admin or agent management token skips the per-IP limit. The node URL must be HTTPS and pass mandatory EVM screening.
- [List RPC route prices](https://routeme.sh/docs/api-reference/pricing/list-rpc-route-prices.md): Public endpoint returning current RPC route prices for each vm, chain ID, method, and routing strategy combination. No authentication required. Rate-limited per IP (default 30 requests per 60 seconds). Empty results return an empty JSON array.
- [List websocket notification prices](https://routeme.sh/docs/api-reference/pricing/list-websocket-notification-prices.md): Public endpoint returning current websocket notification prices per chain ID and subscription type. No authentication required. Rate-limited per IP (default 30 requests per 60 seconds). Empty results return an empty JSON array.
- [List my plans](https://routeme.sh/docs/api-reference/provider/list-my-plans.md): Returns the authenticated provider's pricing plans, or an empty array when the provider has none. Plan creation and pricing edits remain admin-managed.
- [List a plan's RPC methods](https://routeme.sh/docs/api-reference/provider/list-a-plans-rpc-methods.md): Returns the RPC method rows configured for one of the authenticated provider's plans. Returns an empty array when the plan has no methods. Plans not owned by the caller's provider are reported as 404.
- [Add methods to a plan](https://routeme.sh/docs/api-reference/provider/add-methods-to-a-plan.md): Appends RPC method rows (1-500) to one of the authenticated provider's plans. The plan must be owned by the caller's provider (otherwise 404).
- [Get a node's sync status](https://routeme.sh/docs/api-reference/provider/get-a-nodes-sync-status.md): Returns the synchronization status of one of the authenticated provider's nodes. Nodes not owned by the caller's provider are reported as 404.
- [Create or update an HTTP node](https://routeme.sh/docs/api-reference/provider/create-or-update-an-http-node.md): Creates or updates an HTTP RPC node for one of the authenticated provider's plans. The URL must be a public http(s) endpoint (loopback, private, and link-local hosts are rejected). The node is screened before persistence; the request fails with 400 when a mandatory screening test does not pass. Retu…
- [Create or update a WebSocket node](https://routeme.sh/docs/api-reference/provider/create-or-update-a-websocket-node.md): Creates or updates a WebSocket RPC node for one of the authenticated provider's plans. The URL must be a public wss:// endpoint (loopback, private, and link-local hosts are rejected) that accepts eth_subscribe("newHeads"); the server dials the node to verify before persisting. Returns the upserted n…
- [Enable, disable, or delete a node](https://routeme.sh/docs/api-reference/provider/enable-disable-or-delete-a-node.md): Sets the status of one of the authenticated provider's nodes to enable, disable, or delete (hide). Allowed statuses: healthy, disabled by provider, provider-deleted.

## OpenAPI Specs

- [openapi](/docs/api-reference/openapi.json)