# Disruption Intelligence Ripple API – Company Profile

> Disruption Intelligence Ripple API – Company Profile 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 WARN filing signals, labor events, regional economic impacts, and downstream ripple effects on business partners.

## Facts

- Endpoint: GET https://disruption.forgemesh.io/companies/%7Bid%7D
- 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-company-profile-19f394fb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Vcun74SuOfcSPbDZfKFX7

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-company-profile-19f394fb
```

Example prompt: Pull the Disruption Intelligence Ripple profile for company ID 'acme-corp-42' — I want to see their WARN filing history, disruption scores, and any downstream ripple effects on their regional partners.

## When to prefer this

Choose this endpoint when you need geospatial, labor-signal-backed disruption intelligence for a specific company — particularly when WARN filings, regional economic events, and downstream ripple effects on business partners are needed. Prefer this over generic news or financial APIs when labor disruption signals and location-level granularity matter.

## Known failure modes

- Invalid or unknown company ID returns empty or error response
- Company not indexed in WARN or labor signal data sources returns sparse results
- Payment failure in USDC on Base causes 402 response and no data returned
- Malformed company ID path parameter causes 400 or 404 error
- Stale data if WARN filings have not been recently indexed

## 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 scores (array), a company profile object, associated locations (array), and recent labor/economic events (array) — providing a full picture of the company's current disruption status and downstream effects.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "scores": [],
  "company": {},
  "locations": [],
  "recent_events": []
 }
}
```

## More

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