# Delx Commerce — Log Event Normalize

> Delx Commerce — Log Event Normalize 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).

Parses and normalizes raw log text into a structured log event object with level, message, service, trace ID, and timestamp fields.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/log-event-normalize?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-log-event-normalize-1ef9987b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vZc_a5oLSkIxNTq2Z_dg2

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-log-event-normalize-1ef9987b -d '<json body>'
```

Example prompt: I have this raw log line — 'ERROR 2026-08-05T12:00:00Z upstream-service: upstream timeout' — can you normalize it into a structured log event with level, message, service, trace ID, and timestamp?

## When to prefer this

Choose this endpoint when you need to convert unstructured or freeform log text into a consistent, machine-readable event schema — especially in agent pipelines that need to route, alert on, or store logs in a structured format. Particularly useful when logs come from heterogeneous sources with varying formats. The pay-per-call x402 model (no signup, $0.002 USDC) makes it suitable for sporadic or agent-driven invocations without managing API keys.

## Known failure modes

- log_text exceeds 1,000,000 character limit — request rejected
- log_text is empty or missing — may return null fields or error
- ambiguous log format with no detectable level — level field may be null
- no timestamp found in log text — timestamp field may be null or estimated
- payment failure via x402 — HTTP 402 returned before processing

## 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 normalized log event with fields: level (e.g. 'error', 'warn'), message (extracted log message), service (service name or null), trace_id (trace identifier or null), and timestamp (ISO 8601). Also includes the detected source_format (e.g. 'common_text') and schema identifier ('delx/log-event-normalize/v1').

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "log_text": {
   "type": "string",
   "maxLength": 1000000
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "event": {
   "level": "error",
   "message": "upstream timeout",
   "service": null,
   "trace_id": null,
   "timestamp": "2026-08-05T12:00:00Z"
  },
  "schema": "delx/log-event-normalize/v1",
  "source_format": "common_text"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-log-event-normalize-1ef9987b/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)