# Agent-to-Human Notification Channel Routing Procedure

> Agent-to-Human Notification Channel Routing Procedure is a paid API for AI agents from k2so-8080.on.ascii.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

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.

## Facts

- Endpoint: GET https://k2so-8080.on.ascii.dev/api/services/agent-to-human-notification-channel-routing-deci
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-to-human-notification-channel-routing-procedure-4667c933
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_D7YQrL3OQab2Z0dtogZXq

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agent-to-human-notification-channel-routing-procedure-4667c933
```

Example prompt: 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?

## When to prefer this

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.

## Known failure modes

- 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

## How this service works

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

## Output

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.

## Request schema (JSON Schema)

```json
{
 "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"

… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-to-human-notification-channel-routing-procedure-4667c933/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from k2so-8080.on.ascii.dev](https://www.zero.xyz/host/k2so-8080.on.ascii.dev/llms.txt)