Inworld AI · API Governance Rules
Inworld AI API Rules
Spectral linting rules defining API design standards and conventions for Inworld AI.
7 Rules
error 2
warn 5
Rule Categories
inworld
Rules
error
inworld-paths-lowercase
All paths use lowercase ASCII letters, digits, hyphens, slashes, and the `:verb` action suffix; no camelCase or underscores.
$.paths.*~
warn
inworld-camelcase-properties
Inworld schemas use camelCase property names (e.g. `voiceId`, `audioConfig`, `langCode`).
$..properties.*~
error
inworld-api-version-prefix
Endpoints should be versioned with `/v1/` somewhere in the path.
$.paths.*~
warn
inworld-basic-auth-required
All HTTP REST endpoints require Basic API-key authentication unless explicitly overridden for Realtime JWT.
$.paths.*[get,post,put,patch,delete]
warn
inworld-operation-summary-title-case
Operation summaries must use Title Case.
$.paths.*[get,post,put,patch,delete].summary
warn
inworld-action-suffix-verbs
When an action verb is used in the path it should follow the `:verb` suffix convention (e.g. `:clone`, `:design`, `:publish`, `:stream`, `:websocket`).
$.paths.*~
warn
inworld-error-schema
4XX responses should reference the canonical Error schema.
$.paths.*.*.responses.4XX