Free developer tools · OpenAPI Parser

Understand your spec.
Before you build on it.

Validate, inspect, bundle and dereference OpenAPI with Octri’s open-source Rust parser. Run it in your browser, without an account.

Rust poweredRuns in your browserOpen source · Apache-2.0
Start with your specification

Fetched through Octri’s source proxy. Restricted URL? Upload the file instead.

Files and pasted content stay on this device. Processing runs in a Rust WebAssembly worker. External references require supplied files; they are never fetched automatically.

More than a valid JSON file.

One parsing engine, from the first diagnostic to the document your next tool consumes.

01

Validate

Check the document against its declared version. Diagnostics carry codes and source locations so you can find the original problem.

02

Inspect

Explore operations, schemas, security schemes and the reference graph through a structured API. This demo shows operations and reference counts.

03

Bundle

Collect referenced documents into a portable contract. Supply your files explicitly and keep the reference relationships visible.

04

Dereference

Expand reference targets for tools that need inline schemas. Circular references stay serializable instead of becoming infinite objects.

Version-aware by design

Swagger through OpenAPI 3.2.

Keep your existing contract version. Parse JSON or YAML without rounding large numbers along the way.

Need to change formats? Use Spec Converter
Parser support
DocumentsSwagger 2.0 · OpenAPI 3.0, 3.1, 3.2
EncodingJSON and YAML
NumbersLossless numeric values
ReferencesLocal, supplied files and circular references
ResultsDiagnostics, inventory, reference graph and serialized output

The same engine, in your project

Try it here.
Build with it anywhere.

This demo uses the published WebAssembly package. The Rust core and language bindings live in the same open-source repository.

Source & API reference Package on npm

Browser / WebAssembly

npm install @octri/openapi-parser-wasm

Also available as a Rust library and CLI, with native language bindings. Check the repository for each binding’s installation instructions and supported platforms.

Bounded browser processing

This demo accepts up to 100 UTF-8 files, 5 MiB each and 20 MiB combined. Each engine run has a 30-second limit. Large or deeply nested contracts may reach resource limits sooner.

A few practical questions.

What to expect from this tool, and where its boundaries are.

Swagger 2.0 and OpenAPI 3.0, 3.1 and 3.2, in JSON or YAML. Validation follows the declared dialect. Use Spec Converter to migrate the contract to another version.

Next, check contract quality

A valid contract can still leave gaps.

Spec Auditor finds missing schemas, naming problems and other issues that affect the tools built from your OpenAPI.

Audit your specification