What we monitor, and whether it is answering (OPEN — no key, not metered)

The 254 official sources behind the enforcement layer — agency newsrooms, AG press feeds, court dockets — with the last successful read, the fault state and whether each is stale against its own silence budget.

IT PUBLISHES THE BAD NEWS. 132 of 254 are enabled and 123 are stale (measured 2026-08-22). Those go out as they are, on the same argument /v1/us-law/jurisdictions publishes its OLDEST verification stamp: an enforcement product whose coverage table only showed the healthy sources would be advertising, not data.

FAULTS ARE CLASSIFIED, NOT QUOTED. last_fault_reason_code is a closed vocabulary (blocked, unauthorized, not_found, timeout, adapter_missing, egress_unavailable, other) with a one-line label; the raw internal fault text never leaves the server.

Read this before concluding anything from an empty /enforcement/matters result: a stale source is a gap in OUR monitoring, never a statement that an authority has taken no action.

get/enforcement/sources

Request

  • Base URL: https://ai-law-tracker.com/api/v1
  • URL: https://ai-law-tracker.com/api/v1/enforcement/sources
  • Auth: one of:
    • none
    • API key in header X-API-Key
    • HTTP bearer

Query parameters

jurisdiction_level'federal' | 'state' | 'multistate' | 'territory' | 'local' | 'international'
is_enabledboolean
is_staleboolean

true = sources not read inside their own max_silence_hours.

Response

Source health.

api_versionstring
dataobject[]

Changes

No recorded changes to this operation across all 1 revision of this API.