AI Readiness Audit
Ref. APM-EBB4ED33 · Confidential

Due API

An independent assessment of whether the Due API specification is ready for AI-assisted integration and autonomous agents, prepared for Due.

Prepared for
Due
Subject
Due API
Scope
84 operations · 4 pillars · 3 groups
Date
October 2026
45/100
Not ready
Gaps for AI-assisted builds.
Broken for autonomous agents.
Reach AI-ready by Phase 2; resolve all findings → 100 · AI-ready
Import blocked: SDK, docs, and MCP generators will refuse this spec

The validation engine found 1 blocking violation: A discriminator cannot be present in a `oneOf` schema containing primitive type case(s).. Import tools reject the specification outright until it is fixed, so nothing downstream can be generated regardless of the other pillar scores. While this gate is open, the Standards Compliance score is capped at 40 and every AI pillar weights standards at 60% (normally 30%). Fixing the blocker in Phase 1 lifts the caps; the score projection below shows what that unlocks.

2
Critical blockers stopping entire operation groups for agents
4583
Total instances: 2 critical, 316 high, 2119 medium, 2146 low
53
Rule groups across 4 pillars: 2 critical, 316 high sev. instances
Executive summary

Your API cannot generate SDKs, documentation, or MCPs due to a blocking violation in the specification. The overall composite score of 45.3 out of 100 indicates significant weaknesses, particularly in standards compliance at 40 and documentation readiness for AI at 43.6. While SDK readiness shows some progress at 58.1, the audit identified 316 high findings and 4583 instances across 53 rule groups, revealing critical gaps for AI-assisted builds and broken functionality for autonomous agents. Addressing the blocking violation is the most urgent action needed to move forward.

Readiness by pillar
Not ready 45 / 100
FoundationThe spec itself
40/100
Standards Compliancecapped · import blocked
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
40Not ready
Build Time ReadinessAI writes the code
51/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
44Not 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
58Significant gaps
Runtime ReadinessAgents make the calls
42/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
42Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
45
Not ready
Phase 1fix criticals
60
Significant gaps
Phase 2+ fix highs
91
AI-ready
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the Due 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

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 40 / 100
Active risk · Standards compliance
Discriminator Misconfigurations Break Payment Integrations
You must address critical spec violations that disrupt SDK generation and downstream integrations, risking payment processing functionality.
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 51 / 100
Active risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
You must provide detailed descriptions for parameters and operations to ensure accurate understanding.
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 ensure accurate integration code for payments.
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 42 / 100
Active risk · MCP readiness
MCP Tools Fail to Execute API Safely
Autonomous agents cannot select or call the payments API due to missing operation identifiers and confusing operation names. This lack of clarity severely impacts runtime execution and safety.
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

What's inside the full report

Unlock the full report

Book a free call to view the full report and the roadmap our team recommends to upgrade your developer and agentic experience.

Book a free call to view the full report