RouteMesh

https://routeme.sh/docs
Admin
RouteMesh is a multi-provider blockchain RPC aggregator and router that provides unified access to...
Tokens:47,107
Snippets:327
Trust Score:5.1
Update:1 month ago
Show doc for...
Tokens:
Raw
### Example error response for -32005 (query too dense)

Source: https://routeme.sh/docs/intro/rpc-error-codes

Example JSON-RPC error response for code -32005, indicating the query exceeds max results and suggesting a maximum of 1025 blocks.

```json
{
  "jsonrpc": "2.0",
  "id": 2,
  "error": {
    "code": -32005,
    "message": "query exceeds max results; try a block range of at most 1025 blocks"
  }
}
```

--------------------------------

### Service Health Response Example

Source: https://routeme.sh/docs/api-reference

The expected JSON response when the service is healthy.

```json
{
  "success": true,
  "message": "The service is ready to serve requests"
}
```

--------------------------------

### GET /provider/plans

Source: https://routeme.sh/docs/api-reference/provider/list-my-plans

Retrieves a list of pricing plans for the authenticated provider. Returns an empty array if no plans are associated with the provider.

```APIDOC
## GET /provider/plans

### Description
Returns the authenticated provider's pricing plans, or an empty array when the provider has none. Plan creation and pricing edits remain admin-managed.

### Method
GET

### Endpoint
https://api.routeme.sh/provider/plans

### Response
#### Success Response (200)
- **Array** (ProviderPlan) - List of plans or empty array

#### Error Responses
- **401** - Unauthorized
- **403** - Provider not resolved - token's customer is not linked to a provider
- **500** - Internal server error
```

--------------------------------

### Check Service Health with Go

Source: https://routeme.sh/docs/api-reference

Use the net/http package to perform a GET request to the health endpoint.

```go
package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.routeme.sh/health"

	req, _ := http.NewRequest("GET", url, nil)

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}
```

--------------------------------

### GET /chains/ws

Source: https://routeme.sh/docs/intro/websockets

Retrieves the list of chains currently supported over WebSocket subscriptions.

```APIDOC
## GET /chains/ws

### Description
Returns the set of chains currently supported over WebSocket connections. Use this to discover available chains.

### Method
GET

### Endpoint
GET /chains/ws

### Response
- **Response** - Contains a list of supported chains (not specified in source).
```

--------------------------------

### Check Service Health with Java

Source: https://routeme.sh/docs/api-reference

Use the Unirest library to perform a GET request to the health endpoint.

```java
HttpResponse<String> response = Unirest.get("https://api.routeme.sh/health")
  .asString();
```

--------------------------------

### GET /v1/usage

Source: https://routeme.sh/docs/api-reference/usage/get-usage-data

Retrieves usage data for a given customer within a period, with optional grouping and breakdown.

```APIDOC
## GET /v1/usage

### Description
Retrieves usage data for a customer within a specified period, providing totals and various breakdowns.

### Method
GET

### Endpoint
/v1/usage

### Parameters
#### Query Parameters
- **customer_id** (string) - Required - The customer identifier.
- **period[from]** (string, date-time) - Required - Start of the period.
- **period[to]** (string, date-time) - Required - End of the period.
- **group_by** (string, comma-separated) - Optional - Group the usage data by fields such as chain_id, api_key_id, method, scenario, day.
- **chain_id** (string) - Optional - Filter by chain ID.
- **api_key_id** (string) - Optional - Filter by API key ID.
- **method** (string) - Optional - Filter by RPC method.
- **scenario** (string) - Optional - Filter by routing scenario.
- **page** (integer) - Optional - Pagination page number.
- **per_page** (integer) - Optional - Items per page.

### Response
#### Success Response (200)
- **customer_id** (string) - The customer identifier.
- **period** (object) - The requested period with `from` and `to` date-time fields.
- **summary** (object) - Summary of usage with `credits_consumed` (number), `request_count` (integer), `credits_per_request` (number).
- **balance** (object) - Current credit balance with `credits` (number) and `as_of` (date-time).
- **by_chain** (array) - Per-chain breakdown. Each item contains `chain_id` (string), `credits_consumed` (number), `request_count` (integer).
- **by_api_key** (array) - Per-API-key breakdown. Each item contains `api_key_id` (integer), `name` (string, nullable), `key_hint` (string), `credits_consumed` (number), `request_count` (integer).
- **by_api_key_chain** (array) - Per-API-key, per-chain breakdown. Each item contains `api_key_id` (integer), `name` (string, nullable), `key_hint` (string), `chain_id` (string), `credits_consumed` (number), `request_count` (integer).
- **top_methods** (array) - Top RPC methods by spend. Each item contains `method` (string), `credits_consumed` (number), `request_count` (integer).
- **time_series** (array) - Time-bucketed usage data. Each item contains `bucket` (date-time), `credits_consumed` (number), `request_count` (integer).
- **by_scenario** (array) - Usage by routing scenario. Each item contains `scenario` (string), `credits_consumed` (number), `request_count` (integer).
- **groups** (array) - Grouped results when `group_by` specified. Each item contains `api_key_id`, `name`, `key_hint`, `chain_id`, `method`, `scenario`, `day` (all nullable), `credits_consumed` (number), `request_count` (integer).

#### Response Example
{
  "customer_id": "customer123",
  "period": {
    "from": "2025-01-01T00:00:00Z",
    "to": "2025-01-31T23:59:59Z"
  },
  "summary": {
    "credits_consumed": 123.45,
    "request_count": 1234,
    "credits_per_request": 0.1
  },
  "balance": {
    "credits": 500.0,
    "as_of": "2025-01-31T23:59:59Z"
  },
  "by_chain": [
    {
      "chain_id": "1",
      "credits_consumed": 10.0,
      "request_count": 100
    }
  ],
  "by_api_key": [
    {
      "api_key_id": 1,
      "name": "my key",
      "key_hint": "rm_a…456",
      "credits_consumed": 10.0,
      "request_count": 100
    }
  ],
  "by_api_key_chain": [
    {
      "api_key_id": 1,
      "name": "my key",
      "key_hint": "rm_a…456",
      "chain_id": "1",
      "credits_consumed": 10.0,
      "request_count": 100
    }
  ],
  "top_methods": [
    {
      "method": "eth_call",
      "credits_consumed": 5.0,
      "request_count": 50
    }
  ],
  "time_series": [
    {
      "bucket": "2025-01-01T00:00:00Z",
      "credits_consumed": 1.0,
      "request_count": 10
    }
  ],
  "by_scenario": [
    {
      "scenario": "direct",
      "credits_consumed": 5.0,
      "request_count": 50
    }
  ],
  "groups": [
    {
      "api_key_id": 1,
      "name": "my key",
      "key_hint": "rm_a…456",
      "chain_id": "1",
      "method": "eth_call",
      "scenario": "direct",
      "day": "2025-01-01",
      "credits_consumed": 5.0,
      "request_count": 50
    }
  ]
}
```

### Error Handling
- **400 Bad Request** - Invalid parameters or missing required fields.
- **401 Unauthorized** - Missing or invalid authentication.
- **404 Not Found** - Customer not found.
- **429 Too Many Requests** - Rate limit exceeded.
- **500 Internal Server Error** - Unexpected server error.
```

--------------------------------

### Make your first RPC request with curl

Source: https://routeme.sh/docs/intro/quick-start

Replace your existing RPC endpoint with RouteMesh. Use a supported chain_id (e.g., 1 for Ethereum) and your API key. The URL scheme is POST /rpc/{chain_id}/{api_key}.

```bash
curl -X POST https://lb.routeme.sh/rpc/{chain_id}/{api_key} \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'
```

--------------------------------

### OpenAPI spec for GET /chains/rpc

Source: https://routeme.sh/docs/api-reference/chains/list-supported-rpc-chains

OpenAPI specification for the GET /chains/rpc endpoint. It defines the response schema (array of ChainInfo objects) and example response with chain_id and name fields. The endpoint is public, requires no authentication, and returns an empty array when no chains are supported.

```yaml
openapi: 3.0.0
info:
  title: RouteMesh API
  version: 1.0.0
  description: >-
    HTTP API for routing JSON-RPC requests across providers, managing API keys,
    and viewing usage.
  license:
    name: Proprietary
    url: https://routeme.sh
servers:
  - url: https://api.routeme.sh
    description: API server — health, chains, API keys, usage, and public submissions
  - url: https://lb.routeme.sh
    description: RPC router (primary load balancer)
  - url: https://lb2.routeme.sh
    description: RPC router (AWS backup load balancer)
security: []
tags:
  - name: RPC
    description: Forward JSON-RPC requests to the router.
  - name: Chains
    description: Discover supported chains.
  - name: Submissions
    description: Public chain and node listing requests (rate-limited per IP).
  - name: API Keys
    description: Manage your API keys for self-service access.
  - name: Usage
    description: View your usage and billing data.
  - name: Pricing
    description: >-
      Current RPC route and websocket notification prices (public,
      rate-limited).
  - name: Health
    description: Service health checks.
  - name: Provider
    description: >-
      Provider-scoped management endpoints for managing node plans, methods, and
      nodes. Authenticated with a management token whose customer is linked to a
      provider.
paths:
  /chains/rpc:
    servers:
      - url: https://api.routeme.sh
    get:
      tags:
        - Chains
      summary: List supported RPC chains
      description: >-
        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.
      operationId: getChainsRpc
      responses:
        '200':
          description: Supported RPC chains
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/ChainInfo'
              example:
                - chain_id: '1'
                  name: Ethereum Mainnet
                - chain_id: '8453'
                  name: Base
        '500':
          description: Internal server error
components:
  schemas:
    ChainInfo:
      type: object
      properties:
        chain_id:
          type: string
          description: Numeric chain ID (e.g. "1", "137", "8453").
        name:
          type: string
          description: Human-readable chain name.
      required:
        - chain_id
        - name
      additionalProperties: false
```

--------------------------------

### OpenAPI specification for /health endpoint

Source: https://routeme.sh/docs/api-reference/health/service-health

OpenAPI 3.0.0 specification for the GET /health endpoint. It defines the server as https://api.routeme.sh and the response schema with success and message properties. The example response shows success: true and message: The service is ready to serve requests.

```yaml
openapi: 3.0.0
info:
  title: RouteMesh API
  version: 1.0.0
  description: >-
    HTTP API for routing JSON-RPC requests across providers, managing API keys,
    and viewing usage.
  license:
    name: Proprietary
    url: https://routeme.sh
servers:
  - url: https://api.routeme.sh
    description: API server — health, chains, API keys, usage, and public submissions
  - url: https://lb.routeme.sh
    description: RPC router (primary load balancer)
  - url: https://lb2.routeme.sh
    description: RPC router (AWS backup load balancer)
security: []
tags:
  - name: RPC
    description: Forward JSON-RPC requests to the router.
  - name: Chains
    description: Discover supported chains.
  - name: Submissions
    description: Public chain and node listing requests (rate-limited per IP).
  - name: API Keys
    description: Manage your API keys for self-service access.
  - name: Usage
    description: View your usage and billing data.
  - name: Pricing
    description: >-
      Current RPC route and websocket notification prices (public,
      rate-limited).
  - name: Health
    description: Service health checks.
  - name: Provider
    description: >-
      Provider-scoped management endpoints for managing node plans, methods, and
      nodes. Authenticated with a management token whose customer is linked to a
      provider.
paths:
  /health:
    servers:
      - url: https://api.routeme.sh
    get:
      tags:
        - Health
      summary: Service health
      description: Public health endpoint used by load balancers and uptime checks.
      operationId: getHealth
      responses:
        '200':
          description: Service is healthy and serving requests
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  message:
                    type: string
                required:
                  - success
                  - message
                additionalProperties: false
              example:
                success: true
                message: The service is ready to serve requests

```

--------------------------------

### GET /provider/plans/{planId}/methods

Source: https://routeme.sh/docs/api-reference/provider/list-a-plans-rpc-methods

Lists the RPC method rows configured for a plan owned by the authenticated provider. Returns an empty array when the plan has no methods. Plans not owned by the caller's provider are reported as 404.

```APIDOC
## GET /provider/plans/{planId}/methods

### Description
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.

### Method
GET

### Endpoint
https://api.routeme.sh/provider/plans/{planId}/methods

### Parameters
#### Path Parameters
- **planId** (integer) - Required - Numeric plan ID.

### Authentication
- **X-Api-Key** (header) - Required - Management token from the RouteMesh dashboard (Settings → Management Tokens). Tokens are prefixed rmtm_ and scoped to your account.

### Response
#### Success Response (200)
- **array of ProviderPlanMethod** - List of method rows or empty array

Each ProviderPlanMethod object has the following properties:
- **method** (string) - RPC method name, e.g. eth_blockNumber.
- **vm** (string) - Virtual machine type, e.g. evm.
- **node_target_type** (string) - Node target type the method routes to.
- **cost** (integer) - Credit cost per call (0 = free).
- **rate_limit** (integer, nullable) - Optional per-call rate limit.
- **rate_limit_interval_sec** (integer, nullable) - Rate limit window in seconds.
- **chain_id** (string, nullable) - Chain this cost applies to; null/omitted for all chains.

#### Response Example
```json
[
  {
    "method": "eth_blockNumber",
    "vm": "evm",
    "node_target_type": "full",
    "cost": 1,
    "rate_limit": 100,
    "rate_limit_interval_sec": 60,
    "chain_id": "1"
  }
]
```

#### Error Responses
- **400** - Invalid plan id
- **401** - Unauthorized
- **403** - Provider not resolved
- **404** - Plan not found (or not owned by the caller's provider)
- **500** - Internal server error
```

--------------------------------

### rpc_get_fee_data

Source: https://routeme.sh/docs/intro/mcp-server

Gets current gas price, max priority fee, and a one-block fee history. Use this to get fee information for the chain.

```APIDOC
## rpc_get_fee_data

### Description
Gets current gas price, max priority fee, and a one-block fee history. Use this to get fee information for the chain.

### Parameters
- **chainId** (number) - Required - Numeric EVM chain ID.

```

--------------------------------

### GET /pricing/rpc

Source: https://routeme.sh/docs/api-reference/pricing/list-rpc-route-prices

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.

```APIDOC
## GET /pricing/rpc

### Description
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.

### Method
GET

### Endpoint
https://api.routeme.sh/pricing/rpc

### Parameters
#### Query Parameters
- **vm** (string) - Optional - Filter by virtual machine type (e.g. evm). Example: evm
- **chain_id** (string) - Optional - Filter by chain ID (e.g. 1, 137, 8453). Example: '1'
- **method** (string) - Optional - Filter by JSON-RPC method (e.g. eth_blockNumber). Example: eth_blockNumber
- **routing_strategy** (string) - Optional - Filter by routing strategy. Enum: economy, performance. Example: economy

### Response
#### Success Response (200)
- **vm** (string) - Virtual machine type (e.g. "evm").
- **chain_id** (string) - Numeric chain ID (e.g. "1", "137", "8453").
- **method** (string) - JSON-RPC method name (e.g. eth_blockNumber).
- **routing_strategy** (string) - Routing strategy the price applies to. Enum: economy, performance.
- **price_per_million** (number) - Price per one million requests.

#### Response Example
[
  {
    "vm": "evm",
    "chain_id": "1",
    "method": "eth_blockNumber",
    "routing_strategy": "economy",
    "price_per_million": 3
  }
]

#### Error Responses
- **429** - Rate limit exceeded (per-IP limit; default 30 requests per 60 seconds)
- **503** - Pricing data temporarily unavailable
```

--------------------------------

### Configure Cursor MCP server

Source: https://routeme.sh/docs/intro/mcp-server

Add this configuration to your ~/.cursor/mcp.json file to enable the RouteMesh MCP server in Cursor.

```json
{
  "mcpServers": {
    "routemesh": {
      "command": "npx",
      "args": ["-y", "@routemesh/mcp"],
      "env": {
        "ROUTEMESH_API_KEY": "your_routemesh_api_key"
      }
    }
  }
}
```

--------------------------------

### POST /provider/plans/{planId}/methods

Source: https://routeme.sh/docs/api-reference/provider/add-methods-to-a-plan

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

```APIDOC
## POST /provider/plans/{planId}/methods

### Description
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).

### Method
POST

### Endpoint
https://api.routeme.sh/provider/plans/{planId}/methods

### Parameters
#### Path Parameters
- **planId** (integer) - Required - Numeric plan ID.

#### Request Body
- **methods** (array) - Required - Array of method definitions (1-500 items).
  - **method** (string) - Required - The RPC method name.
  - **vm** (string) - Required - The virtual machine type.
  - **node_target_type** (string) - Required - The node target type.
  - **cost** (integer) - Required - The cost of the method (minimum 0).
  - **rate_limit** (integer) - Optional - Rate limit (minimum 0).
  - **rate_limit_interval_sec** (integer) - Optional - Rate limit interval in seconds (minimum 0).
  - **chain_id** (string) - Optional - Chain ID (nullable).

### Request Example
{
  "methods": [
    {
      "method": "eth_blockNumber",
      "vm": "evm",
      "node_target_type": "public",
      "cost": 1,
      "rate_limit": 100,
      "rate_limit_interval_sec": 60,
      "chain_id": "1"
    }
  ]
}

### Response
#### Success Response (201)
- Returns a plain-text success message.

#### Response Example
Plan methods inserted.

### Error Responses
- **400** - Invalid plan id, request body, or validation failure
- **401** - Unauthorized
- **403** - Provider not resolved
- **404** - Plan not found (or not owned by the caller's provider)
- **500** - Internal server error

### Authentication
- **MgmtKeyAuth** - API key in header `X-Api-Key`. Management token from the RouteMesh dashboard (Settings → Management Tokens). Tokens are prefixed `rmtm_` and scoped to your account.
```

--------------------------------

### Example error response for -32602 (block range too large)

Source: https://routeme.sh/docs/intro/rpc-error-codes

Example JSON-RPC error response for code -32602, indicating the block range is too large and suggesting a maximum of 10000 blocks.

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32602,
    "message": "block range too large; try a block range of at most 10000 blocks"
  }
}
```

--------------------------------

### POST /nodes/requests

Source: https://routeme.sh/docs/api-reference/submissions/submit-node-request

Submits a request to list a new RPC node. The request must include a name, URL, VM type, and email. The URL must be HTTPS and pass EVM screening. Rate-limited to 3 submissions per IP per day unless an admin or agent management token is provided via X-Api-Key.

```APIDOC
## POST /nodes/requests

### Description
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.

### Method
POST

### Endpoint
https://api.routeme.sh/nodes/requests

### Parameters
#### Request Body
- **name** (string) - Required - Name of the node.
- **url** (string, uri) - Required - HTTPS RPC endpoint URL.
- **vm** (string, enum: evm) - Required - Virtual machine type (currently only evm).
- **email** (string, email) - Required - Contact email.
- **privacy_policy_url** (string, uri, nullable) - Optional - URL to privacy policy.
- **notes** (string, nullable) - Optional - Additional notes.

### Request Example
{
  "name": "My Node",
  "url": "https://rpc.example.com",
  "vm": "evm",
  "email": "admin@example.com",
  "privacy_policy_url": "https://example.com/privacy",
  "notes": "Optional notes"
}

### Response
#### Success Response (201)
- **id** (integer) - Created request ID.

#### Response Example
{
  "id": 123
}

### Error Responses
- **400** - Validation or screening failure
- **401** - Unauthorized (invalid X-Api-Key when provided)
- **409** - Node URL already exists or pending request exists
- **429** - Per-IP daily submission limit exceeded
- **500** - Internal server error
```

--------------------------------

### OpenAPI specification for GET /api-keys

Source: https://routeme.sh/docs/api-reference/api-keys/list-my-api-keys

Defines the GET /api-keys endpoint, its response schema ApiKeyResponse, and the MgmtKeyAuth security scheme. The response excludes the secret key, and authentication is via the X-Api-Key header with a management token prefixed rmtm_. This is the base OpenAPI document used by the endpoint.

```yaml
openapi: 3.0.0
info:
  title: RouteMesh API
  version: 1.0.0
  description: >-
    HTTP API for routing JSON-RPC requests across providers, managing API keys,
    and viewing usage.
  license:
    name: Proprietary
    url: https://routeme.sh
servers:
  - url: https://api.routeme.sh
    description: API server — health, chains, API keys, usage, and public submissions
  - url: https://lb.routeme.sh
    description: RPC router (primary load balancer)
  - url: https://lb2.routeme.sh
    description: RPC router (AWS backup load balancer)
security: []
tags:
  - name: RPC
    description: Forward JSON-RPC requests to the router.
  - name: Chains
    description: Discover supported chains.
  - name: Submissions
    description: Public chain and node listing requests (rate-limited per IP).
  - name: API Keys
    description: Manage your API keys for self-service access.
  - name: Usage
    description: View your usage and billing data.
  - name: Pricing
    description: >-
      Current RPC route and websocket notification prices (public,
      rate-limited).
  - name: Health
    description: Service health checks.
  - name: Provider
    description: >-
      Provider-scoped management endpoints for managing node plans, methods, and
      nodes. Authenticated with a management token whose customer is linked to a
      provider.
paths:
  /api-keys:
    servers:
      - url: https://api.routeme.sh
    get:
      tags:
        - API Keys
      summary: List my API keys
      description: >-
        Returns the authenticated customer's API keys. Excludes the secret key
        value; use X-Hint for identification.
      operationId: listMyApiKeys
      responses:
        '200':
          description: List of API keys
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/ApiKeyResponse'
        '401':
          description: Unauthorized
      security:
        - MgmtKeyAuth: []
components:
  schemas:
    ApiKeyResponse:
      type: object
      properties:
        id:
          type: integer
          description: Internal key ID (for filtering /usage).
        name:
          type: string
          nullable: true
          description: Friendly name.
        active:
          type: boolean
          description: Whether the key is active.
        allowed_domains:
          type: array
          items:
            type: string
          description: Allowed domains.
        routing_strategy:
          type: string
          enum:
            - economy
            - performance
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
      required:
        - id
        - name
        - active
        - allowed_domains
        - routing_strategy
        - created_at
        - updated_at
      additionalProperties: false
  securitySchemes:
    MgmtKeyAuth:
      type: apiKey
      in: header
      name: X-Api-Key
      description: >-
        Management token from the RouteMesh dashboard (Settings → Management
        Tokens). Required for customer API endpoints (/api-keys, /usage). Tokens
        are prefixed rmtm_ and scoped to your account. Authenticate by passing
        the token in the X-Api-Key header. Separate from RPC service keys (rm_),
        which authenticate dApp traffic to the routing layer.
```

--------------------------------

### POST /chains/requests

Source: https://routeme.sh/docs/api-reference/submissions/submit-chain-request

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.

```APIDOC
## POST /chains/requests

### Description
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.

### Method
POST

### Endpoint
https://api.routeme.sh/chains/requests

### Parameters
#### Request Body
- **name** (string) - Required - Name of the chain.
- **chain_id** (string) - Required - Decimal or 0x-prefixed chain ID (e.g. "137").
- **short_name** (string) - Required - Short name of the chain.
- **native_currency_name** (string) - Required - Name of the native currency.
- **native_currency_decimals** (integer) - Optional - Number of decimals for the native currency. Default: 0. Minimum: 0.
- **info_url** (string, uri) - Required - URL with information about the chain.
- **icon_url** (string, uri) - Optional - URL for the chain icon. Can be null.
- **rpc_urls** (array of string, uri) - Required - HTTPS RPC URLs to screen (max 5). At least one must pass screening. Min items: 1, max items: 5.
- **explorer_urls** (array of string, uri) - Optional - URLs of block explorers for the chain.
- **requestor_email** (string, email) - Required - Email of the requester.
- **requestor_name** (string) - Required - Name of the requester.

### Request Example
{
  "name": "Example Chain",
  "chain_id": "137",
  "short_name": "EXC",
  "native_currency_name": "Example Coin",
  "native_currency_decimals": 18,
  "info_url": "https://example.com",
  "icon_url": "https://example.com/icon.png",
  "rpc_urls": ["https://rpc.example.com"],
  "explorer_urls": ["https://explorer.example.com"],
  "requestor_email": "user@example.com",
  "requestor_name": "John Doe"
}

### Response
#### Success Response (201)
- **id** (integer) - Created request ID.

#### Response Example
{
  "id": 123
}

#### Error Responses
- **400** - Validation or screening failure
- **401** - Unauthorized (invalid X-Api-Key when provided)
- **409** - Chain already exists or pending request exists for this chain ID
- **429** - Per-IP daily submission limit exceeded
- **500** - Internal server error
```

--------------------------------

### rpc_get_transaction

Source: https://routeme.sh/docs/intro/mcp-server

Fetches a transaction by hash. Use this to get transaction details.

```APIDOC
## rpc_get_transaction

### Description
Fetches a transaction by hash. Use this to get transaction details.

### Parameters
- **chainId** (number) - Required - Numeric EVM chain ID.
- **txHash** (string) - Required - Transaction hash.

```

--------------------------------

### rpc_get_transaction_receipt

Source: https://routeme.sh/docs/intro/mcp-server

Fetches a transaction receipt by hash. Use this to get receipt details.

```APIDOC
## rpc_get_transaction_receipt

### Description
Fetches a transaction receipt by hash. Use this to get receipt details.

### Parameters
- **chainId** (number) - Required - Numeric EVM chain ID.
- **txHash** (string) - Required - Transaction hash.

```

--------------------------------

### OpenAPI definition for adding methods to a plan

Source: https://routeme.sh/docs/api-reference/provider/add-methods-to-a-plan

The OpenAPI specification for the insertProviderPlanMethods operation, including the required request body schema and security requirements.

```yaml
openapi: 3.0.0
info:
  title: RouteMesh API
  version: 1.0.0
  description: >-
    HTTP API for routing JSON-RPC requests across providers, managing API keys,
    and viewing usage.
  license:
    name: Proprietary
    url: https://routeme.sh
servers:
  - url: https://api.routeme.sh
    description: API server — health, chains, API keys, usage, and public submissions
  - url: https://lb.routeme.sh
    description: RPC router (primary load balancer)
  - url: https://lb2.routeme.sh
    description: RPC router (AWS backup load balancer)
security: []
tags:
  - name: RPC
    description: Forward JSON-RPC requests to the router.
  - name: Chains
    description: Discover supported chains.
  - name: Submissions
    description: Public chain and node listing requests (rate-limited per IP).
  - name: API Keys
    description: Manage your API keys for self-service access.
  - name: Usage
    description: View your usage and billing data.
  - name: Pricing
    description: >-
      Current RPC route and websocket notification prices (public,
      rate-limited).
  - name: Health
    description: Service health checks.
  - name: Provider
    description: >-
      Provider-scoped management endpoints for managing node plans, methods, and
      nodes. Authenticated with a management token whose customer is linked to a
      provider.
paths:
  /provider/plans/{planId}/methods:
    post:
      tags:
        - Provider
      summary: Add methods to a plan
      description: >-
        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).
      operationId: insertProviderPlanMethods
      parameters:
        - name: planId
          in: path
          required: true
          schema:
            type: integer
          description: Numeric plan ID.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ProviderPlanMethodsInput'
      responses:
        '201':
          description: Plan methods inserted. Returns a plain-text success message.
        '400':
          description: Invalid plan id, request body, or validation failure
        '401':
          description: Unauthorized
        '403':
          description: Provider not resolved
        '404':
          description: Plan not found (or not owned by the caller's provider)
        '500':
          description: Internal server error
      security:
        - MgmtKeyAuth: []
      servers:
        - url: https://api.routeme.sh
components:
  schemas:
    ProviderPlanMethodsInput:
      type: object
      properties:
        methods:
          type: array
          minItems: 1
          maxItems: 500
          items:
            $ref: '#/components/schemas/ProviderPlanMethodInput'
      required:
        - methods
    ProviderPlanMethodInput:
      type: object
      properties:
        method:
          type: string
        vm:
          type: string
        node_target_type:
          type: string
        cost:
          type: integer
          minimum: 0
        rate_limit:
          type: integer
          minimum: 0
        rate_limit_interval_sec:
          type: integer
          minimum: 0
        chain_id:
          type: string
          nullable: true
      required:
        - method
        - vm
        - node_target_type
        - cost
  securitySchemes:
    MgmtKeyAuth:
      type: apiKey
      in: header
      name: X-Api-Key
      description: >-
        Management token from the RouteMesh dashboard (Settings → Management
        Tokens). Required for customer API endpoints (/api-keys, /usage). Tokens
        are prefixed rmtm_ and scoped to your account. Authenticate by passing
        the token in the X-Api-Key header. Separate from RPC service keys (rm_),
        which authenticate dApp traffic to the routing layer.
```
Tokens:
Raw