# Delx Commerce — Incident Timeline API

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

Transforms a list of raw incident events into a structured, chronologically ordered incident timeline with start/end times and event count.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/incident-timeline?utm_source=zero.xyz
- Price: $0.002/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-timeline-api-5e08b070
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wKAWFqgZnROPWSbvSWty9

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-timeline-api-5e08b070 -d '<json body>'
```

Example prompt: I have a list of raw alert events from our monitoring system during last night's outage — can you build a structured incident timeline showing what happened in order, with start and end times?

## When to prefer this

Choose this endpoint when you have a raw, unordered collection of monitoring or incident events and need to produce a structured, chronologically ordered incident timeline with computed start/end bounds — especially in agent workflows where no signup or OAuth is required and micropayment-per-call via USDC is acceptable. Prefer this over building your own sorting/aggregation logic when you need a clean, schema-versioned output suitable for downstream reporting or post-mortems.

## Known failure modes

- Empty or malformed events array returns an error or empty timeline
- Events array exceeds 1000 item limit — request rejected
- Missing required timestamp fields in event objects cause processing errors
- Payment failure via x402 protocol results in 402 response and no data returned
- Malformed JSON body returns 400 error

## 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 with a sorted array of events (each with a timestamp, event description, and source), the schema identifier 'delx/incident-timeline/v1', a starts_at timestamp, an ends_at timestamp, and a total event_count.

## 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-commerce-incident-timeline-api-5e08b070/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)