# Disruption Intelligence Ripple API – Regional Disruption Lookup

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

Returns geospatial disruption intelligence for a US state, including WARN filings, labor signals, and downstream regional economic effects.

## Facts

- Endpoint: GET https://disruption.forgemesh.io/regions/%7Bstate%7D
- 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-regional-disruption-lookup-ed9a8fbf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7aGIVBUIM84v2b7QFgtoP

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-regional-disruption-lookup-ed9a8fbf
```

Example prompt: Pull the disruption intelligence ripple data for Texas — I need to see any WARN filings, labor signals, and downstream regional economic effects across all counties in that state.

## When to prefer this

Use this endpoint when you need state-level geospatial disruption intelligence derived from WARN Act filings and labor market signals, especially when analyzing downstream or ripple economic effects on regional businesses. Prefer this over general news or economic APIs when you need structured, county-level labor disruption data with business impact context. Best suited for supply chain risk analysis, economic research, or business intelligence use cases targeting specific US states.

## Known failure modes

- Invalid or unrecognized state code returns empty data array with county_count of 0
- Payment not received or USDC transaction fails — HTTP 402 returned, request blocked
- State path parameter missing or malformed URL — likely 404 or 400 error
- No disruption events currently indexed for that state — returns empty data array
- Rate limiting or quota exceeded on the x402 payment facilitator side

## 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 disruption data for the requested state, including an array of disruption events (WARN filings, labor signals, regional economic events), the state identifier, and a county count indicating how many counties have active disruption signals.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": [],
  "state": "",
  "county_count": 0
 }
}
```

## More

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