Teliax · API Governance Rules
Teliax API Rules
Spectral linting rules defining API design standards and conventions for Teliax.
10 Rules
error 5
warn 3
info 2
Generated by API Evangelist
Written by API Evangelist tooling for Teliax's APIs. It is a starting point, not a ruleset Teliax publishes or enforces.
Rule Categories
info
operation
operationid
path
servers
Rules
warn
operationid-casing-camel
operationIds are camelCase (measured: 92% of this contract)
$.paths[*][get,post,put,patch,delete].operationId
warn
operation-has-summary
Every operation has a summary (measured: 98% of this contract)
$.paths[*][get,post,put,patch,delete]
error
operation-has-tags
Every operation is tagged (measured: 100% of this contract)
$.paths[*][get,post,put,patch,delete]
warn
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: 88% 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[*]~
info
servers-https
Servers are https (measured: 80% of this contract)
$.servers[*].url
error
info-has-description
The contract's info block carries a description (measured: 100% of this contract)
$.info
error
info-has-contact-or-terms
The contract's info block names a contact or terms of service (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.