Spendflo · API Governance Rules
Spendflo API Rules
Spectral linting rules defining API design standards and conventions for Spendflo.
4 Rules
error 2
warn 2
Rule Categories
spendflo
Rules
error
spendflo-operationid-required
All API operations should have an operationId for Spendflo integration mapping.
$.paths[*][get,post,put,patch,delete,options,head]
error
spendflo-summary-required
All API operations should have a summary describing the procurement action.
$.paths[*][get,post,put,patch,delete]
warn
spendflo-tags-required
Operations should be tagged by procurement domain (Vendors, Contracts, Spend, etc.).
$.paths[*][get,post,put,patch,delete]
warn
spendflo-error-responses-defined
Operations should document error responses for procurement workflow error handling.
$.paths[*][post,put,patch,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/spendflo-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.