OpenAPI Operation Contract Explorer

How to use OpenAPI Operation Contract Explorer

Inspect local OpenAPI 3.1 operations, effective parameters, declared security alternatives and selected reference diagnostics. Follow root-document pointers for selected operation components. See parameter overrides, request/response media types and literal server templates while keeping unresolved documents and unmodeled schema/runtime behavior visible.

1. Provide self-contained openapi 3.1 document.
2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
3. Copy the result or download a separate output; reset to clear the current form.

Good to know

• 200 KB well-formed UTF-8; 500 path keys, 1,000 operations, 100 parameters/responses/media types per operation and 20 server alternatives. Output is capped at 500,000 characters and 1,000 selected diagnostics. OpenAPI 3.1.0–3.1.2 only.
• JSON refuses duplicate/prototype-related object keys and exceeds neither 100,000 values nor 40 levels. YAML 1.2 core uses at most 20,000 syntax nodes and 40 levels; aliases, merge/custom tags and non-string mapping keys are refused. Quote YAML response keys such as "200".
• Root-document JSON Pointer fragments resolve selected Path Item, Parameter, Request Body, Response and Security Scheme references, at most 40 links per chain and 5,000 traversals. Path Items with adjacent $ref fields are left unresolved. External documents and anchors are reported without fetching them.
• Selected operation semantics only: parameter override by name/location, ignored reserved header parameters, required path parameters and declared security inheritance/alternatives. JSON Schema validation, Schema $id/$ref bases, serialization styles, examples, callbacks, webhooks, links and runtime expressions are not evaluated.
• Server URL templates remain source strings; variables are listed but not expanded. No API call, authentication, URL fetch, Markdown rendering or user HTML mounting occurs. A clean selected report cannot prove full specification conformance or deployed security.
• Requested libraries/modules prepare for at most 10 seconds; a separate 2-second computation limit terminates the Worker. Large or complex contracts may need splitting into smaller local documents.
• Inputs are processed on this device and are not automatically saved or uploaded.