University of Washington · API Governance Rules
University of Washington API Rules
Spectral linting rules defining API design standards and conventions for University of Washington.
6 Rules
error 1
warn 3
info 2
Rule Categories
uw
Rules
warn
uw-info-contact
UW Enterprise Web Services specs should declare a contact (the EWS & Events Team).
$.info
warn
uw-info-description
API info object must include a description.
$.info
info
uw-server-relative-path
UW EWS specs use a relative server path matching the service mount (e.g. /student, /idcard).
$.servers[*].url
warn
uw-paths-versioned
Operation paths should be version-prefixed (e.g. /v5/..., /v1/...) per UW EWS convention.
$.paths[*]~
info
uw-viewmodel-schema-naming
Response object schemas follow the UW ...ViewModel / ...ResourceUri naming convention.
$.components.schemas[*]~
error
uw-operation-response
Every operation must define at least one response.
$.paths[*][*].responses
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/university-of-washington-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.