Vagrant · API Governance Rules

Vagrant API Rules

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

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

Rule Categories

vagrant

Rules

warn
vagrant-bearer-auth
Vagrant Cloud API operations should use bearerAuth security
$.paths[*][*]
error
vagrant-operations-have-summaries
All operations must have a summary
$.paths[*][get,post,put,delete,patch]
warn
vagrant-operations-have-tags
All operations should have at least one tag
$.paths[*][get,post,put,delete,patch]
warn
vagrant-operation-ids-camel-case
Operation IDs should use camelCase
$.paths[*][*].operationId
hint
vagrant-username-name-paths
Box paths should use :username/:name format
$.paths
warn
vagrant-error-responses
Operations should document error responses
$.paths[*][get,post,put,delete].responses
warn
vagrant-json-content-type
API responses should use application/json content type
$.paths[*][*].responses[*].content

Spectral Ruleset

Raw ↑
extends:
  - spectral:oas
rules:
  vagrant-bearer-auth:
    description: Vagrant Cloud API operations should use bearerAuth security
    message: Operations should use bearerAuth security scheme
    severity: warn
    given: "$.paths[*][*]"
    then:
      function: truthy
      field: security

  vagrant-operations-have-summaries:
    description: All operations must have a summary
    message: Operations must have a summary field
    severity: error
    given: "$.paths[*][get,post,put,delete,patch]"
    then:
      function: truthy
      field: summary

  vagrant-operations-have-tags:
    description: All operations should have at least one tag
    message: Operations should be tagged
    severity: warn
    given: "$.paths[*][get,post,put,delete,patch]"
    then:
      function: truthy
      field: tags

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

  vagrant-username-name-paths:
    description: Box paths should use :username/:name format
    message: Box resource paths should include username and name parameters
    severity: hint
    given: "$.paths"
    then:
      function: truthy

  vagrant-error-responses:
    description: Operations should document error responses
    message: Operations should have 401 or 404 error responses defined
    severity: warn
    given: "$.paths[*][get,post,put,delete].responses"
    then:
      function: truthy

  vagrant-json-content-type:
    description: API responses should use application/json content type
    message: Responses should use application/json content type
    severity: warn
    given: "$.paths[*][*].responses[*].content"
    then:
      function: truthy

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