# Disruption Intelligence Ripple API – Jurisdiction Endpoint

> Disruption Intelligence Ripple API – Jurisdiction Endpoint is a paid API for AI agents from disruption.forgemesh.io, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Returns geospatial disruption intelligence for a US state jurisdiction, including WARN filing events, labor signals, and downstream business impact data.

## Facts

- Endpoint: GET https://disruption.forgemesh.io/jurisdictions/%7Bstate%7D
- Price: $0.01/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-jurisdiction-endpoint-9faa3530
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AWc_j0Kwk6zMo8_jJaSv5

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-jurisdiction-endpoint-9faa3530
```

Example prompt: Pull the disruption intelligence ripple data for California — I want to see total WARN filing events, labor signals, and any downstream business effects happening in that state right now.

## When to prefer this

Use this endpoint when you need jurisdiction-level labor disruption and WARN filing intelligence for a specific US state, especially when downstream business ripple effects are needed for supply chain, investment, or economic risk analysis. Prefer this over general news APIs when you need structured, signal-based economic disruption data tied to a geographic region.

## Known failure modes

- Invalid or unrecognized state code returns an error or empty dataset
- State with no recent WARN filings returns zero events with empty data arrays
- Payment failure (402) if USDC payment on Base is not included or insufficient
- Rate limiting if too many calls are made in a short period
- Stale data if WARN filings have not been recently ingested for the requested jurisdiction

## 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 the jurisdiction name and total event count for disruption events in the requested state, derived from WARN filings, labor signals, and regional economic activity. May include downstream ripple effects on local businesses.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "jurisdiction": "",
   "total_events": 0
  }
 }
}
```

## More

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