# Delx Commerce Record Fingerprint

> Delx Commerce Record Fingerprint 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).

Computes a deterministic SHA-256 fingerprint of a JSON record using sorted keys and compact separators for verifiable, canonical hashing.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/record-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-record-fingerprint-9da34889
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WSdcEhLtzKZuoMERWNBjV

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-record-fingerprint-9da34889 -d '<json body>'
```

Example prompt: Compute a canonical SHA-256 fingerprint of this JSON record for me so I can verify its integrity later: {"user_id": 42, "action": "purchase", "amount": 9.99}.

## When to prefer this

Choose this endpoint when you need a deterministic, canonical, and verifiable SHA-256 fingerprint of a JSON record without setting up your own hashing infrastructure. It is ideal for agents that need tamper detection, deduplication keys, or audit trail proofs in a pay-per-use model with no signup required. Prefer it over local hashing when you need a standardized canonicalization scheme (sorted keys, compact separators) that is reproducible across systems and languages.

## Known failure modes

- Missing or null 'record' field returns a validation error
- Non-serializable input values (e.g. circular references) may cause a processing error
- Payment failure via x402 results in a 402 Payment Required response before processing
- Malformed JSON body returns a 400 Bad Request
- Network timeout on the Base/Solana payment rails delays response

## 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 schema identifier (delx/util-record-fingerprint/v1), the hashing algorithm used (sha256), the computed hex fingerprint string, and a description of the canonicalization method (sorted JSON keys, compact separators, default string conversion).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "record": {
   "type": "object",
   "description": "Input field: record."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "schema": "delx/util-record-fingerprint/v1",
  "algorithm": "sha256",
  "fingerprint": "16e1f64597cd8012eca960a1f62715444c0999b8bd2ab48d479f544f05751c26",
  "canonicalization": "sorted JSON keys, compact separators, default string conversion"
 }
}
```

## More

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