{"uid":"cap_bDvkdq-2Twr7oW6imZWDm","slug":"k-2so-agent-to-human-notification-channel-routing-decision-procedure-e5bf3134","name":"K-2SO Agent-to-Human Notification Channel Routing Decision Procedure","description":"Decision procedure for outbound agent-to-human notifications. Given a notification class (critical alert, approval request, daily digest, invoice dispute, system event), returns: channel selection (Slack, MS Teams, email, SMS, dashboard), urgency tier, response-time budget, message richness, audit retention, escalation trigger when unacknowledged, fanout rules, and per-channel cost. Thresholds are concrete, not vibes: severity maps to channel, latency budget maps to escalation cadence, audit","url":"https://k2so.wrong.systems/api/services/agent-to-human-notification-channel-routing-deci","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":"Agent-to-Human Notification Channel Routing 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":"agent-to-human-notification-channel-routing-deci","procedure":"same as brief","generatedAt":"2026-01-01T00:00:00.000Z","generationSource":"deterministic"},"service":"agent-to-human-notification-channel-routing-deci","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_gPusym5Nrwr7im56rnOyV","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 paid LLM-generated decision procedure (prose brief) explaining how an AI agent should route notifications to humans across available channels","exampleAgentPrompt":"Give me a decision procedure for how an AI agent should choose which channel — email, SMS, push, Slack, etc. — to use when it needs to notify a human, factoring in urgency and availability.","exampleUseCases":[{"title":"Autonomous agent alert escalation logic","prompt":"My autonomous agent needs to know when to escalate a notification to SMS versus just sending an email — can you get me a decision procedure for how to route those alerts to a human based on urgency?"},{"title":"Multi-channel notification policy for agent fleet","prompt":"I'm building a fleet of AI agents and need a documented decision procedure they can follow for choosing the right notification channel when they need a human to review something — walk me through the routing logic."},{"title":"On-call incident routing for AI-powered ops","prompt":"When my ops agent detects an incident at 2am, how should it decide whether to page someone on PagerDuty, send a Slack message, or fire an SMS? Get me a concrete decision procedure for that routing choice."}],"resultDescription":"A JSON object containing a plain-prose decision procedure (120+ words) explaining how an agent should route notifications to humans, including the model used to generate it, the topic, service slug, ISO-8601 generation timestamp, and generation source (llm, reasoning, or deterministic). Payment metadata and provider identity (K-2SO) are also included.","failureModes":["HTTP 402 returned if payment not settled — must pay exact USDC amount and retry with PAYMENT-SIGNATURE header","Invalid or missing method enum (must be GET, HEAD, or DELETE) causes schema validation failure","Network or provider downtime on Base chain may delay payment settlement","LLM generation failure may result in empty or malformed 'brief' field","Passing unsupported query parameters beyond 'meta' and 'topic' may be silently ignored or rejected"],"whenToPreferThis":"Choose this endpoint when an AI agent needs a procedural, plain-language brief on how to route notifications to humans — especially in agentic pipelines where the agent must decide autonomously which channel (email, SMS, push, Slack, webhook) to use. Prefer it over static documentation when you need a freshly generated, model-reasoned procedure that reflects current best practices. It's well-suited for agents building or auditing their own notification logic at runtime via a micropayment-gated x402 call on Base.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-15T15:27:36.870Z","isFirstParty":false}