Slack agents

A Slack agent connects your own Slack app to RouterPlus. People mention the app in a channel or send it a direct message. RouterPlus answers in the same thread, with the model you select.

Each agent has its own RouterPlus inference key. Every answer is an ordinary request on that key. Your guardrails, budgets, routing and billing apply.

Set up an agent

1. 01
   Create a Slack app at api.slack.com/apps:

   • Select "From scratch" and install the app in your workspace.
   • Copy the bot token (xoxb-...) from "OAuth & Permissions".
   • Copy the signing secret from "Basic Information".
2. 02
   Create the agent with a management key (Authorization: Bearer tm_mk_...):

POST /v1/slack/agents

{
  "slug": "helpdesk",
  "bot_token": "xoxb-...",
  "signing_secret": "8f74...",
  "model": "gpt-6-luna",
  "system_prompt": "You answer questions about our product.",
  "allowed_channel_ids": ["C0123ABCD"],
  "allowed_user_ids": [],
  "tools": { "server": [{ "type": "web_fetch" }], "mcp_servers": ["docs"] },
  "max_cost_usd_per_day": 10
}

3. 03
   Get the app manifest:

GET /v1/slack/agents/{id}/manifest

4. 04
   In your Slack app, open "App Manifest", paste the manifest and save. Slack checks the events URL. When Slack asks, install the app again to give it the new scopes.
5. 05
   Invite the app to a channel (/invite @helpdesk). Mention it, or send it a direct message.

POST returns 201 with the agent. Slack sends events to the agent's events_url: https://<gateway>/v1/slack/events/{id}.

Fields

Manage agents

• Every route also works under /api/v1.
• Each change writes a row to the audit log (GET /v1/audit).
• Responses show has_bot_token and has_signing_secret, never the values.
• The agent's key is a normal inference key with the name slack:<slug>. It shows in GET /v1/keys and in activity. To stop all spend immediately, disable the key or the agent.

Scopes and events

The manifest asks for these bot scopes:

It subscribes to two bot events: app_mention and message.im.

How the agent answers

• A mention in a channel gets an answer in the thread of that message.
• A direct message gets an answer in the direct message. Direct messages outside a thread are one conversation.
• The agent does not answer bots (itself included), edits, deletions, or people who are not on the allow lists.
• RouterPlus removes the app mention from the text before the model sees it.
• The model sees the system prompt, the thread's earlier messages (up to 30), and the new message.
• When the agent's key has reached max_cost_usd_per_day today, the agent posts a short notice and does not call the model.
• When the model call fails, the agent posts a short message, for example "Sorry, I could not answer that. Try again later."

Security

• RouterPlus checks Slack's signature on every request. The signature is an HMAC-SHA256 of the timestamp and the body, with your signing secret. A request without a valid signature gets 401.
• A request with a timestamp more than 5 minutes from now gets 401. Thus nobody can send a captured request again.
• Slack sends an event again when it gets no acknowledgement in time. RouterPlus answers each event id one time.
• RouterPlus acknowledges each event immediately and answers in the background.

What is stored

RouterPlus keeps the model requests like any other request on your key. See Data policy.