AI Readiness AuditRef. APM-DAA3FBA2 · Confidential
Quaderno API
An independent assessment of whether the Quaderno API specification is ready for AI-assisted integration and autonomous agents, prepared for Quaderno.
62/100
Significant gaps
Gaps for AI-assisted builds.
Partially ready for autonomous agents.
Partially ready for autonomous agents.
Reach Mostly 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
1394
Total instances: 0 critical, 31 high, 692 medium, 671 low
50
Rule groups across 4 pillars: 0 critical, 31 high sev. instances
Executive summary
Your API scores 61.5 out of 100, reflecting significant gaps in several areas. Standards compliance scored 53.8, showing it is not ready for effective use. Documentation readiness for AI received a score of 59.7, while SDK readiness and MCP readiness both fell short with scores of 68.5 and 67.9, respectively. You must prioritize addressing the gaps for AI-assisted builds to improve overall readiness.
Readiness by pillar
Significant gaps
62 / 100
FoundationThe spec itself
54/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
54Not ready
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
60Significant 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
69Significant gaps
Runtime ReadinessAgents make the calls
68/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
68Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Quaderno 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
Where you’re exposed – and where you’re not
4 failure modes across 3 groups. Some are active risks; others are under control.
Foundation
The spec itself
54 / 100
Active risk · Standards compliance
Schema violations disrupt payment integrations
You must correct invalid schema types and version numbers to ensure downstream tools function properly.
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 Quaderno API details
Sparse and generic documentation leads to incorrect assumptions, risking payment processing accuracy.
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 in responses
The Quaderno API's success responses lack body schemas, causing integration code to generate wrong types and formats.
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
68 / 100
Elevated risk · MCP readiness
Agents misinterpret GET operation semantics, Agents cannot safely execute the Quaderno API due to misleading operation descriptions and mutation verbs in GET requests
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