{"uid":"cap_oALdr7nUTQ5ooe5mPJcv8","slug":"multi-channel-agent-entitlement-scope-mapping-procedure-91bfdf30","name":"Multi-Channel Agent Entitlement Scope Mapping Procedure","description":"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.","url":"https://k2so-8080.on.ascii.dev/api/services/multi-channel-agent-entitlement-scope-mapping-pr?utm_source=zero.xyz","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":"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"},"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_Sg8a0w-kY7z6pF2jnPf0O","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 decision procedure for defining and enforcing which Slack and MS Teams channels, workspaces, and DM scopes are permitted to invoke or approve agent actions.","exampleAgentPrompt":"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?","exampleUseCases":[{"title":"Slack channel allowlist for agent invocation","prompt":"I need a procedure for figuring out exactly which Slack channels and workspaces should be allowed to trigger my agent's actions — give me the entitlement scope mapping so I can build the allowlist correctly."},{"title":"MS Teams DM scope enforcement setup","prompt":"We're deploying an agent across multiple MS Teams workspaces and need to know which direct message scopes it's allowed to respond in — can you get me the scope mapping procedure so we can enforce proper boundaries?"},{"title":"Cross-channel agent audit evidence prep","prompt":"We have an upcoming compliance audit and need to document which channels and workspaces our agent is active in and what permissions it holds — can you run the multi-channel entitlement scope mapping procedure so we have the audit evidence bundle?"}],"resultDescription":"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.","failureModes":["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"],"whenToPreferThis":"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.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-21T22:57:37.153Z","isFirstParty":false,"canonicalSlug":"multi-channel-agent-entitlement-scope-mapping-procedure-91bfdf30"}