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

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



## OpenAPI

````yaml /api-reference/openapi.json post /provider/plans/{planId}/methods
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.

````