# Delx Incident Severity

> Delx Incident Severity is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-13).

Classifies operational incident severity from explicit impact signals, returning a deterministic machine-readable JSON result for use in enterprise agent workflows.

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/incident-severity
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-incident-severity-3957deb9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bdSi_ZXw4DfzX_txO7hu1

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 delx-incident-severity-3957deb9 -d '<json body>'
```

Example prompt: Classify the severity of this incident based on its impact signals — users in three regions are unable to complete checkout and error rates have spiked to 40% in the last 5 minutes.

## When to prefer this

Use this endpoint when you need a fast, stateless, deterministic severity classification of an operational incident before routing to escalation, policy, or integration systems. Prefer it over manual triage or LLM reasoning alone when you need consistent machine-readable output for automated workflow gating. Ideal as a bounded preflight step inside enterprise agent pipelines where reproducibility and auditability matter.

## Known failure modes

- Missing or malformed impact object returns a 400 validation error
- Ambiguous or empty impact signals may result in a low-confidence or default severity classification
- Payment failure (insufficient USDC balance or x402 protocol error) blocks execution
- Overly sparse impact data may yield a conservative or indeterminate severity level

## How this service works

Classify operational incident severity from explicit impact signals. Use it as a bounded preflight or analysis step inside an enterprise agent workflow before data, policy, integration, security, or commercial decisions reach production. Returns deterministic machine-readable JSON for $0.003 USDC via x402 on Base. Execution is first-party, local-only, stateless, memory-only, and has no paid upstream or input retention. Results are advisory; the caller remains responsible for authorization and p…

## Output

Returns a deterministic machine-readable JSON object containing the classified severity level for the incident (e.g. critical, high, medium, low) based on the provided impact signals, suitable for programmatic consumption in automated enterprise workflows.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "impact": {
   "type": "object",
   "description": "Input field: impact."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "score": 35,
  "schema": "delx/util-incident-severity/v1",
  "signals": [
   "outage",
   "payments"
  ],
  "advisory": "Map this result to the organization's incident policy.",
  "severity": "sev2"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-incident-severity-3957deb9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.delx.ai](https://www.zero.xyz/host/api.delx.ai/llms.txt)