api-commons

The API Commons — the hub and website (apicommons.org) for open, machine-readable API building blocks, standards, and browser-first tools.

The Spectral ruleset format as a standalone specification and JSON Schema — normative, independently versioned, implementable by anyone.

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.

JSON:API artifacts for the API Commons — schemas and governance for the JSON:API standard.

Turn a prose style guide into an owned, grounded, well-named Spectral ruleset. studio.apicommons.org.

The change log schema for the API Commons — a machine-readable way to publish an API's changelog.

This is the repository for managing the APIs.json for the Train Travel API template.

The plans schema for the API Commons — machine-readable API access plans, tiers, and pricing.

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.

Shared examples for the API Commons building blocks and the APIs.json ecosystem.

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.

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.

Machine-readable API governance rules for the API Commons — Spectral rulesets across many artifact types.

De facto standards for the model layer — the OpenAI interface profiled as adopters actually implement it, graded into core/extended/vendor tiers by measured adoption, with a registry of who implements what.

Machine-readable API lifecycle building blocks for the API Commons — the stages every API moves through.

Turn Spectral lint output into a rich, self-contained HTML API governance report — the newman-reporter-htmlextra for API governance. CLI + reporter.apicommons.org.