OpenAPI $ref resolver

FREE with proof-of-work · or $0.001 in USDC · POST /api/openapi-resolve-refs

Inline every local `$ref` in an OpenAPI 3.x or Swagger 2.x document so downstream tools see a self-contained spec. Send POST /api/openapi-resolve-refs with the required field spec and pay $0.001 per call over x402 or MPP, or call it free by solving a proof-of-work challenge. It returns a JSON object with spec, resolved, circular, unresolved and external.

Resolves `#/components/...` (OpenAPI) and `#/definitions/...` (Swagger) JSON-pointer refs anywhere in the document, including inside components themselves. Per-branch cycle detection: if A→B→A, the second A is left as a `$ref` and recorded under `circular`. External refs (http://, file://, ./other.yaml) are never fetched - they're reported under `external` and left as-is. Sibling keys of `$ref` (e.g. a `description` next to a `$ref`) are dropped to match JSON Schema Draft 7 / OpenAPI 3.0 semantics. Returns the dereffed spec plus `resolved` (count inlined) and arrays of any refs that couldn't be inlined. Pure CPU - deterministic, no network.

Category: Data conversion · Tags: openapi swagger ref dereference resolve api

TRY IN PLAYGROUND →

Parameters

NameTypeRequiredDescription
specanyyesOpenAPI/Swagger document (object or JSON string) Also accepted as openapi, schema, document, doc, definition.

Example request

curl -i -X POST https://agent402.tools/api/openapi-resolve-refs \
  -H "Content-Type: application/json" \
  -d '{"spec":{"openapi":"3.0.0","info":{"title":"Demo","version":"1.0.0"},"paths":{"/users/{id}":{"get":{"parameters":[{"$ref":"#/components/parameters/UserId"}],"responses":{"200":{"description":"ok","content":{"application/json":{"schema":{"$ref":"#/components/schemas/User"}}}}}}}},"components":{"schemas":{"User":{"type":"object","properties":{"id":{"type":"string"},"name":{"type":"string"}}}},"parameters":{"UserId":{"name":"id","in":"path","required":true,"schema":{"type":"string"}}}}}}'

Without payment this returns HTTP 402 Payment Required with the exact price for openapi-resolve-refs; any x402 v2 or MPP client pays it and retries.

Example response

{
  "spec": {
    "openapi": "3.0.0",
    "info": {
      "title": "Demo",
      "version": "1.0.0"
    },
    "paths": {
      "/users/{id}": {
        "get": {
          "parameters": [
            {
              "name": "id",
              "in": "path",
              "required": true,
              "schema": {
                "type": "string"
              }
            }
          ],
          "responses": {
            "200": {
              "description": "ok",
              "content": {
                "application/json": {
                  "schema": {
                    "type": "object",
                    "properties": {
                      "id": {
                        "type": "string"
                      },
                      "name": {
                        "type": "string"
                      }
                    }
                  }
                }
              }
            }
          }
        }
      }
    },
    "components": {
      "schemas": {
        "User": {
          "type": "object",
          "properties": {
            "id": {
              "type": "string"
            },
            "name": {
              "type": "string"
            }
          }
        }
      },
      "parameters": {
        "UserId": {
          "name": "id",
          "in": "path",
          "required": true,
          "schema": {
            "type": "string"
          }
        }
      }
    }
  },
  "resolved": 2,
  "circular": [],
  "unresolved": [],
  "external": []
}
FieldTypeAlways presentIn the example
specobjectyes4 fields: openapi, info, paths, components
resolvednumberyes2
circulararrayyes0 items in the example
unresolvedarrayyes0 items in the example
externalarrayyes0 items in the example

From an MCP client

catalog.call {
  "slug": "openapi-resolve-refs",
  "params": {
    "spec": {
      "openapi": "3.0.0",
      "info": {
        "title": "Demo",
        "version": "1.0.0"
      },
      "paths": {
        "/users/{id}": {
          "get": {
            "parameters": [
              {
                "$ref": "#/components/parameters/UserId"
              }
            ],
            "responses": {
              "200": {
                "description": "ok",
                "content": {
                  "application/json": {
                    "schema": {
                      "$ref": "#/components/schemas/User"
                    }
                  }
                }
              }
            }
          }
        }
      },
      "components": {
        "schemas": {
          "User": {
            "type": "object",
            "properties": {
              "id": {
                "type": "string"
              },
              "name": {
                "type": "string"
              }
            }
          }
        },
        "parameters": {
          "UserId": {
            "name": "id",
            "in": "path",
            "required": true,
            "schema": {
              "type": "string"
            }
          }
        }
      }
    }
  }
}

On the hosted connector at https://agent402.tools/mcp, catalog.call runs openapi-resolve-refs free (rate-limited, no wallet). Local install: npx -y agent402-mcp.

Errors and behavior

Paid call (JavaScript agent)

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const client = new x402Client();
client.setSpendControls?.(false); // keep your own spending ceiling in code
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);

const res = await payFetch("https://agent402.tools/api/openapi-resolve-refs", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    "spec": {
      "openapi": "3.0.0",
      "info": {
        "title": "Demo",
        "version": "1.0.0"
      },
      "paths": {
        "/users/{id}": {
          "get": {
            "parameters": [
              {
                "$ref": "#/components/parameters/UserId"
              }
            ],
            "responses": {
              "200": {
                "description": "ok",
                "content": {
                  "application/json": {
                    "schema": {
                      "$ref": "#/components/schemas/User"
                    }
                  }
                }
              }
            }
          }
        }
      },
      "components": {
        "schemas": {
          "User": {
            "type": "object",
            "properties": {
              "id": {
                "type": "string"
              },
              "name": {
                "type": "string"
              }
            }
          }
        },
        "parameters": {
          "UserId": {
            "name": "id",
            "in": "path",
            "required": true,
            "schema": {
              "type": "string"
            }
          }
        }
      }
    }
  }),
});

No wallet? Pay with compute

Fetch a challenge, solve the sha256 puzzle (16 leading zero bits, a fraction of a second of CPU), and resend with the X-Pow-Solution header:

import { createHash } from "node:crypto";
const lz = (b) => { let t = 0; for (const x of b) { if (!x) { t += 8; continue; } t += Math.clz32(x) - 24; break; } return t; };
const c = await (await fetch("https://agent402.tools/api/pow/challenge?slug=openapi-resolve-refs")).json();
let n = 0;
while (lz(createHash("sha256").update(c.challenge + ":" + n).digest()) < c.difficulty) n++;
await fetch("https://agent402.tools/api/openapi-resolve-refs", { method: "POST", headers: { "X-Pow-Solution": c.token + ":" + n, "Content-Type": "application/json" }, body: JSON.stringify({"spec":{"openapi":"3.0.0","info":{"title":"Demo","version":"1.0.0"},"paths":{"/users/{id}":{"get":{"parameters":[{"$ref":"#/components/parameters/UserId"}],"responses":{"200":{"description":"ok","content":{"application/json":{"schema":{"$ref":"#/components/schemas/User"}}}}}}}},"components":{"schemas":{"User":{"type":"object","properties":{"id":{"type":"string"},"name":{"type":"string"}}}},"parameters":{"UserId":{"name":"id","in":"path","required":true,"schema":{"type":"string"}}}}}}) });

Related tools

OpenAPI / Swagger diff

FREE w/ compute · or $0.001 · POST /api/openapi-diff

Compare two OpenAPI 3.x or Swagger 2.x documents and return a structured diff: added / removed / changed endpoints, with…

OpenAPI endpoint extractor

FREE w/ compute · or $0.001 · POST /api/openapi-extract

Flatten an OpenAPI 3.x or Swagger 2.x spec into a structured list of callable endpoints - one row per operation with met…

OpenAPI mock response generator

FREE w/ compute · or $0.001 · POST /api/openapi-mock-response

Synthesize a JSON response body for one operation + status code in an OpenAPI 3.x or Swagger 2.x spec. Locate the operat…

OpenAPI spec redactor

FREE w/ compute · or $0.001 · POST /api/openapi-redact

Shrink an OpenAPI 3.x or Swagger 2.x document for LLM context by stripping verbose meta-fields (examples, descriptions, …

OpenAPI required-params extractor

FREE w/ compute · or $0.002 · POST /api/openapi-required-params

For one operation, return the minimum set of inputs an agent must provide to make a successful call. Locate the op by `o…

OpenAPI operation search

FREE w/ compute · or $0.001 · POST /api/openapi-search

Search operations in an OpenAPI 3.x or Swagger 2.x spec against a free-text query. Tokenizes the query (lowercase, alpha…