# Disruption Intelligence Ripple API – Event History

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

Retrieves the version history of a specific disruption event, showing how its data and downstream business effects have evolved over time.

## Facts

- Endpoint: GET https://disruption.forgemesh.io/events/%7Bid%7D/history
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/disruption-intelligence-ripple-api-event-history-7fe7a195
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZnBdjzNF3Mi-FqomQKwoy

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-history-7fe7a195
```

Example prompt: Can you pull the full revision history for disruption event ID 'evt-00483' from the Ripple API — I want to see how many versions exist and how the downstream effects have changed since it was first filed?

## When to prefer this

Use this endpoint when you need to audit how a specific disruption event's data has evolved — e.g., tracking changes in layoff counts, affected regions, or downstream ripple effect estimates over time. Prefer this over the base event endpoint when change history and data provenance matter, not just current state.

## Known failure modes

- Event ID not found — returns empty versions array or 404-equivalent response
- Malformed event ID format — API may return an error or empty result
- No version history available for very recent events — version_count may be 0
- Payment not completed in USDC on Base — request blocked with 402 response
- Network timeout if event has an unusually large number of versions

## How this service works

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

## Output

Returns a JSON object containing the event ID, an array of versioned snapshots of the event (capturing how WARN filing data, labor signals, and downstream business effect estimates changed over time), and a total version count.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "event_id": "",
  "versions": [],
  "version_count": 0
 }
}
```

## More

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