Example: Run Regulatory Checks

Example • advanced • regulatory workflow

Run regulatory checks

Turn SmartAPIs regulatory routes into a practical compliance-style workflow while staying honest about source grounding and non-advice boundaries.

Requires API key Paid route MCP-ready Not legal advice

Title

Run regulatory checks

Problem solved

Screen a facility by regulatory records, then generate a workflow brief for watch-style operations.

Required route or routes

GET /v1/regulatory/licenses/search, GET /v1/workflows/regulatory-site-brief/{facility_id}

Auth expectation

Both routes require X-API-Key with regulatory:read and workflow access.

Request snippet

curl

curl -H "X-API-Key: $SMARTAPIS_API_KEY" \
  "https://smartapis.net/v1/regulatory/licenses/search?region_id=new-york-city&q=food&limit=3"

curl -H "X-API-Key: $SMARTAPIS_API_KEY" \
  "https://smartapis.net/v1/workflows/regulatory-site-brief/fac_nyc_001"

Response snippet

{
  "facility_id": "fac_nyc_001",
  "summary": "Recent inspection cadence is stable.",
  "signals": ["license_active", "inspection_history_available"],
  "legal_notice": "Informational only; not legal advice."
}

Next step

Attach the facility ID to watch automation and export attribution with each downstream alert.

Caveats / legal posture

This output is an operational summary, not legal advice. Preserve official source meaning and attribution.