Spectral CLI — a maintained, openly-governed API Commons build of the Spectral linter. Reference implementation of the Spectral ruleset specification.
-
Updated
Aug 18, 2026 - TypeScript
Spectral CLI — a maintained, openly-governed API Commons build of the Spectral linter. Reference implementation of the Spectral ruleset specification.
Standalone documentation for any APIs.json — rich, portable HTML docs for every API, property, and inline OpenAPI/Arazzo artifact. Supports APIs.json 0.11–0.21.
Browser-first API governance validator for OpenAPI, AsyncAPI, Arazzo, and JSON Schema — powered by Spectral, with Swagger 2.0 parity. Search Git hosts for real artifacts, lint against a best-of-breed ruleset, edit rules, and commit or PR back. No backend. validator.apicommons.org
The universal install button for MCP servers — one button, every client. Hosted chooser, embeddable web component, and an open registry of MCP client install methods.
Sanctioned, owned, expiring API governance exceptions — reconcile a machine-readable waivers file against Spectral output. Browser-first.
Browser-first registry for API artifacts — search APIs.io + GitHub/GitLab/Bitbucket, keep provenance, save locally or commit/PR to git, and edit
A browser-first, ref-resolving design-diff for OpenAPI (and AsyncAPI/Arazzo) — paste an old and a new spec, resolve $ref so reviewers see the real shape, and get a stakeholder-friendly, breaking-flagged change list plus a copyable Markdown summary for the PR.
Measure how much of your API description your governance rules actually check — coverage by section, dead rules, per-rule reach. Browser-first.
A federated API governance rule registry — a central baseline plus the domains that adopt it, as a matrix of inherit / override / waive / promote. federation.apicommons.org
Forge MCP tools and Agent Skills from your OpenAPI — a browser-first workbench for designing the agent layer of an API
A DX/AX visual layer for any APIs.json — see each REST operation flow to its MCP tool and Agent Skill, with a free/paid coverage scorecard. experience.apicommons.org
A registry of adoptable, provenanced API governance rulesets — adopt a real owned ruleset by reference instead of the defaults. rulesets.apicommons.org.
A browser-first tool for a versioned, reusable API model/component library — author or import a library of named JSON Schemas, see which OpenAPI specs consume each model, and classify a version bump as breaking or non-breaking across every consumer while surfacing near-duplicate model drift.
A browser-first tool for the longitudinal view of API governance — ingest a series of Spectral snapshots over time, compute a 0–100 health score per spec, and see health trends and the growing problem lists so you can act before a spec goes the wrong direction.
Assess API reusability across your organization — discover (apis.io/GitHub/HAR/gateways), index as APIs.json, and score reuse per API and per org/team/domain. Runs in your browser.
A browser-first tool that meets code-first API teams where they are — fingerprint the OpenAPI generator from a generated spec, separate the governance findings that must be fixed in code (because the spec is regenerated) from spec-authoring findings, and map each one to the exact code annotation that fixes it.
Issue and verify tamper-evident API governance certificates — SHA-256 fingerprint lets consumers re-verify an API passed a ruleset at a profile. Browser-first.
A browser-first tool to make Spectral/Spotlight governance adoptable on a legacy estate — snapshot a baseline of the violations you have today, then ratchet: fail only NEW violations while baselined ones are suppressed, track a warning budget, and burn the baseline down to zero.
Export an API governance ruleset into agent-native artifacts — AGENTS.md, system prompt, remediation prompt pack, rule digest. Browser-first.
Bind your API governance building blocks — policies, rules, pipelines, and specs — into one navigable graph with a Gaps view. A browser-first API Commons tool at graph.apicommons.org.
Add a description, image, and links to the api-commons topic page so that developers can more easily learn about it.
To associate your repository with the api-commons topic, visit your repo's landing page and select "manage topics."