Slack
Add AxioRank to Slack with one click. Route high-risk AI-agent alerts to a channel, approve or deny held tool calls right in Slack, and run /axiorank for what needs attention.
The AxioRank Slack app brings AI-agent governance into Slack: high-risk
alerts, an App Home dashboard, approvals you can resolve in place, and
an /axiorank command. Approve and deny in Slack run through the same dual-control
path as the dashboard and signed email links, so a two-person hold needs two
distinct Slack users when your policy requires it.
Scopes and what is stored
Installing requests three least-privilege scopes: incoming-webhook (a webhook
bound to the one channel you pick), commands (the /axiorank command), and
chat:write (publish the App Home tab and modals). Alerts and approvals ride
the incoming-webhook URL; the App Home tab uses an encrypted bot token. The bot
token is stored only when the deployment has an encryption key
(AXR_DISCOVERY_CRED_KEY, or AXR_PROXY_CRED_KEY). Without it, alerts,
approvals, and the command still work and the Home tab simply stays empty.
Add to Slack
- In the AxioRank dashboard, open Channels.
- Click Add to Slack and choose the channel for alerts and approvals.
- You are returned to Channels with the new Slack channel created. High alerts route there now. Use the row menu to add escalations or daily and weekly digests, or to change the severity floor.
The Add to Slack button appears when the deployment has the AxioRank Slack
app configured (SLACK_CLIENT_ID and SLACK_CLIENT_SECRET). If it is not
configured, paste an incoming-webhook URL by hand on the same screen instead.
Approve and deny in Slack
When a policy holds a risky action, an Approve / Deny message lands in the
channel. A click is verified with the app signing secret on
/api/slack/interactivity and resolved through AxioRank's approval engine. Two
distinct Slack users are needed to clear a hold that requires two approvals.
Interactive buttons need a signing secret
Approve and deny buttons require SLACK_SIGNING_SECRET on the deployment.
Without it, AxioRank still posts the alert and the approval, but the buttons
fall back to a dashboard link.
The App Home tab
Open AxioRank in your Slack sidebar for a live dashboard: pending approvals with inline Approve and Deny, the last 24 hours of allow, deny, and hold decisions, and the agents holding the most. Resolving a hold from the Home tab refreshes it in place. The Home tab needs the encryption key noted above so the bot token can be stored.
The /axiorank command
Run /axiorank in any channel to get a private summary: the approvals waiting on
you and the trailing 24 hours of decisions. Drill in with a subcommand:
/axiorank approvals- the full pending approval list/axiorank agents- the agents holding the most approvals/axiorank status- governed volume and decisions/axiorank spend- month-to-date AI spend/axiorank help- the command list
Only you see the reply. There is also a global AxioRank approvals shortcut
(the lightning bolt or + in the message composer) that opens the approvals list
from anywhere.
Self-hosting and manual setup
If you run your own AxioRank deployment, register the Slack app from the manifest
in packages/slack-app and set SLACK_CLIENT_ID, SLACK_CLIENT_SECRET, and
SLACK_SIGNING_SECRET. For the App Home tab, also set an encryption key
(AXR_DISCOVERY_CRED_KEY, or reuse AXR_PROXY_CRED_KEY) so the bot token can be
stored at rest. The full submission and configuration steps are in that package's
SUBMISSION.md. You can also skip the OAuth app entirely and paste an
incoming-webhook URL into Channels; alerts and approvals still work, and the
buttons work as long as the signing secret is set.
Strands Agents
Govern a Strands (AWS) agent's tools with AxioRank. Wrap each @tool so every call is scored before it runs, with no rewrite.
WordPress
Verify the AI agents that reach your WordPress REST API, admin, and dynamic endpoints with the AxioRank Agent Verification plugin. A thin client of the inbound verify endpoint, with monitor and enforce modes.