Echo Case Crs1 Compliance Schedules Structure

This section provides compliance schedule milestone activity information for a subset of EPA judicial consent decrees with compliance schedules.

Type: object Properties: 7 Required: 7
GovernmentEnvironmentalOpen DataAir QualityWater QualityHazardous WasteComplianceEmissions

crs1_ComplianceSchedules is a JSON Structure definition published by EPA — U.S. Environmental Protection Agency, describing 7 properties, of which 7 are required. It conforms to the https://json-structure.org/meta/core/v0/# meta-schema.

Properties

ActualDate EventAmount FacilityFRSID ScheduleCommentText ScheduleDate ScheduleEventDescription ScheduleNumber

Meta-schema: https://json-structure.org/meta/core/v0/#

JSON Structure

Raw ↑
{
  "$schema": "https://json-structure.org/meta/core/v0/#",
  "$id": "https://raw.githubusercontent.com/api-evangelist/epa/refs/heads/main/json-structure/echo-case-crs1-compliance-schedules-structure.json",
  "name": "crs1_ComplianceSchedules",
  "description": "This section provides compliance schedule milestone activity information for a subset of EPA judicial consent decrees with compliance schedules.",
  "type": "object",
  "properties": {
    "ActualDate": {
      "type": "string",
      "description": "The actual date on which the Compliance Schedule event was completed/achieved.",
      "example": "08/12/1988"
    },
    "EventAmount": {
      "type": "string",
      "description": "The dollar amount of a scheduled payment initiated through a penalty action or a cost recovery pursuant to a Final Order.",
      "example": "$100.00"
    },
    "FacilityFRSID": {
      "type": "string",
      "description": "The number assigned by the Facility Linkage Application that is used to associate facility records from multiple environmental database systems that are known or believed to represent the same facility.",
      "example": "12345"
    },
    "ScheduleCommentText": {
      "type": "string",
      "description": "The free-text field used to store descriptive Compliance Schedule information.",
      "example": "string"
    },
    "ScheduleDate": {
      "type": "string",
      "description": "The date the event is scheduled to be completed (i.e. the due date).",
      "example": "string"
    },
    "ScheduleEventDescription": {
      "type": "string",
      "description": "The description of the particular event with which the permittee is scheduled to comply.",
      "example": "string"
    },
    "ScheduleNumber": {
      "type": "string",
      "description": "A two-digit number which in combination with the Schedule Type and NPDES ID uniquely identifies a Compliance Schedule.",
      "example": "string"
    }
  },
  "required": [
    "FacilityFRSID",
    "ScheduleNumber",
    "ScheduleCommentText",
    "ScheduleEventDescription",
    "ScheduleDate",
    "ActualDate",
    "EventAmount"
  ]
}

Work with this as data

Every JSON Structure 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 json structure

4 MCP tools reach this
  • find_json_structuresBrowse and filter every JSON Structure 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 JSON Structure
curl "https://apis.io/api/v1/json-structures/echo-case-crs1-compliance-schedules-structure"
All json structure
curl "https://apis.io/api/v1/json-structures?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.