# Per-Rail Settlement Confirmation Wait-Time Thresholds for x402/MPP Agents

> Per-Rail Settlement Confirmation Wait-Time Thresholds for x402/MPP Agents is a paid API for AI agents from k2so.wrong.systems, paid per call via x402, $0.002/call, status down (last checked 2026-10-18).

Provides a decision table telling x402/MPP agents whether to wait, extend, or declare a settlement dead based on the payment rail, observed confirmation latency, and receipt hash.

## Facts

- Endpoint: GET https://k2so.wrong.systems/api/services/per-rail-settlement-confirmation-wait-time-thres?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: down
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/per-rail-settlement-confirmation-wait-time-thresholds-for-x402-mpp-0e3b82d4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JJO1ySmUofB7hJW-Fh6F3

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 per-rail-settlement-confirmation-wait-time-thresholds-for-x402-mpp-0e3b82d4
```

Example prompt: I paid an x402 challenge on Solana 45 seconds ago and still have no confirmation — tell me whether I should keep waiting, extend the timeout, or declare the payment dead, and flag any double-pay risk if I retry now.

## When to prefer this

Choose this endpoint when an x402 or MPP agent has already submitted a payment and needs a structured, per-rail decision on whether to wait longer, extend its timeout, or declare the settlement dead — especially when double-pay risk on retry is a concern. Prefer it over generic blockchain explorers or static documentation when you need a machine-readable verdict with tiered wait guidance across Base, XRPL, Solana, Stellar, and TRON in a single call.

## Known failure modes

- Missing or invalid rail parameter may result in a generic rather than rail-specific verdict
- Slow or unavailable upstream LLM could delay response or return a degraded generation
- If receipt hash is null the double-pay risk assessment may be less precise
- Payment not received or facilitator credit exhausted returns unpaid/error state
- Network timeout reaching k2so.wrong.systems returns no verdict

## How this service works

Decision table for agents that paid an x402/MPP challenge and now must decide when their settlement is actually dead versus merely slow. Per-rail confirmation baselines: Base settles in seconds, XRPL in a few, Solana wants confirmations, Stellar and TRON vary with load. Inputs: rail, observed confirmation latency, receipt hash or null. Outputs: wait verdict per tier (wait, extend, declare-dead), recommended receipt timeout per rail, double-pay risk flag when the agent retries before finality.

## Output

Returns a JSON object containing a plain-prose decision procedure (120+ words) advising wait, extend, or declare-dead per tier for the queried rail, a recommended receipt timeout value, a double-pay risk flag for premature retries, an ISO-8601 generatedAt timestamp, and metadata including model, topic, service slug, and generation source (llm, reasoning, or deterministic).

## 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": "Per-rail settlement confirmation wait-time thresholds for x402/MPP agents 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": {
      
… (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": "per-rail-settlement-confirmation-wait-time-thres",
   "procedure": "same as brief",
   "generatedAt": "2026-01-01T00:00:00.000Z",
   "generationSource": "deterministic"
  },
  "service": "per-rail-settlement-confirmation-wait-time-thres",
  "provider": "K-2SO"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/per-rail-settlement-confirmation-wait-time-thresholds-for-x402-mpp-0e3b82d4/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)
