# PHMSA Pipeline Incident Search

> PHMSA Pipeline Incident Search is a paid API for AI agents from api.govparse.io, paid per call via x402, $1.25/call, status unknown (last checked 2026-09-14).

Searches PHMSA pipeline incident records (2010+) by operator, mode, state, cause, commodity, cost, and date — returning entity-resolved incident details including casualties, costs, and cause.

## Facts

- Endpoint: GET https://api.govparse.io/v1/phmsa/incidents/search
- Price: $1.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/phmsa-pipeline-incident-search-d6c511de
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_p7vxK0-zU4D9z8l-PTcOO

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 phmsa-pipeline-incident-search-d6c511de
```

Example prompt: Pull all PHMSA hazardous liquid pipeline incidents involving Enbridge in Texas since 2020 where the cause was corrosion — sort by total cost descending and give me the top 25.

## When to prefer this

Use this endpoint when you need to search PHMSA pipeline incident records with flexible filters across operator, mode, state, cause, commodity, cost, or date. Prefer it over general web search when you need structured, machine-readable incident data with entity-resolved operators and consistent cost/casualty fields. Best for compliance research, operator due diligence, insurance/claims triggers, environmental monitoring, and regulatory analysis of US pipeline safety incidents from 2010 onward.

## Known failure modes

- No results returned when operator name spelling doesn't match PHMSA records — use operator_id for precision
- Invalid mode string returns an error — must be gas_distribution, hazardous_liquid, or gas_transmission
- Date format errors if since parameter is not YYYY-MM-DD
- Limit exceeding 100 is capped or rejected
- Overly broad queries may hit pagination limits — use offset and limit to paginate

## How this service works

Which pipeline operators had a reported incident? Search PHMSA pipeline incidents (2010+, gas distribution / hazardous liquid / gas transmission) by operator, operator_id, mode, state, cause, commodity, minimum cost (min_cost), year, or incident date (since). Returns the incident, its entity-resolved operator, location, commodity released, casualties, cost, and cause — a remediation / integrity / claims trigger. Reported exactly as recorded, not a safety judgment.

## Output

Returns a list of PHMSA pipeline incident records matching the search criteria, each including the entity-resolved operator name and ID, incident date, location (state), pipeline mode, commodity released, incident cause, fatalities, injuries, and total cost — reported exactly as recorded in PHMSA data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {
  "input": {
   "type": "object",
   "required": [],
   "properties": {
    "mode": {
     "type": "string",
     "examples": [
      "hazardous_liquid"
     ],
     "description": "Pipeline mode (gas_distribution | hazardous_liquid | gas_transmission), CSV."
    },
    "sort": {
     "type": "string",
     "examples": [
      "total_cost:desc"
     ],
     "description": "incident_date | total_cost | fatalities :asc|:desc. Default incident_date:desc."
    },
    "year": {
     "type": "string",
     "examples": [
      "2025"
     ],
     "description": "Incident year."
    },
    "cause": {
     "type": "string",
     "examples": [
      "CORROSION"
     ],
     "description": "Incident cause fragment."
    },
    "limit": {
     "type": "integer",
     "examples": [
      25
     ],
     "description": "Max rows (default 25, cap 100)."
    },
    "since": {
     "type": "string",
     "examples": [
      "2025-01-01"
     ],
     "description": "Incident date on/after this date (YYYY-MM-DD)."
    },
    "state": {
     "type": "string",
     "examples": [
      "TX"
     ],
     "description": "Incident state code(s), CSV."
    },
    "offset": {
     "type": "integer",
     "examples": [
      0
     ],
     "description": "Rows to skip."
    },
    "min_cost": {
     "type": "string",
     "examples": [
      "1000000"
     ],
     "description": "Minimum total cost (USD)."
    },
    "operator": {
     "type": "string",
     "examples": [
      "Enbridge"
     ],
     "description": "Operator name — suffix/punctuation-insensitive."
    },
    "commodity": {
     "type": "string",
     "examples": [
      "CRUDE OIL"
     ],
     "description": "Commodity released fragment."
    },
    "entity_id": {
     "type": "string",
     "examples": [
      "b7f3e2d1-4a5c-4e6f-8a9b-0c1d2e3f4a5b"
     ],
     "description": "Resolved operator entity UUID."
    },
    "operator_id": {
     "type": "string",
     "examples": [
      "15007"
     ],
     "description": "PHMSA operator id(s), CSV."
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/phmsa-pipeline-incident-search-d6c511de/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.govparse.io](https://www.zero.xyz/host/api.govparse.io/llms.txt)