# Delx Commerce Agent Result Provenance Check

> Delx Commerce Agent Result Provenance Check 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).

Validates whether an agent result payload contains the required provenance fields, returning a pass/fail status with a cryptographic input hash and evidence metadata.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/agent-result-provenance-check?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-agent-result-provenance-check-e7cf49ec
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aw7ISbrOCLIk7aEWHI2e8

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-agent-result-provenance-check-e7cf49ec -d '<json body>'
```

Example prompt: Can you check whether this agent result payload has valid provenance — run a provenance check on it and tell me if it passes, what fields are missing if any, and give me the SHA-256 hash of the input?

## When to prefer this

Choose this endpoint when you need a lightweight, cryptographically-attested, in-memory provenance check for agent results without storing any input data. Ideal for pay-per-call agent pipelines that require verifiable delivery compliance at minimal cost ($0.001 USDC), especially when operating under x402 payment protocol on Base or Solana and needing an audit-ready SHA-256 hash of the checked payload.

## Known failure modes

- Missing or malformed provenance object in request body returns validation error
- Provenance object exceeds 128 properties limit causing rejection
- Network timeout or service unavailability returns HTTP 5xx
- Payment not included or insufficient USDC via x402 returns HTTP 402
- Malformed JSON body causes parse error 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 with a top-level status ('pass' or 'fail'), a result object listing any missing_fields and a boolean provenance_present flag, an evidence block containing the SHA-256 hash of the input, the number of external calls made (always 0), and a retained flag (always false), plus schema and operation identifiers.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "provenance": {
   "type": "object",
   "description": "Provenance supplied to Agent Result Provenance Check; used only for this bounded calculation and processed in memory without retention.",
   "maxProperties": 128,
   "additionalProperties": true
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "missing_fields": [],
   "provenance_present": true
  },
  "schema": "delx/util-agent-result-provenance-check/v1",
  "status": "pass",
  "evidence": {
   "retained": false,
   "input_sha256": "0e9f76fd45b6b4e6392d9b4ea5720e2bda3cfc3d637149ab1fae8195b1ff6dad",
   "external_calls": 0
  },
  "operation": "delivery_contract:agent_result_provenance_check"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-agent-result-provenance-check-e7cf49ec/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)