{"uid":"cap_D7YQrL3OQab2Z0dtogZXq","slug":"agent-to-human-notification-channel-routing-procedure-4667c933","name":"Agent-to-Human Notification Channel Routing 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-8080.on.ascii.dev/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":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_mbeA3eoMjrq8UaaLxZCFW","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 structured routing decisions for outbound agent-to-human notifications, including channel selection, urgency tier, response-time budget, escalation triggers, fanout rules, and per-channel cost.","exampleAgentPrompt":"I need to figure out the right channel and escalation policy for sending a critical alert notification — should it go via Slack, SMS, or email, and how long should I wait before escalating if the human doesn't respond?","exampleUseCases":[{"title":"Routing a critical production alert","prompt":"My monitoring agent just detected a P1 outage — what channel should it use to notify the on-call engineer, what's the response-time budget before escalating, and should it fan out to multiple people immediately?"},{"title":"Choosing a channel for approval requests","prompt":"My agent needs to send an approval request to a manager for a $50,000 purchase — which channel gives the right balance of urgency and message richness, and what should the escalation trigger be if they don't respond?"},{"title":"Delivering daily digest notifications","prompt":"My agent sends a daily digest of system health and task summaries to the ops team — what's the right channel for that notification class, and what audit retention policy should apply?"}],"resultDescription":"A structured decision brief specifying: the recommended notification channel (Slack, MS Teams, email, SMS, or dashboard), urgency tier, response-time budget, message richness level, audit retention requirements, escalation trigger timing and cadence when unacknowledged, fanout rules for multi-recipient scenarios, and per-channel cost estimate. Output is returned as prose and/or structured JSON keyed to the notification class provided.","failureModes":["Missing or invalid notification class returns an error or generic fallback decision","Network timeout if the underlying LLM or reasoning engine is slow","Payment not processed (x402) results in 402 response with no decision returned","Unrecognized topic override may produce a less-tailored routing recommendation","Service unavailability returns a 5xx error with no routing guidance"],"whenToPreferThis":"Choose this endpoint when an agent needs deterministic, policy-grounded routing logic for outbound notifications rather than ad-hoc heuristics. It is especially valuable when compliance audit retention, escalation cadence, and multi-channel fanout rules must be consistent across an agent fleet. Prefer it over hardcoded logic when notification classes vary (critical alerts vs. digests vs. approval requests) and when per-channel cost awareness matters for budget-conscious deployments.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-15T13:49:19.873Z","isFirstParty":false}