# Delx Commerce ETag Match

> Delx Commerce ETag Match 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).

Compares two ETag values to determine whether they match, supporting weak and strong comparison modes.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/etag-match?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-etag-match-76fb0091
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Q9kSzNwIF-cMa6O8VMrif

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-etag-match-76fb0091 -d '<json body>'
```

Example prompt: Check if these two ETags match: '"abc123"' and '"abc123"' — I need to know if they're equal so I can decide whether to use the cached version.

## When to prefer this

Use this endpoint when you need a standards-compliant, pay-per-use ETag comparison without setting up any infrastructure. Ideal for AI agents performing HTTP cache validation, conditional request logic, or resource identity checks in automated workflows where a lightweight, no-signup utility is preferred over implementing ETag comparison logic inline.

## Known failure modes

- Missing or malformed ETag inputs may return an error or unexpected match result
- Invalid ETag format (not quoted strings) may cause incorrect comparison
- Payment failure via x402 protocol blocks the request from being processed
- Non-string inputs may cause schema validation errors

## 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 indicating whether the two provided ETags match (match: true/false), the comparison mode used (e.g. 'list'), whether the first ETag is weak (weak_a: boolean), and the schema version identifier. The 'ok' field confirms the request was processed successfully.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "etag": {
   "type": "string",
   "description": "Input field: etag."
  },
  "other": {
   "type": "string",
   "description": "Input field: other."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "mode": "list",
  "match": true,
  "schema": "delx/util-etag-match/v1",
  "weak_a": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-etag-match-76fb0091/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)