# authorship: generated by API Evangelist tooling. Stamped 2026-08-18
# on the file's own generator header (roadmap#64). An unmarked file is
# NOT assumed to be ours -- absence of evidence was never stamped.
x-method: generated
# apache-dubbo — Spectral ruleset (strengthened)
# Plain Spectral. Existing hand-authored rules preserved; measured rules added
# from this provider's own OpenAPI conventions by strengthen_ruleset.py,
# then self-validated against the spec.
#
# Provenance:
# - path-params-casing: snake @ 100% (n=81)
# - query-params-casing: snake @ 93% (n=56)
# - operation-documents-500: 98% adherence
# - pagination params observed: ['limit', 'offset', 'page', 'size']
# - merge: kept 15 existing, added 2 measured, upgraded 0
# - added: query-params-casing, operation-documents-500
extends:
- spectral:oas
rules:
info-title-required:
description: Info title must be defined
severity: error
given: $.info
then:
field: title
function: truthy
info-description-required:
description: Info description must be present
severity: warn
given: $.info
then:
field: description
function: truthy
info-version-required:
description: API version must be specified
severity: error
given: $.info
then:
field: version
function: truthy
operation-summary-required:
description: All operations must have a summary
severity: error
given: $.paths[*][get,post,put,delete,patch]
then:
field: summary
function: truthy
operation-summary-apache-dubbo-prefix:
description: Operation summaries should start with Apache Dubbo
severity: warn
given: $.paths[*][get,post,put,delete,patch].summary
then:
function: pattern
functionOptions:
match: ^Apache Dubbo
operation-description-required:
description: All operations must have a description
severity: warn
given: $.paths[*][get,post,put,delete,patch]
then:
field: description
function: truthy
operation-operationId-required:
description: All operations must have an operationId
severity: error
given: $.paths[*][get,post,put,delete,patch]
then:
field: operationId
function: truthy
operation-tags-required:
description: All operations must have at least one tag
severity: warn
given: $.paths[*][get,post,put,delete,patch]
then:
field: tags
function: truthy
paths-kebab-case:
description: Path segments should use kebab-case
severity: warn
given: $.paths
then:
field: '@key'
function: pattern
functionOptions:
match: ^(/[a-z0-9{}_-]+)+$
paths-no-trailing-slash:
description: Paths must not have trailing slashes
severity: warn
given: $.paths
then:
field: '@key'
function: pattern
functionOptions:
notMatch: /$
parameter-description-required:
description: All parameters must have descriptions
severity: warn
given: $.paths[*][get,post,put,delete,patch].parameters[*]
then:
field: description
function: truthy
response-success-required:
description: Operations must define at least one 2xx response
severity: error
given: $.paths[*][get,post,put,delete,patch].responses
then:
function: schema
functionOptions:
schema:
minProperties: 1
response-description-required:
description: All responses must have descriptions
severity: warn
given: $.paths[*][get,post,put,delete,patch].responses[*]
then:
field: description
function: truthy
schema-property-description:
description: Schema properties should have descriptions
severity: info
given: $.definitions[*].properties[*]
then:
field: description
function: truthy
no-empty-descriptions:
description: Descriptions must not be empty strings
severity: warn
given: $..description
then:
function: pattern
functionOptions:
match: .+
query-params-casing:
description: Query parameters should be snake_case (the dominant convention in this API).
severity: warn
given: $.paths[*][get,post,put,patch,delete].parameters[?(@.in=='query')]
then:
field: name
function: casing
functionOptions:
type: snake
operation-documents-500:
description: Operations should document a 500 response (documented on 98% of this API's operations).
severity: warn
given: $.paths[*][get,post,put,patch,delete].responses
then:
field: '500'
function: truthy
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.