# Mining Incidents Feature Request Upvote

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

Records a single upvote for a specific feature request on the Mining Incidents MSHA database platform

## Facts

- Endpoint: GET https://miningincidents.org/api/x402/feature-request/1/upvote
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mining-incidents-feature-request-upvote-b5d14a79
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_d15Ml38WS_GMrExE3Ih5j

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-feature-request-upvote-b5d14a79
```

Example prompt: Can you upvote feature request number 1 on Mining Incidents for me so the team knows I want that feature added to the MSHA database?

## When to prefer this

Use this endpoint when you want to express support for a specific feature request on the Mining Incidents MSHA database platform. This is the only endpoint for recording feature votes on this service; there is no alternative voting mechanism. Check the sibling feature-requests list endpoint first to find valid request IDs.

## Known failure modes

- Feature request ID not found — returns error if the specified ID does not exist
- Duplicate vote — the 'counted' field may return false if the same source votes twice
- Invalid request ID format — non-integer or missing ID may cause a bad request response
- Network or payment failure — $0.01 USDC payment may fail before the vote is recorded

## 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

Returns a JSON object confirming the upvote was recorded, including the updated upvote count for the feature request, the request ID, a confirmation note, schema version, and a link to the full feature requests list.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "note": "Upvote recorded.",
  "links": {
   "list": "https://miningincidents.org/api/x402/feature-requests"
  },
  "source": "Mining Incidents",
  "counted": true,
  "upvotes": 3,
  "endpoint": "feature_request_upvote",
  "request_id": 7,
  "schema_version": 1
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mining-incidents-feature-request-upvote-b5d14a79/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)