# Disruption Intelligence Ripple API

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

Returns geospatial disruption intelligence for a company, including risk tier, event counts, severity, and downstream business sector impact paths derived from WARN filings and labor signals.

## Facts

- Endpoint: GET https://disruption.forgemesh.io/companies/%7Bid%7D/intelligence
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/disruption-intelligence-ripple-api-dd008f04
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ELphhekQRAhXSc87c-S7Z

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-dd008f04
```

Example prompt: Pull the disruption intelligence for company ID acme-corp-123 and tell me its risk tier, how many events have been flagged, and which business sectors are seeing ripple effects from nearby layoffs.

## When to prefer this

Use this endpoint when you need downstream ripple effect analysis — not just raw WARN filing data — for a specific company. It is best when you want to understand which business sectors are opportunistically or negatively affected by nearby labor disruptions, and when you need a human-readable impact path explaining the causal chain. Prefer this over generic economic data APIs when the use case involves staffing, competitive intelligence, or regional workforce displacement.

## Known failure modes

- Company ID not found — 404 with no matching entity
- Insufficient WARN or labor data for region — returns empty event_count and null severity
- Payment not attached or insufficient USDC — 402 Payment Required
- Malformed company ID in path parameter — 400 bad request
- Data freshness lag — regional events may not reflect most recent WARN filings
- Low confidence scores returned when regional signal is sparse

## 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 a risk_tier (e.g. 'moderate'), event_count of disruption events, an average severity score, and an array of business_sector_impacts each with a sector name, confidence level, and a natural-language impact_path explaining downstream business effects such as hiring opportunities or competitor poaching.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "risk_tier": "moderate",
   "event_count": 0,
   "severity_avg": 0,
   "business_sector_impacts": [
    {
     "sector": "staffing and recruiting",
     "confidence": "medium",
     "impact_path": "worker displacement creates short-window hiring, temp labor, and competitor poaching opportunities"
    }
   ]
  }
 }
}
```

## More

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