{"uid":"cap_aY5dVXVj1J3pcvBy4xS36","slug":"k-2so-reservation-hold-settlement-lifecycle-procedure-d7615455","name":"K-2SO Reservation Hold Settlement Lifecycle Procedure","description":"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.","url":"https://k2so.wrong.systems/api/services/reservation-hold-settlement-lifecycle-procedure?utm_source=zero.xyz","method":"GET","headers":{},"bodySchema":{"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"},"selfPay":{"type":"boolean"},"transaction":{"type":"string"}}},"service":{"type":"string"},"provider":{"type":"string","const":"K-2SO"}}}}}}},"responseSchema":{"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":"reservation-hold-settlement-lifecycle-procedure","procedure":"same as brief","generatedAt":"2026-01-01T00:00:00.000Z","generationSource":"deterministic"},"service":"reservation-hold-settlement-lifecycle-procedure","provider":"K-2SO"}},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.002","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"down","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.002/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_D9QudfUGGZUW9X2mQA6ha","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.002","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Returns an AI-generated decision procedure (prose brief) describing how an autonomous agent should handle the full lifecycle of reservation hold settlement — from hold creation through settlement or expiry.","exampleAgentPrompt":"What's the full decision procedure I should follow as an autonomous agent for managing a reservation hold settlement lifecycle — from when the hold is created all the way through settlement or expiry?","exampleUseCases":[{"title":"Hotel booking agent hold management","prompt":"I'm building an agent that books hotels and needs to know exactly how to handle payment holds — when to settle, when to release, and what to do if a hold expires before check-in. Give me the decision procedure for that lifecycle."},{"title":"Agent-to-agent reservation marketplace","prompt":"My autonomous merchant agent needs a clear procedure for managing reservation holds with downstream agents — how do I handle the full hold-to-settlement flow correctly, including edge cases like partial fulfillment or cancellation?"},{"title":"Compliance review of hold settlement logic","prompt":"Can you give me the decision procedure for reservation hold settlement so I can audit whether my current agent implementation matches the recommended autonomous agent best practices?"}],"resultDescription":"A JSON response containing a plain-prose decision procedure (120+ words) tailored to the reservation hold settlement lifecycle topic, the model used to generate it, an ISO-8601 generation timestamp, a generation source indicator (llm/reasoning/deterministic), and the service slug. Payment metadata including payer address and transaction hash is also returned.","failureModes":["HTTP 402 returned if USDC payment not yet settled — agent must pay exact amount and retry with PAYMENT-SIGNATURE header","Invalid or missing method enum causes request rejection","Meta flag '1' returns free metadata JSON without triggering payment or returning the procedure","Underlying LLM unavailability may delay or alter generation source to deterministic fallback","Topic override ignored or misinterpreted if not well-formed string"],"whenToPreferThis":"Choose this endpoint when an autonomous agent needs structured, plain-language guidance on the reservation hold settlement lifecycle specifically — not generic payment flows. Prefer over static documentation when the agent needs freshly generated, model-backed prose it can act on or pass downstream. Useful for agents in hospitality, ticketing, or any booking domain that must handle pre-authorization holds.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-18T12:25:54.112Z","isFirstParty":false,"canonicalSlug":"k-2so-reservation-hold-settlement-lifecycle-procedure-d7615455"}