Browserbase · API Governance Rules
Browserbase API Rules
Spectral linting rules defining API design standards and conventions for Browserbase.
10 Rules
error 2
warn 5
info 3
Rule Categories
browserbase
Rules
warn
browserbase-versioned-paths
All Browserbase API paths must be served under /v1/ or be a top-level resource that the server already prefixes.
$.paths[*]~
warn
browserbase-operation-id-camel-case
Browserbase operationIds use camelCase (e.g., createSession, getSession).
$.paths[*][get,post,put,patch,delete].operationId
error
browserbase-operation-id-required
All Browserbase operations must have an operationId.
$.paths[*][get,post,put,patch,delete]
warn
browserbase-tags-required
All Browserbase operations must declare at least one tag.
$.paths[*][get,post,put,patch,delete]
error
browserbase-auth-defined
Browserbase API must define the X-BB-API-Key apiKey security scheme.
$.components.securitySchemes
warn
browserbase-success-response-defined
Browserbase operations must define a 2xx success response.
$.paths[*][get,post,put,patch,delete].responses
info
browserbase-summary-title-case
Browserbase operation summaries should use Title Case.
$.paths[*][get,post,put,patch,delete].summary
info
browserbase-info-contact
API info should include a contact block.
$.info
warn
browserbase-info-description
API info must include a description.
$.info
info
browserbase-tag-title-case
OpenAPI tags should use Title Case for consistency across Browserbase resources.
$.tags[*].name