# ForgeMesh Disruption Intelligence – Sector Impact Paths by Signal

> ForgeMesh Disruption Intelligence – Sector Impact Paths by Signal 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 one event propagates across industry sectors.

## Facts

- Endpoint: GET https://disruption.forgemesh.io/gold/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-intelligence-sector-impact-paths-by-signal-45fa5570
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_64LRODtWDWx_5F_BeoaY8

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-intelligence-sector-impact-paths-by-signal-45fa5570
```

Example prompt: Using ForgeMesh disruption intelligence, show me the downstream business-sector impact paths for signal ID abc123 — I want to understand which industries are in the ripple zone.

## When to prefer this

Use this endpoint when you have a specific disruption signal ID and need to understand its downstream ripple effects across business sectors. Ideal for economic impact analysis, supply chain risk assessment, and sector exposure modeling tied to labor market events like WARN filings. Prefer this over the general timeline or company profile endpoints when the analytical goal is cross-sector propagation rather than event history or entity details.

## Known failure modes

- Signal ID not found – 404 if the provided :id does not exist in the system
- Payment required – 402 if x402 payment header is missing or insufficient (requires $0.15 USDC)
- No sector impacts available – empty result if the signal has no mapped downstream paths yet
- Invalid signal type – error if the signal does not support sector-impact path analysis
- Rate limiting – 429 if too many requests are made in a short window

## How this service works

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

## Output

A structured list of downstream sector impact paths ('Ripple Paths') showing how the queried disruption signal propagates through business sectors, including affected industries, impact depth, and directional relationships between them.

## 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-intelligence-sector-impact-paths-by-signal-45fa5570/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)