# Disruption Intelligence Ripple API – Event Timeline

> Disruption Intelligence Ripple API – 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).

Returns the full timeline of state transitions, versions, and relationships for a specific disruption event identified by ID

## Facts

- Endpoint: GET https://disruption.forgemesh.io/events/%7Bid%7D/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-intelligence-ripple-api-event-timeline-eae04b05
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AbgS0Cy47ZGtMt7gR-ZuV

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-intelligence-ripple-api-event-timeline-eae04b05
```

Example prompt: Pull the full Ripple timeline for disruption event ID evt_8821 — I want to see how it evolved, all the state transitions, and what downstream business effects were flagged.

## When to prefer this

Use this endpoint when you have a specific disruption event ID and need its full chronological history, including how the event evolved through different states and what downstream economic or business effects were identified. Best suited for deep-dive analysis of a known event rather than discovering new events.

## Known failure modes

- Event ID not found — returns empty or 404-equivalent event object
- Malformed event ID format — bad request response
- No timeline data available for a very recent or stub event
- Payment not processed in USDC on Base — 402 response blocking access
- Rate limiting or quota exceeded — throttle error

## How this service works

Paid layoff risk and WARN filing intelligence via x402. Company risk scores, ripple effects, and geographic disruption data.

## Output

A JSON object containing the disruption event record, an array of versioned snapshots of the event over time, an array of state transitions documenting how the event progressed, and an array of related events or relationships showing downstream ripple effects on regional business and labor.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "event": {},
  "versions": [],
  "transitions": [],
  "relationships": []
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/disruption-intelligence-ripple-api-event-timeline-eae04b05/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)
