AI Readiness AuditRef. APM-4A0CAB58 · Confidential
AI API
An independent assessment of whether the AI API specification is ready for AI-assisted integration and autonomous agents, prepared for Elliptic.
86/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
86
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
142
Total instances: 0 critical, 9 high, 56 medium, 77 low
22
Rule groups across 4 pillars: 0 critical, 9 high sev. instances
Executive summary
Your AI API scores an impressive 86.2 out of 100, demonstrating strong compliance with standards and excellent SDK readiness. However, documentation readiness shows significant gaps at 69.8, and MCP readiness requires attention with a score of 77.1. While the API functions well for AI-assisted builds, it is not prepared for autonomous agent calls. Prioritizing improvements in documentation will be essential for achieving full readiness.
Readiness by pillar
AI-ready
86 / 100
FoundationThe spec itself
97/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
97AI-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
70Significant 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
95AI-ready
Runtime ReadinessAgents make the calls
77/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
77Needs work
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the AI API 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
97 / 100
Managed · Standards compliance
Circular reference in schema definitions
We found a circular reference in the schema definitions that may disrupt SDK generation and 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 Sparse Documentation
You must improve parameter descriptions; missing or short explanations lead AI readers to build on incorrect assumptions about the payments API.
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 occasionally, but you maintain a high readiness score
The AI API for payments performs well overall, with minor adjustments needed for schema clarity.
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
77 / 100
Elevated risk · MCP readiness
Agents struggle to execute API calls
The AI API lacks a JSON request/response variant, which complicates safe execution and may lead to errors.
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