Food Safety and Inspection Service · API Governance Rules

Food Safety and Inspection Service API Rules

Spectral linting rules defining API design standards and conventions for Food Safety and Inspection Service.

0 Rules
View Rules File View on GitHub

Spectral Ruleset

Raw ↑
x-name: FSIS Recall Usage Rules
description: Operational and consumption rules for the FSIS Recall API.
rules:
  - id: open-data
    statement: The API is open and does not require authentication.
    severity: informational
  - id: client-side-filtering
    statement: All filtering must be performed client-side; the API returns the entire dataset.
    severity: required
  - id: cache-responses
    statement: Cache responses locally to avoid repeated full-dataset downloads.
    rationale: The endpoint returns the full recall corpus on every request.
    severity: advisory
  - id: not-emergency-channel
    statement: Do not rely on the API alone for emergency public alerting.
    rationale: USDA FSIS has authoritative public alerting channels separate from this API.
    severity: required
  - id: respect-government-source
    statement: Cite USDA FSIS as the data source when redistributing.
    severity: advisory

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/fsis-recall-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.