AI Readiness AuditRef. APM-CA2CD8AA · Confidential
Core
An independent assessment of whether the Core specification is ready for AI-assisted integration and autonomous agents, prepared for Stedi.
85/100
AI-ready
Functional 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
85
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
1109
Total instances: 0 critical, 26 high, 249 medium, 834 low
36
Rule groups across 4 pillars: 0 critical, 26 high sev. instances
Executive summary
Your API scores an impressive 85 out of 100, demonstrating strong standards compliance and SDK readiness for AI integration. However, documentation readiness shows significant gaps at 69.2, and MCP readiness requires attention with a score of 74.7. While your API is functional for AI-assisted builds, it is not ready for autonomous agents to make calls. Prioritizing improvements in documentation and MCP readiness will be essential for achieving full AI readiness.
Readiness by pillar
AI-ready
85 / 100
FoundationThe spec itself
96/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
96AI-ready
Build Time ReadinessAI writes the code
82/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
69Significant 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
94AI-ready
Runtime ReadinessAgents make the calls
75/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
75Needs work
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Core 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
96 / 100
Managed · Standards compliance
Address minor spec violations now
We found minor spec violations that could disrupt toolchains and SDK generation; addressing these will ensure smoother downstream integrations.
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
82 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API details due to sparse documentation
You must provide clear parameter descriptions to prevent coding assistants from building on 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
Managed · SDK readiness for AI
SDKs generate incorrect types and formats
You should refine the success response to include a body schema for accurate integration.
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
75 / 100
Elevated risk · MCP readiness
Confusing Operations Impact API Execution
Autonomous agents struggle to select and execute operations due to confusable names and inconsistent error responses, risking user experience.
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