AI Readiness Audit
Ref. APM-2A110E46 · Confidential

Discord HTTP API (stable)

An independent assessment of whether the Discord HTTP API (stable) specification is ready for AI-assisted integration and autonomous agents, prepared for Discord.

Prepared for
Discord
Subject
Discord HTTP API (stable) v10
Scope
246 operations · 4 pillars · 3 groups
Date
October 2026
46/100
Not ready
Gaps for AI-assisted builds.
Not ready for autonomous agents.
Reach AI-ready by Phase 2; resolve all findings → 100 · AI-ready
Import blocked: SDK, docs, and MCP generators will refuse this spec

The validation engine found 1 blocking violation: No item found in the enumeration list.. Import tools reject the specification outright until it is fixed, so nothing downstream can be generated regardless of the other pillar scores. While this gate is open, the Standards Compliance score is capped at 40 and every AI pillar weights standards at 60% (normally 30%). Fixing the blocker in Phase 1 lifts the caps; the score projection below shows what that unlocks.

2
Critical blockers stopping entire operation groups for agents
12963
Total instances: 2 critical, 675 high, 6365 medium, 5921 low
46
Rule groups across 4 pillars: 2 critical, 675 high sev. instances
Executive summary

Your specification currently fails import: blocking violations make SDK, docs, and MCP generators refuse it, and the scores below are capped until they are fixed. Discord HTTP API (stable) scores 46.3/100: Not ready · Grade F. The weakest pillar is Standards compliance at 40; the strongest is SDK readiness for AI at 60. We recorded 12963 finding instances: 2 critical, 675 high, 6365 medium, and 5921 low. Gaps for AI-assisted builds. Not ready for autonomous agents. Every finding lives in the specification, and the roadmap in this report orders the fixes by impact; resolving them projects the score to 100/100.

Readiness by pillar
Not ready 46 / 100
FoundationThe spec itself
40/100
Standards Compliancecapped · import blocked
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
40Not ready
Build Time ReadinessAI writes the code
51/100
Documentation Readiness for AI
Descriptions that say when to use an operation, examples that pin down every shape: whether an AI can learn the truth of your API from what you publish
42Not ready
SDK Readiness for AI
Clean types, predictable naming, correct formats: whether production-grade client code can be generated from your spec, by SDK pipelines and AI coding assistants alike
60Significant gaps
Runtime ReadinessAgents make the calls
47/100
MCP Readiness
Whether your operations survive being turned into tools: distinct names, descriptions that carry what an agent must know, safe invocation semantics, auth, error recovery, and context budget
47Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
46
Not ready
Phase 1fix criticals
72
Needs work
Phase 2+ fix highs
88
AI-ready
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the Discord HTTP API (stable) specification against thousands of deterministic rules we have refined over twelve years of building API tooling, supplemented by AI-based analysis. Every finding is reproducible from the spec itself, scored consistently, and paired with a concrete fix.
What's at stake

What these gaps cost you in production

4 failure modes across 3 groups, each driven by your audit scores. Several are active risks today.

Foundation The spec itself 40 / 100
Active risk · Standards compliance
Spec Violations Disrupt API Toolchains
You must address critical spec violations that break SDK generation and downstream integrations, impacting the Discord HTTP API's functionality.
22→29
code quality score out of 40: the lift consumers achieve when the underlying spec is clean and standards-compliant
APIMatic Context Plugins research · Series B · June 2026
Build Time Readiness AI writes the code 51 / 100
Active risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
The Discord HTTP API lacks essential descriptions for parameters and operations, leading to incorrect assumptions.
74%
of developers name missing or unclear documentation as the top reason they abandon an API. AI readers are stricter: what a human would ask about, an AI assumes.
APIMatic Developer Experience research · June 2026
Elevated risk · SDK readiness for AI
SDKs generate incorrect types and formats
You should refine the schema layer to ensure accurate integration code and prevent errors.
0
fabricated API constructs when a coding assistant was grounded in an AI-ready spec. Ambiguity in the spec is what triggers hallucinated integration code
APIMatic Context Plugins research · 6 APIs · 3 models · June 2026
Runtime Readiness Agents make the calls 47 / 100
Active risk · MCP readiness
Autonomous agents struggle with API execution
Autonomous agents misinterpret tool names and encounter unsafe request formats, risking failures in the Discord HTTP API.
65%
reduction in token consumption when agent tools are grounded in authoritative API context. Bloated or confusable tools consume up to 3.3× more.
APIMatic Context Plugins research · Series A · June 2026
The evidence numbers come from our controlled research: 6 experiments across 3 models, 6 commercial APIs, and 3 languages. We derive each card's risk status from this API's pillar scores. Full methodology at apimatic.io.
Contents

What's inside the full report

Unlock the full report

Book a free call to view the full report and the roadmap our team recommends to upgrade your developer and agentic experience.

Book a free call to view the full report