# Delx Commerce — Incident Severity Classifier

> Delx Commerce — Incident Severity Classifier is a paid API for AI agents from commerce.delx.ai, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-01).

Classifies an incident's severity level (e.g. sev1–sev4) and returns a numeric score and detected signals based on impact context

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/incident-severity?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-commerce-incident-severity-classifier-c63e453c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3vch8VWQ2jwdeZ5-Of_U_

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-commerce-incident-severity-classifier-c63e453c -d '<json body>'
```

Example prompt: We just had a payments outage affecting all customers — can you score the severity of this incident based on that impact and tell me whether it's a sev1 or sev2?

## When to prefer this

Choose this endpoint when you need a fast, pay-per-call, no-signup incident severity classification without managing a subscription or standing infrastructure. Ideal for AI agents that handle incident triage autonomously and need a verifiable, machine-readable severity score with signal detection. Prefer this over building a custom classifier when you need structured output (score + severity label + signals) and want USDC-based micropayment billing via x402 on Base or Solana.

## Known failure modes

- Missing or malformed 'impact' object in request body — likely returns a 400 Bad Request
- Insufficient detail in the impact field — may return a low-confidence or generic severity classification
- Payment failure via x402 protocol — endpoint returns 402 Payment Required if USDC payment is not included or insufficient
- Network timeout — no result returned if the upstream model is slow
- Ambiguous impact description — signals array may be empty or severity may be overly broad

## How this service works

Pay-per-result APIs for agents. No signup. Exact price. Verifiable delivery. USDC on Base + Solana via x402.

## Output

Returns a JSON object containing a numeric severity score (e.g. 35), a severity label (e.g. 'sev2'), an array of detected signals (e.g. ['outage','payments']), a schema identifier, and an advisory note recommending how to map the result to organizational policy.

## 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-commerce-incident-severity-classifier-c63e453c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from commerce.delx.ai](https://www.zero.xyz/host/commerce.delx.ai/llms.txt)