# Delx Incident Timeline

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

Normalize and chronologically sort a list of incident events into a structured, machine-readable JSON timeline

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/incident-timeline
- Price: $0.002/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-timeline-dcf0bba5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_diA0cvvkBP_SjWT30yjKV

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-timeline-dcf0bba5 -d '<json body>'
```

Example prompt: I have a messy list of incident events from last night's outage — timestamps are all over the place and the format is inconsistent. Can you normalize and sort them into a clean chronological timeline I can feed into our post-mortem workflow?

## When to prefer this

Choose this endpoint when you need a deterministic, stateless, local-only normalization and chronological sort of incident events without relying on an upstream AI or external provider. It is ideal as a preflight step in autonomous workflows that need structured, ordered incident data before taking action — especially when predictability, no side effects, and low cost ($0.002 USDC) matter. Prefer it over general-purpose LLM sorting when you need guaranteed machine-readable output format and structured validation feedback.

## Known failure modes

- Invalid or missing events array returns a structured validation error (not billed)
- Events exceeding 1000 items are rejected
- Malformed event objects may cause normalization errors
- Events with unparseable or missing timestamps may result in ordering ambiguity
- Network or payment authorization failures prevent execution

## How this service works

Normalize and chronologically order incident events into a machine-readable timeline. Use it before an autonomous workflow acts on untrusted input, changes an API, retries a request, or evaluates production reliability. Returns bounded machine-readable JSON for $0.002 USDC via x402 on Base. Execution is deterministic, first-party, local-only, stateless, and does not call an upstream provider; structured validation failures are not billed.

## Output

A bounded machine-readable JSON object containing the input events normalized and sorted chronologically. Each event is standardized in structure, and the overall timeline is ordered by time. Structured validation failures are returned as error responses without billing.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "events": {
   "type": "array",
   "items": {
    "type": "object"
   },
   "maxItems": 1000
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "events": [
   {
    "at": "2026-08-05T12:00:00+00:00",
    "event": "alert fired",
    "source": "monitor"
   }
  ],
  "schema": "delx/incident-timeline/v1",
  "ends_at": "2026-08-05T12:00:00+00:00",
  "starts_at": "2026-08-05T12:00:00+00:00",
  "event_count": 1
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-incident-timeline-dcf0bba5/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)