Skip to main content
Your whole model catalog, right where your team already talks. Mention @aireserve in a channel and it answers in a thread — the gateway picks the best model for the request (or you name one), usage is metered to your organization’s wallet, and each reply footnotes which model served it. No API keys in Slack, no per-seat AI subscriptions.

​
What you get

  • Every model, one mention. The same 80+ model catalog as the API. No model named? The gateway’s auto-router picks the right one for the request. Name one — an exact id like claude-opus-5 or plain prose like “use deepseek” — and that model serves it.
  • Answers in threads, with receipts. Replies land in a thread on your message, and every reply ends with served by <model> so there’s never a question of what ran.
  • Billed like everything else. Mentions meter to your organization’s wallet at normal model rates and appear in your usage analytics, attributed to the Slack user who asked. If your wallet runs dry the bot says so politely instead of failing silently.
  • Org guardrails apply. Model allowlists, rate limits, and spend controls configured for your org apply to Slack exactly as they do to API keys.

​
Two ways to connect

Install in your workspace

An org admin installs the AI Reserve app into your Slack workspace from the portal. Once linked, invite @aireserve to any channel — public or private — and everyone in it can use it.

Shared channel with us

Already have a Slack Connect channel with the AI Reserve team? Mention @aireserve right there — we link the channel to your org during onboarding, nothing to install.

​
Installing in your own workspace

  1. An AI Reserve org admin starts the install from the portal — the install link is minted for your organization, so the workspace binds to your org and nobody else’s.
  2. Approve the app in Slack (a Slack workspace admin may need to allow it).
  3. Invite the bot to the channels where you want it: /invite @aireserve.
  4. Mention it. That’s the whole setup — keys, billing, and model access ride the link to your org.
The app only answers in workspaces linked to an AI Reserve organization. If it’s installed but not linked, it replies with a short note instead of serving — so an install can never bill the wrong org. Uninstalling the app severs the link and revokes its workspace credentials immediately.

​
Picking a model

The footer on every reply (served by …) always names the model that actually ran, whichever path chose it.

​
Billing and privacy

Slack usage is ordinary gateway usage: metered to your org’s wallet at the model’s normal rates, visible in usage analytics, and attributed to the individual Slack user who mentioned the bot. Message content passes through the gateway to the serving model exactly like an API call — see Data & privacy for the full data-handling posture. Wallet empty or billing disabled? The bot replies with a friendly note and a pointer to top up — mentions never fail silently.