# ForgeMesh Disruption Ripple - Sector Impact Paths

> ForgeMesh Disruption Ripple - Sector Impact Paths is a paid API for AI agents from disruption.forgemesh.io, paid per call via x402, $0.15/call, status unknown (last checked 2026-09-14).

Returns downstream business-sector impact paths for a given disruption signal, showing how it ripples through connected economic sectors

## Facts

- Endpoint: GET https://disruption.forgemesh.io/ripple/signals/:id/sector-impacts
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/forgemesh-disruption-ripple-sector-impact-paths-b5227839
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kEB8-neHbs44c6zDziSwi

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 forgemesh-disruption-ripple-sector-impact-paths-b5227839
```

Example prompt: Using the ForgeMesh Ripple API, show me all the downstream business sectors impacted by disruption signal ID abc-12345 — I want to see the full cascade of sector-level effects from that WARN filing.

## When to prefer this

Use this endpoint when you need to understand the downstream business-sector ripple effects of a specific disruption signal already identified in the ForgeMesh system. Ideal for supply chain risk analysis, economic impact modeling, or investment research where you need to trace how a labor or regional disruption propagates through connected industries. Prefer this over generic economic data APIs when working with WARN filing signals and structured disruption intelligence.

## Known failure modes

- Signal ID not found — 404 with no matching disruption record
- Invalid or malformed signal ID format — 400 bad request
- Payment not completed or insufficient USDC — 402 payment required
- Signal exists but no sector impact data yet computed — empty result set
- Rate limiting or quota exceeded — 429 too many requests

## How this service works

Ripple Paths: downstream business-sector impact paths for one signal

## Output

A structured list of downstream business sector impact paths originating from the specified disruption signal, showing how economic consequences cascade through connected industries and sectors based on WARN filings, labor signals, and regional economic data.

## 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/forgemesh-disruption-ripple-sector-impact-paths-b5227839/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)