Vectara · API Governance Rules
Vectara API Rules
Spectral linting rules defining API design standards and conventions for Vectara.
4 Rules
error 2
warn 2
Rule Categories
vectara
Rules
warn
vectara-operation-summary-title-case
Operation summaries must be in Title Case.
$.paths[*][get,post,patch,put,delete].summary
warn
vectara-path-kebab-or-snake
Path segments use lowercase, hyphen, or underscore — never camelCase.
$.paths
error
vectara-uses-bearer-or-apikey
Vectara endpoints must declare ApiKeyAuth or OAuth2 security.
$.security
error
vectara-success-status-codes
Operations must declare a 2xx success response.
$.paths[*][get,post,patch,put,delete].responses
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/vectara-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.