{"uid":"cap_l2PZFVPFnR1Pl25Rxbpf3","slug":"telco-rail-settlement-dispute-playbook-e73e85d1","name":"Telco-Rail Settlement Dispute Playbook","description":"Deterministic dispute procedure for agents paying over telco or carrier billing rails (SMS billing, carrier billing, phone-bill settlement) where no on-chain receipt exists. Covers charge confirmation capture (carrier reference, merchant id, amount, timestamp), duplicate-charge and overcharge detection, merchant-then-carrier dispute filing inside the chargeback window, evidence tuple retention, and the refund-vs-double-pay gate: never re-pay disputed work until a refund receipt or a fresh","url":"https://k2so.wrong.systems/api/services/agent-payment-dispute-handling-on-telco-carrier?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":"Telco-rail settlement dispute playbook 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":null,"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_zZkTxL_wT64r6fK4EJaum","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 a deterministic step-by-step dispute procedure for agents handling billing disputes on telco/carrier rails (SMS billing, carrier billing, phone-bill settlement) where no on-chain receipt exists.","exampleAgentPrompt":"I was billed twice for the same service through carrier billing and there's no on-chain receipt — walk me through the step-by-step dispute procedure, including how to capture the carrier reference, detect the duplicate, file with the merchant first then the carrier, and make sure I don't re-pay until I have a refund receipt.","exampleUseCases":[{"title":"Duplicate carrier charge dispute","prompt":"My agent got charged twice for the same SMS billing transaction and there's no blockchain receipt to verify it — give me the full dispute playbook: how to confirm the charges, detect the duplicate, and escalate to the carrier within the chargeback window."},{"title":"Telco overcharge refund gate","prompt":"An autonomous agent I operate was overcharged via phone-bill billing and I need to know whether to re-pay or wait — walk me through the refund-vs-double-pay gate and what evidence to retain until a refund receipt arrives."},{"title":"Carrier billing evidence retention","prompt":"I'm setting up my agent to handle SMS billing disputes and need to know exactly what evidence tuple to capture and how long to keep it before filing a merchant-then-carrier dispute for a phone-bill charge."}],"resultDescription":"A structured decision procedure document (prose and/or structured steps) covering: charge confirmation capture (carrier reference, merchant ID, amount, timestamp), duplicate-charge and overcharge detection logic, merchant-first then carrier-second dispute filing sequence within the chargeback window, evidence tuple retention guidance, and a refund-vs-double-pay gate ensuring the agent never re-pays disputed work until a refund receipt or fresh authorization is confirmed. Response includes service slug, generation source, and ISO-8601 timestamp.","failureModes":["Payment required but not provided — endpoint returns 402 before delivering the playbook","Invalid or missing method parameter causes schema validation failure","Topic override provided but unrecognized — procedure may default to generic telco dispute flow","Service temporarily unavailable on k2so.wrong.systems — no procedure returned","LLM or reasoning engine error — generationSource may indicate fallback or partial result"],"whenToPreferThis":"Choose this endpoint when an autonomous agent has made a payment over telco or carrier billing rails (SMS billing, phone-bill settlement) and needs a deterministic, step-by-step dispute procedure — especially when no on-chain receipt exists to verify the charge. Prefer this over generic payment dispute endpoints when the rail is specifically carrier/telco-based and the agent needs guidance on chargeback windows, merchant-vs-carrier escalation order, evidence retention, and the refund gate before re-attempting payment.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-18T01:26:01.393Z","isFirstParty":false,"canonicalSlug":"telco-rail-settlement-dispute-playbook-e73e85d1"}