RXed AI News

AI news with a spine.
@RXed_EU
SCORE 7/10 10/10 criteria · Strong Assessed 2026-07-25 · ARI rubric v1.0

Slack — can an agent use it?

“The AI work platform” — the vendor’s own words

Slack shipped an official MCP server (GA 17/02/2026) and courts agent builders, but its May 2025 terms cut conversations.history to 1 request per minute for commercially distributed non-Marketplace apps and ban using Slack data to train an LLM.

Service
Category
Team communication platform
Agent protocol
Official
Agent payment rails
None published
Sf8.5
Machine-readable surface
Iq7
Information retrieval quality
Dx8.5
Documentation for machines
Ac8.5
Action coverage
Pt9
Agent protocol support
Au5.5
Access & auth friction
Py2
Agent payment capability
Cf4.5
Cost & rate fairness
Ts5.5
Permission & ToS stance
Rl6.5
Reliability & continuity
Tap or hover any criterion to see why it scored that.

Can an agent get correct information?

Machine-readable surface — 8.5/10

docs.slack.dev serves an open robots.txt that explicitly advertises LLM-friendly markdown ('append .md to any page URL'), and every API response is JSON with structured Block Kit payloads. source

Information retrieval quality — 7/10

Plan prices are public and exact (Free $0 with 90-day history and 10 apps, Pro $7.25/user/mo annual, Business+ $15) but Enterprise+ is 'contact sales' and the MCP server's plan eligibility is published nowhere in Slack's own docs or help centre. source

Documentation for machines — 8.5/10

Per-method reference with required scopes and rate-limit tier, a dated changelog tagged 'Breaking change'/'Deprecation' plus quarterly recaps, and first-party Bolt SDKs — offset by the official OpenAPI spec repo slackapi/slack-api-specs being archived since 27/03/2024. source

Can an agent do the job?

Action coverage — 8.5/10

The Web API covers messaging, channels, files, users, canvases and admin, and 2026 added chat.startStream/appendStream/stopStream plus blocks.validate — but there is no test mode mirroring production and Discovery API export is Enterprise+ only. source

Agent protocol support — 9/10

Official, actively extended MCP server at mcp.slack.com/mcp, GA 17/02/2026 with OAuth 2.1 + PKCE scoped user tokens and new tools shipped Apr–Jun 2026; loses points because it rejects Dynamic Client Registration, so Claude Code and Cursor's default flows fail. source

Access & auth friction — 5.5/10

App creation and tokens are self-serve in minutes with granular scopes, but MCP needs a per-app 'Model Context Protocol' toggle, a user token (xoxp-), workspace-admin approval of the MCP server domain, and any commercial distribution requires Slack Marketplace review with no published turnaround time. source

Agent payment capability — 2/10

Slack sells seat subscriptions but supports no agent payment protocol (no ACP, AP2, MPP or x402) and exposes no purchase or billing-mutation API — team.billing.info is read-only, so money moves only through human checkout or a sales contract. source

Cost & rate fairness — 4.5/10

Standard tiers are documented and generous (Tier 3 = 50+/min, Tier 4 = 100+/min) but non-Marketplace commercially distributed apps created after 29/05/2025 get conversations.history and conversations.replies at 1 request per minute and 15 objects per request — a targeted throttle on third-party data access, with internal apps exempted after the 03/06/2025 clarification. source

Will it still work next quarter?

Permission & ToS stance — 5.5/10

The API ToS effective 10/10/2025 states 'You may not use API Data to train a large language model' for externally offered apps, bans bulk export of messages and files outside the Discovery API, limits storage to what is 'essential for the immediate operation', and makes the Marketplace the only lawful commercial distribution channel — even though bots themselves are first-class citizens. source

Reliability & continuity — 6.5/10

There is a machine-readable status API (slack-status.com/api/v2.0.0/current returns status and active_incidents JSON) and deprecations get long runways (files.upload slipped from 11/03/2025 to 12/11/2025), but the API is not date-versioned, the 29/05/2025 rate-limit cut hit with almost no notice, and a global severe-latency outage on 27/05/2026 was reported by users before the status page updated. source

Sources

Point-in-time assessment — services change terms, prices and APIs often. That volatility is itself scored under Reliability & continuity. Re-verified at least quarterly.