1F916 · API Governance Rules
1F916 API Rules
Spectral linting rules defining API design standards and conventions for 1F916.
9 Rules
error 7
warn 1
info 1
Generated by API Evangelist
Written by API Evangelist tooling for 1F916's APIs. It is a starting point, not a ruleset 1F916 publishes or enforces.
Rule Categories
info
operation
path
response
servers
Rules
error
operation-has-summary
Every operation has a summary (measured: 100% of this contract)
$.paths[*][get,post,put,patch,delete]
error
operation-has-description
Every operation has a description (measured: 100% of this contract)
$.paths[*][get,post,put,patch,delete]
error
operation-has-success-response
Every operation declares a 2xx response (measured: 100% of this contract)
$.paths[*][get,post,put,patch,delete].responses
info
path-segment-casing-camel
Path segments are camel case (measured: 87% of this contract)
$.paths[*]~
error
path-no-trailing-slash
Paths carry no trailing slash (measured: 100% of this contract)
$.paths[*]~
error
path-params-in-braces
Path parameters use {braces}, not :colon (measured: 100% of this contract)
$.paths[*]~
error
servers-https
Servers are https (measured: 100% of this contract)
$.servers[*].url
warn
response-media-type
Responses are served as application/json (measured: 94% of this contract)
$.paths[*][get,post,put,patch,delete].responses[*].content
error
info-has-description
The contract's info block carries a description (measured: 100% of this contract)
$.info
Spectral Ruleset
Work with this as data
Every ruleset here is available over the APIs.io API and to AI agents over MCP.