{"uid":"cap_n1g6CAhIyQ1KKlrGknN6j","slug":"payment-verification-threshold-and-billing-model-selector-c96337a0","name":"Payment Verification Threshold and Billing Model Selector","description":"Decision procedure and JSON schema for x402 merchants choosing between pay-per-verified-call, subscription credits, or hybrid billing. Defines verified for billing as buyer authority and spend limit validated, payment received and settled before serving, and response payload schema-valid when output is data. Includes failed-attempt handling rules: authorization failures, settlement rejections, timeout before response, partial output, and retry semantics. Retries are billable only after a","url":"https://k2so-8080.on.ascii.dev/api/services/merchant-billing-model-selection-verified-call-c?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":"Payment verification threshold and billing selector 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":"unknown","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_JpQZQU8Ieg8EIPQlFmRVS","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 decision procedure and JSON schema for x402 merchants choosing among pay-per-verified-call, subscription credits, or hybrid billing models, including failed-attempt handling rules.","exampleAgentPrompt":"I'm setting up an x402 merchant endpoint and need to decide whether to use pay-per-verified-call, subscription credits, or a hybrid billing model — can you fetch the decision procedure and tell me which one fits a service where buyers need spend-limit validation and I want payment settled before serving the response?","exampleUseCases":[{"title":"Choosing billing model for data API","prompt":"I'm launching a paid data API on x402 and I'm not sure whether to charge per verified call or use subscription credits — can you get me the decision procedure so I can figure out which model makes sense for my use case?"},{"title":"Handling failed payment attempts policy","prompt":"My x402 merchant endpoint sometimes gets authorization failures and settlement timeouts — can you pull up the billing rules for how to handle those failed attempts and whether retries should be charged?"},{"title":"Verifying hybrid billing configuration","prompt":"I want to set up a hybrid billing model for my x402 service where some calls are pay-per-verified-call and others use subscription credits — can you fetch the verification threshold and billing selector procedure to confirm what counts as a verified call before I go live?"}],"resultDescription":"Returns a JSON object with a decision procedure prose brief for agents, the selected billing model slug, a topic label, an ISO-8601 timestamp of generation, and the generation source (llm, reasoning, or deterministic), along with payment confirmation fields (ok, paid, provider, service).","failureModes":["Authorization failure returns an error result with ok:false and no billing model selected","Settlement rejection causes the procedure to return a failed-attempt rule set rather than a billing recommendation","Timeout before response may result in incomplete output with partial procedure data","Invalid or unsupported topic override causes the procedure to fall back to default decision logic","Payment not received causes the endpoint to reject without serving the decision procedure"],"whenToPreferThis":"Use this endpoint when you are an x402 merchant or developer building a paid API and need authoritative, schema-validated guidance on which billing model (pay-per-verified-call, subscription credits, or hybrid) best fits your payment and settlement requirements. Prefer this over generic documentation when you need machine-readable decision logic including failed-attempt handling and retry semantics integrated into an agent workflow.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-16T18:42:28.970Z","isFirstParty":false,"canonicalSlug":"payment-verification-threshold-and-billing-model-selector-c96337a0"}