Parse, validate, transform, and lint OpenAPI, AsyncAPI, Arazzo, Overlay, and JSON Schema through one shared semantic structure. Local-first and lossless.
Built by long-time maintainers of Swagger UI and Swagger Editor, OpenAPI Initiative contributors, and AsyncAPI spec maintainers.
Validate any spec from the terminal. Nothing to install, no account:
npx @speclynx/cli validate openapi.yaml
npx @speclynx/cli validate asyncapi.yaml
npx @speclynx/cli validate arazzo.yaml
npx @speclynx/cli validate overlay.yaml
Apply or generate overlays:
npx @speclynx/cli overlay apply add-contact.yaml museum.yaml
npx @speclynx/cli overlay diff openapi-v1.yaml openapi-v2.yaml
Prefer a UI? Open the SpecLynx Editor in your browser, or install the OpenAPI Toolkit for VS Code. More in the getting started guide.
SpecLynx combines core tooling, developer workflows, and editing surfaces into one consistent stack, plus a workflow toolkit built on top of it. All of it is open source under Apache 2.0.
| Tool | What it does | Type |
|---|---|---|
| CLI | Validate specs and apply overlays from the terminal and CI. | Command line |
| Editor | Write and validate specs in the browser, nothing to install. | Browser editor |
| OpenAPI Toolkit | Validation, completion, and preview while you author specs. | VS Code extension |
| Language Service | LSP intelligence for API specs, in any editor or platform. | Integration library |
| ApiDOM | Parse, dereference, and bundle any API spec through one lossless semantic structure. | Core library |
| UseArazzo | Validate, run, and trace Arazzo API workflows. Built on SpecLynx. | Workflow toolkit |
Your API specs may be standardized, but the tooling around them rarely is. Every format and version brings its own validator, linter, and converter, and every job brings another script in CI. The result is duplicated logic, checks that disagree, and fragile automation around the contracts your systems depend on.
- One semantic structure, not five parsers. Every spec is parsed into ApiDOM, one lossless, error-recovering structure with the semantics of each specification layered on top. Tools built on it behave the same way across every supported spec.
- Local-first, always. Runs on your machine. No accounts, no telemetry, and it works offline. Your specs never leave your environment. Read the manifesto →
- Built by the people who built the ecosystem. We have spent years building core Swagger, OpenAPI, and AsyncAPI tooling. Meet the team →
|
Since my days at Apiary and Swagger, I've been looking for OpenAPI tooling I'd actually recommend. SpecLynx is it, and no wonder: it's built by many of the same people. The editor, CLI, and VS Code extension share one engine, so the whole toolchain just makes sense. I'll be using it in my consulting and training. |
When I started AsyncAPI, the hardest part wasn't the spec. It was the tooling around it: every standard got its own parser, validator and set of quirks. SpecLynx is the toolchain I wish had existed back then, with one consistent model across OpenAPI, AsyncAPI and Arazzo. |
|
|
|
SpecLynx is open source under Apache 2.0. Contributions and questions are welcome: star a repo, open an issue, or join the Discussions.
SpecLynx is free to use. We help developers and teams integrate the tooling, standardize API and workflow specifications, and adopt it across their platform.
- Website: https://speclynx.com
- Email: info@speclynx.com
