Zestful · API Governance Rules
Zestful API Rules
Spectral linting rules defining API design standards and conventions for Zestful.
7 Rules
error 2
warn 5
Rule Categories
zestful
Rules
warn
zestful-operation-id-camel-case
Operation IDs must use camelCase (Zestful convention)
$.paths[*][*].operationId
error
zestful-request-body-required
POST endpoints must define a required request body
$.paths[*].post
warn
zestful-ingredients-array-limits
Ingredients array must enforce min/maxItems limits
$.paths[*].post.requestBody.content.application/json.schema.properties.ingredients
error
zestful-response-200-defined
All operations must define a 200 response
$.paths[*][*].responses
warn
zestful-tags-defined
All operations must have tags
$.paths[*][*].tags
warn
zestful-security-defined
Operations should define security requirements
$.paths[*][*].security
warn
zestful-info-contact
API info must include contact details
$.info
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/zestful-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.