Songstats · API Governance Rules

Songstats API Rules

Spectral linting rules defining API design standards and conventions for Songstats.

7 Rules error 2 warn 5
View Rules File View on GitHub

Rule Categories

songstats

Rules

warn
songstats-query-param-snake-case
$.paths[*][*].parameters[?(@.in == 'query')].name
warn
songstats-operation-summary-title-case
$.paths[*][*].summary
error
songstats-operation-id-required
$.paths[*][get,post,put,delete,patch]
warn
songstats-operation-tags-required
$.paths[*][get,post,put,delete,patch]
error
songstats-security-schemes-defined
$.components.securitySchemes
warn
songstats-success-response-required
$.paths[*][get,post,put,delete,patch].responses
warn
songstats-api-key-header-name
$.components.securitySchemes[?(@.type == 'apiKey')].name

Spectral Ruleset

Raw ↑
extends: spectral:oas
rules:

  # Songstats API uses snake_case for query parameters
  songstats-query-param-snake-case:
    message: "Query parameters should use snake_case"
    severity: warn
    given: "$.paths[*][*].parameters[?(@.in == 'query')].name"
    then:
      function: pattern
      functionOptions:
        match: "^[a-z][a-z0-9_]*$"

  # All operation summaries should use Title Case
  songstats-operation-summary-title-case:
    message: "Operation summaries should use Title Case"
    severity: warn
    given: "$.paths[*][*].summary"
    then:
      function: pattern
      functionOptions:
        match: "^[A-Z]"

  # All operations should have an operationId
  songstats-operation-id-required:
    message: "Operations must have an operationId"
    severity: error
    given: "$.paths[*][get,post,put,delete,patch]"
    then:
      field: operationId
      function: truthy

  # Operations must have at least one tag
  songstats-operation-tags-required:
    message: "Operations must have at least one tag"
    severity: warn
    given: "$.paths[*][get,post,put,delete,patch]"
    then:
      field: tags
      function: truthy

  # API must define security schemes
  songstats-security-schemes-defined:
    message: "API must define security schemes (apikey in header)"
    severity: error
    given: "$.components.securitySchemes"
    then:
      function: truthy

  # Responses must document at least a 2xx response
  songstats-success-response-required:
    message: "Operations must document at least one success response"
    severity: warn
    given: "$.paths[*][get,post,put,delete,patch].responses"
    then:
      function: schema
      functionOptions:
        schema:
          anyOf:
            - required: ["200"]
            - required: ["201"]
            - required: ["204"]

  # API key auth should use 'apikey' header name
  songstats-api-key-header-name:
    message: "API key should use 'apikey' as the header name"
    severity: warn
    given: "$.components.securitySchemes[?(@.type == 'apiKey')].name"
    then:
      function: pattern
      functionOptions:
        match: "^apikey$"

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.
All 92 tools

Call it yourself

curl for this page
This ruleset
curl "https://apis.io/api/v1/rules/songstats-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.