AI Readiness AuditRef. APM-D422A978 · Confidential
dispensary
An independent assessment of whether the dispensary specification is ready for AI-assisted integration and autonomous agents, prepared for Treez.
78/100
Needs work
Gaps for AI-assisted builds.
Partially ready for autonomous agents.
Partially ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
78
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
8270
Total instances: 0 critical, 162 high, 5192 medium, 2916 low
47
Rule groups across 4 pillars: 0 critical, 162 high sev. instances
Executive summary
Your API has a composite score of 77.8 out of 100, reflecting a solid performance in standards compliance but significant weaknesses in documentation readiness for AI and SDK readiness for AI. The documentation score of 64.5 shows substantial gaps that hinder effective use, while the SDK score of 72.4 indicates areas needing improvement. Although agents can partially operate autonomously, gaps remain for AI-assisted builds. Addressing the documentation readiness should be your top priority to improve overall API performance.
Readiness by pillar
Needs work
78 / 100
FoundationThe spec itself
90/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
90AI-ready
Build Time ReadinessAI writes the code
69/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
65Significant gaps
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
72Needs work
Runtime ReadinessAgents make the calls
78/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
78Needs work
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the dispensary 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
Residual risks to monitor
No active failures, but elevated risks remain. Continued improvement will bring these into the managed band.
Foundation
The spec itself
90 / 100
Managed · Standards compliance
Address duplicate schema titles and requirements
You have duplicate schema titles and missing required schemas in media type objects, which can confuse integrations and break toolchains.
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
69 / 100
Elevated risk · Documentation readiness for AI
AI Readers Misinterpret API Documentation
AI readers struggle to understand the dispensary API due to missing or vague parameter descriptions, leading to incorrect assumptions during builds.
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 return incorrect types and formats
You should refine the success response to include a body schema to improve integration accuracy.
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
78 / 100
Elevated risk · MCP readiness
Confusing Operations Hinder API Execution
Autonomous agents struggle to select and execute operations due to confusable names and inconsistent error responses, impacting dispensary functionality.
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