# Delx Commerce — x402 Payment Lifecycle Reconciliation

> Delx Commerce — x402 Payment Lifecycle Reconciliation is a paid API for AI agents from commerce.delx.ai, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-02).

Reconciles and verifies x402 payment lifecycle artifacts (settlement reference, delivery receipt, payment response, and payment requirement) to produce a cryptographic verdict on whether a pay-per-result transaction was correctly completed.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/lifecycle-reconcile?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-commerce-x402-payment-lifecycle-reconciliation-97598d0b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4tMzY_m1xYOg-y2VrFpyz

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-x402-payment-lifecycle-reconciliation-97598d0b -d '<json body>'
```

Example prompt: Can you reconcile this x402 payment lifecycle for me — I have the settlement ref, delivery receipt, payment response, and payment requirement from a recent USDC-on-Base agent transaction, and I need to know if the verdict comes back as 'proven' with all fields matching?

## When to prefer this

Use this endpoint when an AI agent or payment orchestrator needs to verify that an x402 pay-per-result transaction completed correctly, by comparing all four lifecycle artifacts (settlement ref, delivery receipt, payment response, payment requirement) against each other. Prefer this over manual inspection when you need a structured, field-by-field proof verdict for audit, compliance, or dispute resolution — especially within the Delx Commerce / x402 ecosystem on Base or Solana. Note: this endpoint does not fetch on-chain state; it reconciles only the artifacts you supply.

## Known failure modes

- Missing or malformed artifacts produce incomplete field comparisons or a non-proven verdict
- Mismatched values across artifacts (e.g. different amounts) result in a non-proven status for that field
- No on-chain state is fetched, so the verdict reflects only the provided data — not actual blockchain finality
- Private keys or signatures included in input are rejected per bounded metadata rules
- Incomplete input objects may yield partial verdicts with some fields unresolved

## How this service works

Pay-per-result APIs for agents. No signup. Exact price. Verifiable delivery. USDC on Base + Solana via x402.

## Output

A JSON object containing a top-level 'verdict' (e.g. 'proven'), a 'limitation' disclaimer noting that verdicts are computed from provided artifacts only (no on-chain fetch), and a 'fields' map showing each key payment attribute (payTo, amount, network, resource) with its status ('proven' or otherwise) and the values reported by each artifact (settlement_ref, delivery_receipt, payment_response, payment_requirement).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "settlement_ref": {
   "type": "object",
   "description": "Bounded settlement reference metadata. No private keys."
  },
  "delivery_receipt": {
   "type": "object",
   "description": "Bounded delivery receipt metadata. No payload bodies or secrets."
  },
  "payment_response": {
   "type": "object",
   "description": "Bounded non-secret payment response metadata. No signatures."
  },
  "payment_requirement": {
   "type": "object",
   "description": "Bounded non-secret payment requirement metadata from the 402."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "fields": {
   "payTo": {
    "status": "proven",
    "values": {
     "settlement_ref": "0xabc",
     "delivery_receipt": "0xabc",
     "payment_response": "0xabc",
     "payment_requirement": "0xabc"
    }
   },
   "amount": {
    "status": "proven",
    "values": {
     "settlement_ref": "5000",
     "delivery_receipt": "5000",
     "payment_response": "5000",
     "payment_requirement": "5000"
    }
   },
   "network": {
    "status": "proven",
    "values": {
     "settlement_ref": "eip155:8453",
     "delivery_receipt": "eip155:8453",
     "payment_response": "eip155:8453",
     "payment_requirement": "eip155:8453"
    }
   },
   "resource": {
    "status": "proven",
    "values": {
     "settlement_ref": "https://api.example/pay",
     "delivery_receipt": "https://api.example/pay",
     "payment_response": "https://api.example/pay",
     "payment_requirement": "https://api.example/pay"
    }
   }
  },
  "verdict": "proven",
  "limitation": "Verdicts are computed from the artifacts you provide; we do not fetch chain state or contact the provider."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-x402-payment-lifecycle-reconciliation-97598d0b/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)