AgentsReady
Verified deep dive · SaaS

Slack

Run the agent liveReport a change
6 minTime to key
NoNo-human path
2Human gates
7/10Onboarding score
Admin approvalEmail verification

Fastest path to a key

  1. Sign up at slack.com/get-started with email (6-digit confirmation code) or Google/Apple OAuth
  2. Create a workspace (name, first channel) - or join an existing one
  3. Go to api.slack.com/apps > Create New App > From manifest (agent can write the YAML/JSON manifest with scopes)
  4. Admin approval
    Install to Workspace (OAuth consent; on managed workspaces this becomes an admin approval request)
  5. Copy Bot User OAuth Token (xoxb-) or User Token (xoxp-) from OAuth & Permissions
  6. Call https://slack.com/api/auth.test with Bearer token
  7. Working API key

Biggest gap

No personal token and no DCR: every agent needs a registered Slack app (and often admin approval) before it can touch the API or MCP.

Worth copying

Language-split llms-full files (platform + JS/Python/Java/Deno) so agents load only the SDK they need.

Sources (6) · checked 2026-10-11
65Readiness score / 100
L3 Agent-operableBeats 85% of 1,846 companies
Access20/20
Context11/20
Interfaces20/32
Onboarding8/19
Trust6/9
llms.txt · root
MCP · https://mcp.slack.com/mcp

Biggest gains

  1. +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
  2. +6 Docs available as markdown. Serve every docs page as .md, or honour Accept: text/markdown.
  3. +6 Agents can self-register OAuth clients. Support dynamic client registration (RFC 7591) or client ID metadata documents so MCP clients connect in one click.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • PASSllms.txt exists8
  • FAILllms-full.txt exists3
  • FAILDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • FAILMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • FAILSDKs and a CLI4
  • PASSOAuth discovery metadata5
  • FAILAgents can self-register OAuth clients6
  • FAILSelf-serve API keys5
  • PASSFree tier or test mode3
  • PASSAgent manifests4
  • PASSsecurity.txt2
  • FAILPublic status page3

Your fix pack: 8 changes, up to +35 points

Each change is ready to paste, filled in for slack.com, with a command to check it worked. Or hand the whole list to your coding agent.

An OpenAPI spec is the contract agents and SDK generators build against. Without it they guess from prose.

Where: https://slack.com/openapi.json, linked from llms.txt and the API reference
// Serve the spec your API framework already generates (FastAPI: /openapi.json is built in).
// Next.js: app/openapi.json/route.ts
import spec from "@/openapi/openapi.json";
export const GET = () => Response.json(spec, { headers: { "Access-Control-Allow-Origin": "*" } });

// Every operation needs: operationId, summary, description, request/response examples,
// and the auth scheme (components.securitySchemes) so agents know how to send the key.
Check it worked:curl -s https://slack.com/openapi.json | head -c 200

Add the badge to your README

AgentsReady badge for slack.com
[![AgentsReady](https://agentsready.dev/badge/slack.com)](https://agentsready.dev/c/slack.com)