Spec Once. Generate Everything.

One spec is all you need to produce tests, docs, and client/server code for your JSON-RPC API.

{
  "openrpc": "1.2.6",
  "info": {
    "title": "Metrics RPC",
    "version": "0.1.0",
    "description": "Fetch service health metrics from any node."
  },
  "servers": [
    {
      "name": "primary",
      "url": "https://metrics.example.com/rpc"
    }
  ],
  "methods": [
    {
      "name": "metrics_getSnapshot",
      "summary": "Return current CPU, memory, and latency stats.",
      "params": [
        {
          "name": "service",
          "required": true,
          "schema": {
            "type": "string",
            "description": "Service identifier."
          }
        }
      ],
      "result": {
        "name": "snapshot",
        "schema": {
          "type": "object",
          "properties": {
            "cpu": {
              "type": "number"
            },
            "memoryMb": {
              "type": "integer"
            },
            "p95LatencyMs": {
              "type": "number"
            }
          }
        }
      }
    }
  ]
}

Why OpenRPC

A clear versioned API spec can boost developer productivity by 10x

With OpenRPC, you can go from prototype to production-grade services in hours, not weeks. You'll build discoverable, versioned APIs with JSON Schema to enforce client contracts, eliminate boilerplate, and scale faster.