# ForgeMesh Disruption Event History

> ForgeMesh Disruption Event History is a paid API for AI agents from disruption.forgemesh.io, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Retrieves the full historical record of changes and updates for a specific disruption event by its ID

## Facts

- Endpoint: GET https://disruption.forgemesh.io/events/:id/history
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/disruption-forgemesh-io-5230d26c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nwEztBHfYiJbNOfbxYYlU

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 disruption-forgemesh-io-5230d26c
```

Example prompt: Can you pull up the full history of disruption event EVT-4821 so I can see how it has evolved since it was first reported?

## When to prefer this

Use this endpoint when you need to audit or trace the progression of a known disruption event over time, particularly when investigating how severity, relationships, or context changed. Prefer over the event timeline endpoint when you need raw historical state changes rather than a curated timeline narrative.

## Known failure modes

- Event ID not found — returns 404 or empty history
- Invalid or malformed event ID — returns 400 validation error
- Payment not completed — returns 402 requiring USDC payment
- Upstream data unavailable — returns 503 or partial results
- Rate limiting exceeded — returns 429

## How this service works

Event history

## Output

A chronological list of historical states, changes, or updates associated with the specified disruption event, including timestamps and modifications to event data such as severity, status, or related entities over time.

## 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"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "properties": {},
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "additionalProperties": true
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/disruption-forgemesh-io-5230d26c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from disruption.forgemesh.io](https://www.zero.xyz/host/disruption.forgemesh.io/llms.txt)