# Delx Commerce — EVM Hex Data Normalize

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

Normalizes raw data into valid, prefixed EVM hex format and returns byte count, with no data retention.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/evm-hex-data-normalize?utm_source=zero.xyz
- Price: $0.001/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-evm-hex-data-normalize-bf8e34bf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HM0KmggLlpg_bOvfTy85t

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-evm-hex-data-normalize-bf8e34bf -d '<json body>'
```

Example prompt: Can you normalize this data into proper EVM hex format for me — '0xabcd' — and tell me how many bytes it is?

## When to prefer this

Use this endpoint when you need a lightweight, verifiable, pay-per-call utility to normalize EVM hex calldata before submitting blockchain transactions. It is ideal for agent pipelines that require auditability (SHA256 evidence, no-retention proof) without standing up infrastructure. Prefer it over manual normalization when you need deterministic results with a verifiable audit trail.

## Known failure modes

- Input data exceeds 8192 character limit — request rejected
- Malformed or non-hex input that cannot be normalized — returns error status
- Payment failure via x402 — 402 response before processing begins
- Network timeout or service unavailability

## 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: the normalized 0x-prefixed hex string, the byte count, a status field ('pass'), the operation name, and an evidence block confirming no external calls were made and no input data was retained (includes SHA256 of the input for auditability).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "type": "string",
   "maxLength": 8192,
   "description": "Data supplied to EVM Hex Data Normalize; used only for this bounded calculation and processed in memory without retention."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "data": "0xabcd00",
   "byte_count": 3
  },
  "schema": "delx/util-evm-hex-data-normalize/v1",
  "status": "pass",
  "evidence": {
   "retained": false,
   "input_sha256": "9944dc2e2c04677c19c2d73f2496d153a58e6d3177f2db401b47c86a5fb08dca",
   "external_calls": 0
  },
  "operation": "evm_preflight:evm_hex_data_normalize"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-evm-hex-data-normalize-bf8e34bf/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)