# x402 Lifecycle Reconcile

> x402 Lifecycle Reconcile is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-30).

Reconciles an x402 payment lifecycle end-to-end by comparing payment requirement, payment response, delivery receipt, and settlement reference metadata to produce a deterministic field-by-field verdict of proven, conflicting, or missing.

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/lifecycle-reconcile?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-lifecycle-reconcile-550cdc6e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xnEi98GIWn9q3UE1j2JdP

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 x402-lifecycle-reconcile-550cdc6e -d '<json body>'
```

Example prompt: Can you reconcile my x402 purchase? Here is the payment requirement metadata from the 402 response, the payment response metadata, the delivery receipt, and the settlement reference — I need a field-by-field verdict on whether each artifact is proven, conflicting, or missing so I can attach it to a refund request.

## When to prefer this

Choose this endpoint when you need a structured, deterministic audit of an x402 payment lifecycle using artifacts you already possess — particularly when preparing a refund request or dispute. It is not a live chain-state checker or provider contact tool; prefer it when you have the four key artifacts (payment requirement, payment response, delivery receipt, settlement reference) and need a trustless, offline field-level comparison without making external calls.

## Known failure modes

- Missing required artifact objects result in fields being marked as 'missing' rather than an error response
- Conflicting field values across artifacts return a 'conflicting' verdict rather than resolving the truth
- Chain state is not verified — verdicts reflect only the provided metadata, not on-chain reality
- Private keys or signatures included in input are rejected or ignored for security reasons
- Malformed or incomplete JSON objects for any artifact may result in partial verdicts or validation errors

## How this service works

Verify an x402 purchase actually settled and delivered what you paid for:
submit bounded, non-secret metadata for the payment requirement, payment
response, delivery receipt and settlement reference, and receive a single
deterministic verdict — proven, conflicting, or missing — field by field,
suitable to attach to a refund request or dispute.
Limitation: verdicts are computed from the artifacts you provide; we do not
fetch chain state or contact the provider on your behalf.

## Output

A deterministic, field-by-field reconciliation verdict for each artifact submitted (payment_requirement, payment_response, delivery_receipt, settlement_ref). Each field is labeled as proven, conflicting, or missing based solely on the metadata provided. The result is structured and suitable for attaching directly to a refund request or audit log.

## 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/x402-lifecycle-reconcile-550cdc6e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.delx.ai](https://www.zero.xyz/host/api.delx.ai/llms.txt)