Does the inspector fetch external $ref URLs?
No. It records external references and their document paths without making network requests. This avoids leaking private specification locations or credentials.
OpenAPI & Swagger Inspector
Inspect OpenAPI 3.0, OpenAPI 3.1, or Swagger 2.0 operations, schemas, security schemes, servers, and references without remote fetches.
Local input limit: 5 MB · Processing timeout: 120 s
How can I verify this?
Open your browser DevTools and the Network panel, optionally clear existing requests, then run the tool. Page assets or consent-based analytics may still load, but tool payloads, files, keys, and results are not sent for processing.
Inspect an OpenAPI or Swagger document
Paste JSON or YAML, or choose a local specification file. External $ref URLs are reported but never requested automatically.
0 KB
Specification inventory
Specification inventory will appear here
Paste a specification or load the example, then inspect it to explore operations, schemas, security, servers, and references.
API specification inventory
DecodeLens inventories declared API structure and performs bounded structural diagnostics. It is not a full replacement for the official OpenAPI conformance schema or runtime request validation.
Inspection boundaries
- Supports version-marked OpenAPI 3.0.x, OpenAPI 3.1.x, and Swagger 2.0 JSON or YAML documents.
- Internal JSON Pointer $ref values are checked locally. External file and URL references are listed but never fetched automatically.
- OpenAPI 3.1 component schemas may continue to Draft 2020-12 validation. OpenAPI 3.0 and Swagger 2.0 schemas remain inspector-only because their schema dialect differs.
- The structural diagnostics cover common document, operation, parameter, response, operationId, and reference issues; they do not claim complete specification conformance.
- No server request, operation execution, remote schema lookup, authentication flow, or HAR validation occurs in this version.
Related tools for this workflow
Continue with tools that decode, convert, inspect, or verify the same data.
- Data formats
JSON Schema Validator
Validate JSON against Draft 7, 2019-09, or 2020-12 schemas with exact instance paths, source locations, schema keywords, and Object View.
Open tool - Data formats
JSON ↔ YAML Converter
Convert JSON and YAML in either direction, validate syntax, and inspect the result as a tree.
Open tool - API & network
HAR File Analyzer & Sanitizer
Analyze HAR requests, failures, timing, transfer sizes, bodies, and sensitive fields; export a separate redacted copy.
Open tool - Data formats
JSON Formatter & Validator
Format, minify, validate, and explore JSON in a collapsible Object View without uploading data.
Open tool
Review an API contract
Load a local specification, filter operations, inspect reusable schemas and security declarations, then review unresolved or external references before integration or code generation.
OpenAPI document
openapi: 3.1.0
info:
title: Pet API
version: 1.0.0
paths: {}Inventory
OpenAPI 3.1.0 · 0 operations · 0 unresolved $refOpenAPI & Swagger Inspector FAQ
Is this a full OpenAPI validator?
No. It performs useful bounded structural checks and inventories the contract. It does not claim exhaustive conformance with every OpenAPI schema rule.
Why can only OpenAPI 3.1 schemas open in JSON Schema Validator?
OpenAPI 3.1 aligns its Schema Object with modern JSON Schema. OpenAPI 3.0 and Swagger 2.0 use different schema dialects that must not be mislabeled as Draft 2020-12.
Is the specification uploaded?
No. Parsing, reference checks, and inventory generation run in a disposable browser worker.