# ForgeMesh Disruption Event Timeline

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

Retrieves a chronological timeline of events for a specific disruption event by ID

## Facts

- Endpoint: GET https://disruption.forgemesh.io/events/:id/timeline
- Price: $0.05/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-413f1e46
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eE1w3LBGzZOd3mFV5CRNQ

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-413f1e46
```

Example prompt: Can you pull up the full timeline for disruption event ID EVT-4821 — I want to see how the situation unfolded step by step from start to current status?

## When to prefer this

Use this endpoint when you need to understand the chronological progression of a specific disruption event — how it evolved from initial occurrence through subsequent developments. Prefer this over the event history endpoint when you need time-ordered sequencing of a single event rather than a broader historical catalog. Ideal for root cause analysis, incident post-mortems, or monitoring how an ongoing disruption is unfolding.

## Known failure modes

- Event ID not found — 404 if the specified event does not exist
- Invalid event ID format — 400 if path parameter is malformed
- Payment not processed — 402 if x402 payment is missing or invalid
- Rate limiting — 429 if too many requests are made in a short period
- Event has no timeline data yet — empty timeline if event is newly created

## How this service works

Event timeline

## Output

A chronological timeline of a disruption event, including timestamped milestones, stages, and developments that occurred throughout the event lifecycle.

## 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-413f1e46/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)