# Slack — API Agent Score

> Score: 69/100 (Grade: C) | Domain: slack.com | Rubric: 1.0.0 | Checked: July 24, 2026

Slack scored 69/100 (C), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/slack)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 69/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 88/100 (A)
- Developer Experience: 76/100 (B)
- Agent Discovery: 83/100 (A)
- Agent Understanding: 58/100 (D)
- Agent Usability: 51/100 (D)

## Check Results

### API Design

- [pass] Schema coverage & depth — 6/6 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%, spec 83%.
- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: docs 100%, spec 50%, wellknown 50%.
- [warn] Machine-readable, versioned contract — info.version="1.7.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [pass] Example coverage — Code samples in 4 language(s) across docs (top: typescript, shell, python); 2/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%, sdk 100%, spec 0%.
- [warn] Security & governance hygiene — security.txt present but missing or expired Expires. Investigated: wellknown 50%, spec 0%.

### Developer Experience

- [pass] Quickstart present — Quickstart at https://docs.slack.dev/quickstart/ with a runnable first-call sample. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples in 4 language(s) across docs (top: typescript, shell, python); 2/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%.
- [pass] Description completeness — 74% description completeness (target 90%+). Investigated: spec 100%, sdk 86%.
- [pass] Changelog published — changelog documented in the docs site at https://docs.slack.dev/changelog/. Investigated: spec 100%, docs 100%, sdk 100%.
- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.

### Agent Discovery

- [warn] llms.txt present, valid & comprehensive — llms.txt directive found in HTML of 50 of 50 sampled pages, but buried deep in the page (past 50%). Investigated: docs 94%, sdk 0%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/slack_dev, 38747 snippets). Investigated: docs 100%, sdk 100%, cli 100%, mcp 0%, wellknown 0%.
- [warn] Docs reachable, not hard auth-gated — 50 of 50 sampled pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] Crawlable / AEO — Sitemap present (2928 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — No explicit 4xx/5xx codes, but 174 operation(s) document a "default" error response. Investigated: spec 100%, docs 100%, sdk 0%.
- [warn] Agent-navigable, token-efficient docs — 8 of 49 pages have substantive content differences between markdown and HTML (avg 8% missing). Investigated: docs 72%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, sdk) is 4% (threshold 35% for full credit).
- [fail] Operation purpose clarity — 0% of operations are agent-inferable. Investigated: spec 0%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 20 sampled pages — likely a CSR-only docs site. Investigated: docs 0%.

### Agent Usability

- [pass] Pagination documented & consistent — Pagination params detected on 2 list endpoint(s). Investigated: spec 100%, docs 100%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%, spec 0%, docs 0%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Slack's API program scores well on discoverability and contract design, giving partners a solid foundation to find and evaluate the API surface. However, the program's most critical gaps are in agent understanding and agent usability: operations lack the semantic clarity and structured context that AI agents need to build correct integrations without human intervention, and there is no runnable, test-backed collection to serve as an executable source of truth. Closing these gaps — starting with operation-level documentation and a machine-readable agent context file, then adding a runnable collection with test scripts and reliability signals like idempotency and rate-limit headers — will unlock the partner-program outcomes that matter most: faster integrations, fewer support escalations, and agents that can act on your APIs confidently.