> ## Documentation Index
> Fetch the complete documentation index at: https://routeme.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# List supported RPC chains

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



## OpenAPI

````yaml /api-reference/openapi.json get /chains/rpc
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.
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

````