VTEX · API Governance Rules
VTEX API Rules
Spectral linting rules defining API design standards and conventions for VTEX.
10 Rules
warn 5
info 5
Rule Categories
vtex
Rules
warn
vtex-operation-summary-title-case
Operation summaries must use Title Case.
$.paths[*][*].summary
info
vtex-operation-id-kebab-case
operationId should use kebab-case or camelCase consistently.
$.paths[*][*].operationId
warn
vtex-has-tags
Every operation must have at least one tag for grouping.
$.paths[*][*]
info
vtex-server-variable-account-name
VTEX APIs should use {accountName} server variable for multi-tenancy.
$.servers[*].variables
warn
vtex-response-200-defined
Every GET operation should define a 200 response.
$.paths[*].get.responses
warn
vtex-request-body-post
POST operations should define a request body.
$.paths[*].post
warn
vtex-security-defined
VTEX APIs should define security schemes for authentication.
$.components.securitySchemes
info
vtex-info-contact
API info should include contact information.
$.info
info
vtex-path-kebab-case
Path segments should use kebab-case or camelCase, not underscores.
$.paths
info
vtex-no-empty-descriptions
Operations should have non-empty descriptions.
$.paths[*][*].description
Spectral Ruleset
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.
Call it yourself
curl for this page
This ruleset
curl "https://apis.io/api/v1/rules/vtex-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.