US Army · API Governance Rules
US Army — public rules
Spectral linting rules defining API design standards and conventions for US Army.
7 Rules
error 2
warn 4
info 1
Authorship not recorded
No authorship marker is recorded for this file. It is not presented as the provider's; it was most likely written by an API Evangelist pass before outputs were stamped.
Rule Categories
army
Rules
warn
army-operations-have-tags
All US Army API operations must have at least one tag
$.paths[*][get,post,put,patch,delete]
info
army-paths-use-v1-prefix
All Army API paths should use the /api/v1 prefix via servers configuration
$.servers[*].url
error
army-get-operations-have-200
All GET operations must define a 200 response
$.paths[*][get]
warn
army-operations-have-operation-ids
All Army API operations must have operationId for SDK generation
$.paths[*][get,post,put,patch,delete]
warn
army-parameters-have-descriptions
All parameters should have descriptions
$.paths[*][*].parameters[*]
warn
army-responses-have-schemas
All 200 responses should define a content schema
$.paths[*][*].responses.200
error
army-server-https
US Army API servers must use HTTPS
$.servers[*].url
Spectral Ruleset
Work with this as data
Every ruleset here is available over the APIs.io API and to AI agents over MCP.