# Post-Payment Fulfillment-Claim Verification Procedure

> Post-Payment Fulfillment-Claim Verification Procedure is a paid API for AI agents from k2so.wrong.systems, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Grades a merchant's fulfillment claim (order placed, processing, shipped) against verifiable artifacts after a card charge with no order placed, returning a claim grade, evidence tuple, and a hold/poll/escalate/refund decision with timing thresholds.

## Facts

- Endpoint: GET https://k2so.wrong.systems/api/services/post-payment-fulfillment-claim-verification-proc
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/post-payment-fulfillment-claim-verification-procedure-b6e989fd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xxx5fh609D52eskFtuLd-

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 post-payment-fulfillment-claim-verification-procedure-b6e989fd
```

Example prompt: My card was charged $89 for an order that never appeared in the system — the merchant claims the order is 'processing' but I have no confirmation email or order ID. Run the post-payment fulfillment-claim verification procedure and tell me whether to hold, keep polling, escalate, or demand a refund, and by when.

## When to prefer this

Use this endpoint when an agent or user has confirmed that a payment was successfully charged but no order was placed or fulfillment occurred, and needs a blunt, evidence-graded decision on next steps. Prefer this over generic dispute-resolution flows when you have a specific merchant claim (processing, shipped, placed) and need artifact-level grading rather than tone-based assessment. Especially useful for autonomous purchasing agents that need a deterministic hold/poll/escalate/refund gate before triggering a chargeback or support escalation.

## Known failure modes

- Missing or insufficient merchant fulfillment artifacts result in a low claim grade and immediate refund recommendation
- No verifiable evidence provided causes the procedure to default to an escalate decision
- Invalid topic override parameter may cause misaligned procedure framing
- LLM-generated reasoning may occasionally produce an ambiguous hold/poll recommendation without a clear threshold; agent should re-poll
- Payment not completed (402) blocks access to the full procedure output

## How this service works

Paid agent-facing procedure for the post-payment failure half: card charged, order never placed. Grades a merchant fulfillment claim (order placed, processing, shipped) by verifiable artifacts, not tone. Returns claim grade, evidence tuple, and a hold/poll/escalate/refund decision with timing thresholds. Blunt decision procedure, not marketing.

## Output

Returns a claim grade (quality assessment of the merchant's evidence), an evidence tuple capturing what artifacts were or were not present, and a concrete decision — hold, poll, escalate, or refund — with timing thresholds specifying by when each action should be triggered. Also includes a prose brief explaining the reasoning for the decision.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "meta": {
       "enum": [
        "0",
        "1"
       ],
       "type": "string",
       "description": "Set to 1 for free metadata JSON (no payment required)"
      },
      "topic": {
       "type": "string",
       "description": "Optional topic override for the decision procedure"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "title": "Post-payment fulfillment-claim verification procedure paid response",
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "required": [
      "ok",
      "paid",
      "service",
      "provider",
      "result"
     ],
     "properties": {
      "ok": {
       "type": "boolean"
      },
      "paid": {
       "type": "boolean"
      },
      "result": {
       "type": "object",
       "required": [
        "ok",
        "service"
       ],
       "properties": {
        "ok": {
         "type": "boolean",
         "description": "Handler success"
        },
        "brief": {
         "type": "string",
         "description": "Decision procedure prose for agents"
        },
        "model": {
         "type": "string"
        },
        "topic": {
         "type": "string"
        },
        "service": {
         "type": "string",
         "description": "Service slug"
        },
        "procedure": {
         "type": "string"
        },
        "generatedAt": {
         "type": "string",
         "description": "ISO-8601 timestamp"
        },
        "generationSource": {
         "enum": [
          "llm",
          "reasoning",
          "deterministic"
         ],
         "type": "string"
        }
       }
      },
      "payment": {
       "type": "object",
       "properties": {
        "code": {
         "type": "string"
        },
        "payer": {
         "type": "string"
        },
        "detail": {
         "type": "string"

… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "paid": true,
  "result": {
   "ok": true,
   "brief": "plain prose decision procedure (120+ words)",
   "model": "deepseek/deepseek-v4-flash-0731",
   "topic": "string topic",
   "service": "post-payment-fulfillment-claim-verification-proc",
   "procedure": "same as brief",
   "generatedAt": "2026-01-01T00:00:00.000Z",
   "generationSource": "deterministic"
  },
  "service": "post-payment-fulfillment-claim-verification-proc",
  "provider": "K-2SO"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/post-payment-fulfillment-claim-verification-procedure-b6e989fd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from k2so.wrong.systems](https://www.zero.xyz/host/k2so.wrong.systems/llms.txt)