# Mining Incidents Mine Profile API

> Mining Incidents Mine Profile API is a paid API for AI agents from miningincidents.org, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Returns a compliance and safety profile for a specific US mine by MSHA mine ID, including accident, citation, fatality, and penalty totals.

## Facts

- Endpoint: GET https://miningincidents.org/api/x402/mine/2602142
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mining-incidents-mine-profile-api-02ad2174
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hlOjJ2p4rgTGLzk7cPjY7

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 mining-incidents-mine-profile-api-02ad2174
```

Example prompt: Pull up the MSHA safety profile for mine ID 2602142 — I need the accident count, citation count, fatality count, and total penalties paid.

## When to prefer this

Use this endpoint when you need a quick, aggregated safety and compliance snapshot for a single known MSHA mine ID. It is faster and cheaper than scraping MSHA directly and provides pre-computed totals for accidents, citations, S&S violations, fatalities, and penalties. Prefer it over operator-level endpoints when the specific mine (not the parent operator) is the unit of analysis.

## Known failure modes

- Invalid or non-existent mine ID returns empty or error response
- Mine ID format mismatch (non-numeric or wrong length) may return 400 or empty result
- Mine with no recorded incidents returns zeroed aggregate fields
- API unavailable during weekly data refresh window

## How this service works

Mining Incidents is a free, searchable database and research tool covering every reportable US mining incident on file with MSHA. Search by mine, operator, controller, state, year, severity, or any keyword in the investigator's narrative. 1983 to present, refreshed weekly.

## Output

A JSON object containing the mine's name, state, commodity type, MSHA mine ID, aggregate accident count, citation count, S&S (significant and substantial) citation count, fatality count, total penalties proposed, total penalties paid, and a link to the human-readable mine page on miningincidents.org.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "mine": {
   "state": "KY",
   "mine_id": "4608791",
   "ss_count": 88,
   "commodity": "coal",
   "mine_name": "Example Mine",
   "accident_count": 12,
   "citation_count": 540,
   "fatality_count": 1,
   "penalty_paid_total": 98765,
   "penalty_proposed_total": 123456
  },
  "links": {
   "human_page": "https://miningincidents.org/mine/4608791"
  },
  "source": "Mining Incidents",
  "endpoint": "mine",
  "schema_version": 1
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mining-incidents-mine-profile-api-02ad2174/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from miningincidents.org](https://www.zero.xyz/host/miningincidents.org/llms.txt)