Ubuntu · API Governance Rules
Ubuntu API Rules
Spectral linting rules defining API design standards and conventions for Ubuntu.
6 Rules
error 1
warn 5
Rule Categories
ubuntu
Rules
warn
ubuntu-operation-id-camel-case
Operation IDs must use camelCase.
$.paths[*][get,post,put,patch,delete].operationId
warn
ubuntu-has-tags
All operations must have at least one tag.
$.paths[*][get,post,put,patch,delete]
error
ubuntu-has-operation-id
All operations must have an operationId.
$.paths[*][get,post,put,patch,delete]
warn
ubuntu-has-description
All operations must have a description.
$.paths[*][get,post,put,patch,delete]
warn
ubuntu-summary-title-case
Operation summaries must use Title Case.
$.paths[*][get,post,put,patch,delete].summary
warn
ubuntu-200-response-content
Successful GET responses should define a content schema.
$.paths[*].get.responses.200
Spectral Ruleset
Work with this as data
Every ruleset here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for spectral rules
4 MCP tools reach this
find_rulesBrowse and filter every ruleset in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This ruleset
curl "https://apis.io/api/v1/rules/ubuntu-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.