# BNM Data Shop – FCC Enforcement Bureau Orders

> BNM Data Shop – FCC Enforcement Bureau Orders is a paid API for AI agents from ticks.bnm.farm, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-20).

Returns a list of FCC Enforcement Bureau orders and notices of violation as structured JSON, sourced from the FCC daily digest.

## Facts

- Endpoint: GET https://ticks.bnm.farm/fcc-eb-orders?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bnm-data-shop-fcc-enforcement-bureau-orders-faa876ce
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Pz7OqsdR9pOgZ_fo3XYUl

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability bnm-data-shop-fcc-enforcement-bureau-orders-faa876ce
```

Example prompt: Pull the latest FCC Enforcement Bureau orders from the BNM Data Shop so I can see which broadcasters recently received notices of violation.

## When to prefer this

Choose this endpoint when you need structured, machine-readable FCC Enforcement Bureau orders and notices of violation without manually scraping the FCC daily digest. It is ideal for compliance monitoring, legal research, regulatory alerting pipelines, and broadcast industry surveillance where you need per-record detail including docket numbers, institution names, and source document URLs in a consistent JSON schema.

## Known failure modes

- HTTP 402 returned if payment header is missing or invalid (x402 payment required)
- Empty records array if no FCC enforcement orders were published on the queried date
- Stale data if FCC daily digest has not yet updated
- Network timeout or 5xx if upstream FCC docs endpoint is unavailable
- Malformed response if FCC source document structure changes unexpectedly

## How this service works

Official public data as JSON. Unpaid paid routes return HTTP 402.

## Output

A JSON object containing a boolean success flag, a product identifier ('fcc-eb-order-bodies'), a status string, fetch timestamp, asOf date, source URL, total record count, an array of record objects (each with id, url, date, firm name, and type), and an array of card objects (each with id, body text, date, kind, title, case number, docket, citation, source URL, document ID, and institution name).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "headers": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    },
    "queryParams": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string"
    },
    "schema": {
     "type": "object"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "schema": {
  "type": "object",
  "required": [
   "ok",
   "product",
   "status",
   "fetchedAt",
   "asOf",
   "source",
   "recordCount",
   "records",
   "cards"
  ],
  "properties": {
   "ok": {
    "type": "boolean"
   },
   "asOf": {
    "type": "string"
   },
   "cards": {
    "type": "array",
    "items": {
     "type": "object"
    }
   },
   "source": {
    "type": "string"
   },
   "status": {
    "type": "string"
   },
   "product": {
    "type": "string"
   },
   "records": {
    "type": "array",
    "items": {
     "type": "object"
    }
   },
   "fetchedAt": {
    "type": "string"
   },
   "recordCount": {
    "type": "integer"
   }
  }
 },
 "example": {
  "ok": true,
  "asOf": "2026-09-18",
  "cards": [
   {
    "id": "DA-26-1006",
    "body": "Federal Communications Commission. Enforcement Bureau. DA 26-1006. Notice of Violation issued to Vazquez Broadcasting Corporation.",
    "date": "2026-09-18",
    "kind": "Notice of Violation",
    "title": "DA 26-1006",
    "caseNo": "EB-FIELDNER-24-00037648",
    "docket": "EB-FIELDNER-24-00037648",
    "citation": "DA 26-1006",
    "sourceUrl": "https://docs.fcc.gov/public/attachments/DA-26-1006A1.pdf",
    "documentId": "DA-26-1006A1.pdf",
    "institution": "Vazquez Broadcasting Corporation, licensee of AM Station WSDS, Salem Township, Michigan"
   }
  ],
  "source": "https://www.fcc.gov/edocs/daily-digest",
  "status": "ok",
  "product": "fcc-eb-order-bodies",
  "records": [
   {
    "id": "DA-26-1006",
    "url": "https://docs.fcc.gov/public/attachments/DA-26-1006A1.pdf",
    "date": "2026-09-18",
    "firm": "Vazquez Broadcasting Corporation, licensee of AM Station WSDS, Salem Township, Michigan",
    "type": "fcc-eb-orders"
   }
  ],
  "fetchedAt": "2026-09-22T00:00:00.000Z",
  "recordCount": 1
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bnm-data-shop-fcc-enforcement-bureau-orders-faa876ce/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ticks.bnm.farm](https://www.zero.xyz/host/ticks.bnm.farm/llms.txt)