AI Readiness AuditRef. APM-DB143C5A · Confidential
Goodstack Services
An independent assessment of whether the Goodstack Services specification is ready for AI-assisted integration and autonomous agents, prepared for Goodstack.
62/100
Significant gaps
Gaps for AI-assisted builds.
Not ready for autonomous agents.
Not ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
62
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
4633
Total instances: 0 critical, 275 high, 2432 medium, 1926 low
56
Rule groups across 4 pillars: 0 critical, 275 high sev. instances
Executive summary
Goodstack Services scores 61.9/100: Significant gaps · Grade D. The weakest pillar is Standards compliance at 58; the strongest is SDK readiness for AI at 70. We recorded 4633 finding instances: 0 critical, 275 high, 2432 medium, and 1926 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
Significant gaps
62 / 100
FoundationThe spec itself
58/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
58Significant gaps
Build Time ReadinessAI writes the code
64/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
59Significant 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
70Significant gaps
Runtime ReadinessAgents make the calls
64/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
64Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Goodstack Services 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
58 / 100
Elevated risk · Standards compliance
Schema violations disrupt payments integrations
You must address invalid schema types and missing operation IDs to prevent toolchain failures.
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
64 / 100
Elevated risk · Documentation readiness for AI
AI Readers Misinterpret API Documentation
You must improve parameter descriptions; missing or vague details lead AI readers to build on incorrect assumptions, risking payment processing errors.
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
The ambiguous schema layer causes generated SDKs and AI-written integration code to ship wrong types, risking payment processing 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
64 / 100
Elevated risk · MCP readiness
MCP Tools Fail to Execute API Safely
Autonomous agents cannot select or call the Goodstack Services API due to missing operation identifiers and unclear descriptions. This confusion risks payment processing failures and operational disruptions.
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