US Space Command · API Governance Rules
US Space Command API Rules
Spectral linting rules defining API design standards and conventions for US Space Command.
6 Rules
error 2
warn 2
info 2
Rule Categories
space
Rules
info
space-track-path-class-prefix
Space-Track paths should follow /basicspacedata/query/class/{class}/ pattern
$.paths[*]~
error
space-track-operation-summary
All operations must have a summary
$.paths[*][*]
warn
space-track-operation-tags
Operations must have at least one tag
$.paths[*][*]
error
space-track-get-200-response
GET operations must define a 200 response
$.paths[*].get
info
space-track-format-path-param
Space-Track endpoints should include a format path parameter
$.paths[*]~
warn
space-track-401-response
Authenticated endpoints should document 401 response
$.paths[*].get
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/us-space-comman-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.