Universiti Sains Malaysia · API Governance Rules
Universiti Sains Malaysia API Rules
Spectral linting rules defining API design standards and conventions for Universiti Sains Malaysia.
8 Rules
error 5
warn 3
Rule Categories
usm
Rules
error
usm-operator-declared
Every USM contract must declare who operates the thing it describes.
$.info
error
usm-provenance-method
Every USM contract must say how API Evangelist came to hold it.
$.info
error
usm-provenance-source
Derived contracts must name the live surface they were derived from.
$.info
error
usm-servers-institution-host
An institution-operated USM contract must be served from a host under usm.my. This is the check that keeps a vendor's contract — Figshare, Pure, Ex Libris, Dataverse — from being credited to the institution.
$.servers[*].url
error
usm-servers-present
A contract with no servers block cannot be operator-checked by host at all — the hostless class this pipeline exists to catch.
$
warn
usm-contact-declared
A repository contract must name a contact reachable at the institution.
$.info
warn
usm-operation-ids
Every operation needs an operationId so agents can address it.
$.paths[*][get,post,put,patch,delete]
warn
usm-operation-described
Every operation must carry a description. Status codes alone do not tell a consumer that this host answers 200 with HTML on a .json path.
$.paths[*][get,post,put,patch,delete]
Spectral Ruleset
Work with this as data
Every ruleset here is available over the APIs.io API and to AI agents over MCP.