Yoast · API Governance Rules

Yoast API Rules

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

8 Rules error 1 warn 6
View Rules File View on GitHub

Rule Categories

yoast

Rules

warn
yoast-operation-summary-title-case
Operation summaries must use Title Case
$.paths[*][*].summary
warn
yoast-operation-ids-camel-case
Operation IDs should use camelCase
$.paths[*][*].operationId
warn
yoast-all-operations-have-tags
All operations must have at least one tag
$.paths[*][*]
warn
yoast-all-operations-have-description
All operations must have a description
$.paths[*][*]
warn
yoast-responses-have-descriptions
All response objects should have descriptions
$.paths[*][*].responses[*]
warn
yoast-parameters-have-descriptions
All parameters should have descriptions
$.paths[*][*].parameters[*]
error
yoast-get-read-only
GET operations should not have request bodies
$.paths[*].get
hint
yoast-v1-path-prefix
Yoast custom endpoints should use /yoast/v1/ prefix
$.paths

Spectral Ruleset

Raw ↑
extends: spectral:oas
rules:
  yoast-operation-summary-title-case:
    description: Operation summaries must use Title Case
    message: "Summary '{{value}}' must use Title Case"
    given: "$.paths[*][*].summary"
    then:
      function: pattern
      functionOptions:
        match: "^[A-Z][a-zA-Z0-9]*(\\s[A-Z][a-zA-Z0-9]*)*$"
    severity: warn

  yoast-operation-ids-camel-case:
    description: Operation IDs should use camelCase
    message: "OperationId '{{value}}' should use camelCase"
    given: "$.paths[*][*].operationId"
    then:
      function: pattern
      functionOptions:
        match: "^[a-z][a-zA-Z0-9]*$"
    severity: warn

  yoast-all-operations-have-tags:
    description: All operations must have at least one tag
    message: "Operation must have at least one tag"
    given: "$.paths[*][*]"
    then:
      field: tags
      function: truthy
    severity: warn

  yoast-all-operations-have-description:
    description: All operations must have a description
    message: "Operation must have a description"
    given: "$.paths[*][*]"
    then:
      field: description
      function: truthy
    severity: warn

  yoast-responses-have-descriptions:
    description: All response objects should have descriptions
    message: "Response must have a description"
    given: "$.paths[*][*].responses[*]"
    then:
      field: description
      function: truthy
    severity: warn

  yoast-parameters-have-descriptions:
    description: All parameters should have descriptions
    message: "Parameter must have a description"
    given: "$.paths[*][*].parameters[*]"
    then:
      field: description
      function: truthy
    severity: warn

  yoast-get-read-only:
    description: GET operations should not have request bodies
    message: "GET operation '{{path}}' should not have a requestBody"
    given: "$.paths[*].get"
    then:
      field: requestBody
      function: falsy
    severity: error

  yoast-v1-path-prefix:
    description: Yoast custom endpoints should use /yoast/v1/ prefix
    message: "Custom Yoast paths should start with /yoast/v1/"
    given: "$.paths"
    then:
      function: schema
      functionOptions:
        schema:
          type: object
          patternProperties:
            "^/yoast/":
              type: object
    severity: hint

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/yoast-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 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.

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