AI Readiness AuditRef. APM-8A8792BD · Confidential
Airtm Enterprise API V2
An independent assessment of whether the Airtm Enterprise API V2 specification is ready for AI-assisted integration and autonomous agents, prepared for Airtm.
51/100
Not ready
Functional for AI-assisted builds.
Not ready for autonomous agents.
Not ready for autonomous agents.
Resolve all findings (through Phase 2) → score reaches 100 · AI-ready
F
D
C
B
A
51
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
2085
Total instances: 0 critical, 83 high, 971 medium, 1031 low
45
Rule groups across 4 pillars: 0 critical, 83 high sev. instances
Executive summary
Your API, Airtm Enterprise API V2, scored 50.8 out of 100, which places it in the "Not ready" category with a grade of F. The API struggles with standards compliance, scoring 37.3, and documentation readiness for AI, scoring 50.6. While SDK readiness for AI shows some promise at 70.6, agents cannot autonomously make calls due to the API's runtime readiness issues. To improve your API's performance, prioritize addressing the high findings, which total 83.
Readiness by pillar
Not ready
51 / 100
FoundationThe spec itself
37/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
37Not ready
Build Time ReadinessAI writes the code
61/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
51Not 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
71Needs work
Runtime ReadinessAgents make the calls
51/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
51Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Airtm Enterprise API V2 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
37 / 100
Active risk · Standards compliance
Specification violations disrupt API functionality
You must address invalid specification extensions, security scheme names, and webhook keys 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
61 / 100
Active risk · Documentation readiness for AI
AI Readers Misinterpret API Documentation Quality
AI readers struggle to understand the Airtm Enterprise API due to missing or vague parameter descriptions, 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 improve accuracy in AI-generated integration code.
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
51 / 100
Active risk · MCP readiness
Autonomous agents cannot execute API safely
The lack of labeled sandbox servers and missing security scheme references prevent agents from safely calling the Airtm Enterprise 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