# Reservation Hold Settlement Lifecycle Procedure

> Reservation Hold Settlement Lifecycle Procedure is a paid API for AI agents from k2so-8080.on.ascii.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-16).

Returns an agent decision procedure for managing x402 reservation flows including hold placement, hold amount calculation, expiry management, hold-to-payment conversion, and double-hold idempotency.

## Facts

- Endpoint: GET https://k2so-8080.on.ascii.dev/api/services/reservation-hold-settlement-lifecycle-procedure?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reservation-hold-settlement-lifecycle-procedure-081c494d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kInKLtgS2O2sHY8uwEZhp

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 reservation-hold-settlement-lifecycle-procedure-081c494d
```

Example prompt: Walk me through the full decision procedure for handling a reservation hold in x402 — I need to know how to set the hold amount relative to the expected final charge, when to release or convert it, and how to avoid creating duplicate holds if availability and payment happen in the same conversation.

## When to prefer this

Choose this endpoint when an AI agent needs explicit, paid procedural guidance on managing x402 reservation hold flows end-to-end — particularly when the agent must decide between holding vs. paying directly, calculate appropriate hold amounts, handle expiry, convert holds to final settlements, or enforce idempotency across a multi-step availability-and-payment conversation. It is more specific than general x402 payment guidance endpoints and focuses exclusively on the reservation hold lifecycle.

## Known failure modes

- Payment required but no x402 payment header provided — returns 402 with payment instructions
- Invalid query parameter values (e.g. meta not '0' or '1') — schema validation error
- Upstream LLM generation failure — may return ok:false with error detail
- Topic override not recognized — procedure may default to standard reservation hold topic
- Service temporarily unavailable — network or provider outage

## How this service works

Agent-side decision procedure for x402 reservation flows: place a hold or pay directly, calculate hold amount relative to expected final settlement, manage expiry and release, convert hold to final payment, and enforce double-hold idempotency when the AI handles availability checks, holds, and payment in one conversation.

## Output

A structured response containing prose decision procedure guidance (the 'brief' field) for agents managing x402 reservation hold lifecycles, including hold placement logic, amount calculation relative to expected settlement, expiry and release handling, hold-to-payment conversion steps, and double-hold idempotency enforcement. Also includes metadata such as topic, model used, generation source, and ISO-8601 timestamp.

## 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": "Reservation hold settlement lifecycle 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)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/reservation-hold-settlement-lifecycle-procedure-081c494d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from k2so-8080.on.ascii.dev](https://www.zero.xyz/host/k2so-8080.on.ascii.dev/llms.txt)