# K-2SO Agent-to-Human Notification Channel Routing Decision Procedure

> K-2SO Agent-to-Human Notification Channel Routing Decision Procedure is a paid API for AI agents from k2so.wrong.systems, paid per call via x402, $0.002/call, status down (last checked 2026-09-15).

Returns a paid LLM-generated decision procedure (prose brief) explaining how an AI agent should route notifications to humans across available channels

## Facts

- Endpoint: GET https://k2so.wrong.systems/api/services/agent-to-human-notification-channel-routing-deci
- Price: $0.002/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/k-2so-agent-to-human-notification-channel-routing-decision-procedure-e5bf3134
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bDvkdq-2Twr7oW6imZWDm

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 k-2so-agent-to-human-notification-channel-routing-decision-procedure-e5bf3134
```

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

## When to prefer this

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.

## Known failure modes

- 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

## 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 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.

## 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)
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/k-2so-agent-to-human-notification-channel-routing-decision-procedure-e5bf3134/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from k2so.wrong.systems](https://www.zero.xyz/host/k2so.wrong.systems/llms.txt)