Loading
Preparing the page
Public context is loading before any interactive tool code.
Preparing the page
Public context is loading before any interactive tool code.
Parse an OpenAPI 3.0 or 3.1 JSON document locally, expose endpoint facts and download reviewable Markdown without uploading the specification.
Your checked result will appear here.
Methods, paths, parameters, request bodies, security requirements and responses stay in separate lanes until the Markdown reference assembles them. A missing declaration remains visibly missing.
The current local workflow deliberately handles JSON documents from the 3.0 and 3.1 feature sets. YAML, repository import and reference resolution require a broader parser and review boundary.
OpenAPI version, API title, API version and at least one supported path operation must be present.
GET, POST, PUT, PATCH, DELETE, OPTIONS, HEAD and TRACE operations receive independent sections.
Path parameters flow into each operation; an operation parameter with the same name and location replaces the shared definition.
Copy or download the reference, then compare it with the source document and a running test environment.
The tested fixture contributes its own method, path, security scheme name, path parameter and two response descriptions. The generator does not create an example response body because none was declared.
{
"openapi": "3.1.0",
"info": {
"title": "Orders API",
"version": "1.0.0"
},
"security": [{ "bearerAuth": [] }],
"paths": {
"/orders/{orderId}": {
"parameters": [{
"name": "orderId",
"in": "path",
"required": true,
"schema": { "type": "string" }
}],
"get": {
"summary": "Get one order",
"responses": {
"200": { "description": "Order found" },
"404": { "description": "Order not found" }
}
}
}
}
}## GET /orders/{orderId} — Get one order
Security: bearerAuth
### Parameters
| Name | In | Required | Schema |
| orderId | path | yes | string |
### Responses
| Status | Description |
| 200 | Order found |
| 404 | Order not found |Observed: 1 endpoint · 1 parameter · 2 responses · 1 secured
{"swagger":"2.0","paths":{}}A Swagger 2.0 document does not satisfy this parser's explicit OpenAPI 3 boundary.
A structurally valid document can still be stale, incomplete or unsafe to publish. Documentation approval requires product and security evidence beyond parsing.
Exercise each method and response in a controlled environment; a specification is a contract, not execution evidence.
Confirm authentication, authorization, validation, rate-limit and dependency failures are declared where relevant.
Check whether root security, operation overrides and anonymous alternatives express the intended access policy.
Remove internal hosts, private schemas, credentials, tokens and examples containing customer data.
The output exposes declared facts and omissions. It does not call an endpoint, validate schemas exhaustively, resolve external files or prove that security controls work.