The Spectral ruleset format as a standalone specification and JSON Schema — normative, independently versioned, implementable by anyone.
-
Updated
Oct 23, 2026 - HTML
The Spectral ruleset format as a standalone specification and JSON Schema — normative, independently versioned, implementable by anyone.
The API Commons — the hub and website (apicommons.org) for open, machine-readable API building blocks, standards, and browser-first tools.
JSON:API artifacts for the API Commons — schemas and governance for the JSON:API standard.
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.
Turn a prose style guide into an owned, grounded, well-named Spectral ruleset. studio.apicommons.org.
The plans schema for the API Commons — machine-readable API access plans, tiers, and pricing.
Machine-readable API policy building blocks for the API Commons — the business rules behind API governance.
The rate limits schema for the API Commons — a machine-readable way to publish the quotas an API enforces.
This is the repository for managing the APIs.json for the Train Travel API template.
Machine-readable API vocabulary building blocks for the API Commons — shared words and definitions for API operations.
A grounded Spectral ruleset for the OWASP API Security Top 10 — add a real security governance layer in one line.
A Model Context Protocol (MCP) server that lints API artifacts against a best-of-breed API governance ruleset from any AI client. Powered by Spectral.
The change log schema for the API Commons — a machine-readable way to publish an API's changelog.
Shared examples for the API Commons building blocks and the APIs.json ecosystem.
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.
De facto standards for the open-data layer — the CKAN Action API authored from CKAN's own source and graded by probing live government portals across 30 releases.
The common Messaging (Email, SMS, Chat) vocabulary, distilled from providers' own OpenAPI: shared operations, JSON Schema with measured adoption, per-provider crosswalks.
The common Software Testing vocabulary, distilled from providers' own OpenAPI: shared operations, JSON Schema with measured adoption, per-provider crosswalks.
The common Fleet and Telematics vocabulary, distilled from providers' own OpenAPI: shared operations, JSON Schema with measured adoption, per-provider crosswalks.
The common Gaming vocabulary, distilled from providers' own OpenAPI: shared operations, JSON Schema with measured adoption, per-provider crosswalks.
To associate your repository with the api-commons topic, visit your repo's landing page and select "manage topics."