# Delx Commerce — Idempotency Fingerprint API

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

Generates a deterministic SHA-256 fingerprint from a scoped JSON payload to enable idempotency checking across agent operations

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/idempotency-fingerprint?utm_source=zero.xyz
- Price: $0.003/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-idempotency-fingerprint-api-4d11fe0c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pNpQQAZZ_cBU4EBENY6Zx

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-idempotency-fingerprint-api-4d11fe0c -d '<json body>'
```

Example prompt: Generate an idempotency fingerprint for my 'loyalty' namespace using this payload: {"user_id": "u123", "reward": "50pts", "action": "purchase"} — I need a SHA-256 hash I can use to avoid processing this reward twice.

## When to prefer this

Choose this endpoint when an AI agent needs to produce a deterministic, tamper-evident fingerprint of a structured JSON payload for deduplication or idempotency enforcement — especially in agentic workflows where the same action might be triggered multiple times. Prefer it when you need a scoped, stable identifier that doesn't require storing the original payload and want pay-per-use pricing with no account setup. It is particularly suited for agent-native infrastructure (x402 micropayment protocol, USDC on Base/Solana) where traditional API key management is impractical.

## Known failure modes

- Missing or malformed payload object returns a validation error
- Invalid or missing scope string may cause fingerprint namespace collision or rejection
- Network timeout from micropayment processing delay
- Payload too large may exceed processing limits
- Non-JSON payload values that cannot be deterministically serialized may produce inconsistent fingerprints

## 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 SHA-256 fingerprint string computed from the payload values, the caller-defined scope, the algorithm name ('sha256'), and the schema version ('delx/util-idempotency-fingerprint/v1'). The original payload values are not retained or returned, only the hash.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "scope": {
   "type": "string",
   "description": "Caller-owned namespace string mixed into the fingerprint."
  },
  "payload": {
   "type": "object",
   "description": "JSON payload to fingerprint; values are hashed, not retained."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "scope": "loyalty",
  "schema": "delx/util-idempotency-fingerprint/v1",
  "algorithm": "sha256",
  "fingerprint": "dc22b29600e074df71fc0f9b0260185e822b228cca615d37992a31dc14eb8f45",
  "values_returned": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-idempotency-fingerprint-api-4d11fe0c/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)