A minimal spec
openapi: 3.0.0
info: {title: "Pet Store", version: "1.0"}
paths: {/pets: {get: {summary: "List pets"}}}Title "Pet Store" v1.0, one endpoint: GET /pets — List pets.
Paste an OpenAPI or Swagger spec to browse its endpoints and catch structural mistakes.
Was this tool useful?
An OpenAPI spec is meant to be read by tooling first and humans second — this flips that, rendering it as a browsable list of endpoints while flagging the handful of structural mistakes (a missing version field, an unresolvable $ref) that quietly break a code generator downstream.
openapi: 3.0.0
info: {title: "Pet Store", version: "1.0"}
paths: {/pets: {get: {summary: "List pets"}}}Title "Pet Store" v1.0, one endpoint: GET /pets — List pets.