# Multi-Channel Agent Entitlement Scope Mapping Procedure

> Multi-Channel Agent Entitlement Scope Mapping 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-10-21).

Returns a decision procedure for defining and enforcing which Slack and MS Teams channels, workspaces, and DM scopes are permitted to invoke or approve agent actions.

## Facts

- Endpoint: GET https://k2so-8080.on.ascii.dev/api/services/multi-channel-agent-entitlement-scope-mapping-pr?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/multi-channel-agent-entitlement-scope-mapping-procedure-91bfdf30
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oALdr7nUTQ5ooe5mPJcv8

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 multi-channel-agent-entitlement-scope-mapping-procedure-91bfdf30
```

Example prompt: Can you pull up the entitlement scope mapping procedure for deciding which Slack and MS Teams channels and workspaces are allowed to invoke or approve agent actions, so I can set up proper allowlists and have audit evidence ready?

## When to prefer this

Choose this endpoint when you need an authoritative, agent-readable decision procedure specifically for managing Slack and MS Teams channel/workspace entitlements for agent invocations. It is distinct from general IAM or RBAC services because it focuses on the intersection of messaging platform scopes and agent action approval flows, with built-in guidance for audit evidence. Prefer it over generic policy documents when you need a machine-consumable procedure with per-topic customization.

## Known failure modes

- Invalid or missing 'method' field in input returns a 400-level error
- Unpaid request without x402 payment header returns 402 Payment Required
- Topic override not recognized may result in a generic fallback procedure
- Service temporarily unavailable returns a non-ok response with error detail
- Malformed query parameters cause input validation rejection

## How this service works

Procedure for defining and enforcing which Slack and MS Teams channels, workspaces, and direct message scopes may invoke or approve an agent action. Covers entitlement discovery, allowlist derivation, inherited permission boundaries, and audit evidence for cross-channel agent presence.

## Output

A structured decision-procedure brief (prose + metadata) generated by the K-2SO service covering: entitlement discovery steps, allowlist derivation logic, inherited permission boundary handling, and audit evidence requirements for cross-channel (Slack + MS Teams) agent presence. Includes the service slug, ISO-8601 timestamp, generation source, and optionally a topic-specific override.

## 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": "Multi-channel agent entitlement scope mapping 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/multi-channel-agent-entitlement-scope-mapping-procedure-91bfdf30/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)