# Payment Delivery Atomicity Detector

> Payment Delivery Atomicity Detector is a paid API for AI agents from phion.systems, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-15).

Detects inconsistent payment-delivery states, specifically paid-without-delivery and delivered-without-payment conditions, to surface atomicity violations in agentic payment flows

## Facts

- Endpoint: POST https://phion.systems/v1/paid/trust/payment-delivery-atomicity?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/payment-delivery-atomicity-detector-b286e2f9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FhB3PvXbA9j63US9r8WOz

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 payment-delivery-atomicity-detector-b286e2f9 -d '<json body>'
```

Example prompt: Can you check this transaction for payment-delivery atomicity issues — I need to know if we have any cases where payment went through but delivery never happened, or delivery was made without a confirmed payment?

## When to prefer this

Use this endpoint when you need to programmatically detect split or inconsistent states in two-sided exchanges — specifically the classic atomicity failure modes where payment and delivery do not both complete. Prefer this over generic reconciliation tools when working with x402 agentic payment flows, micro-transaction pipelines, or any system where payment and fulfillment happen in separate steps that could desynchronize.

## Known failure modes

- Insufficient input data — if payment or delivery records are missing or incomplete, the detector may return an indeterminate result
- Schema mismatch — the endpoint accepts a generic object schema, so malformed or unexpected fields may cause silent misclassification
- False negatives — if delivery confirmation signals are delayed or asynchronous, the detector may miss a true atomicity violation
- Network or provider error — 5xx responses may occur if the phion.systems backend is unavailable

## How this service works

Detect paid-without-delivery and delivered-without-payment states

## Output

Returns a structured assessment indicating whether the supplied transaction or order context exhibits paid-without-delivery violations, delivered-without-payment violations, or is in a consistent atomic state, along with confidence or evidence signals about the detected inconsistency.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input",
  "output"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "additionalProperties": true
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "example"
   ],
   "properties": {
    "example": {
     "type": "object",
     "additionalProperties": true
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/payment-delivery-atomicity-detector-b286e2f9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from phion.systems](https://www.zero.xyz/host/phion.systems/llms.txt)