AI Readiness AuditRef. APM-084F3F52 · Confidential
DIDWW Public API
An independent assessment of whether the DIDWW Public API specification is ready for AI-assisted integration and autonomous agents, prepared for DIDWW.
68/100
Significant gaps
Functional for AI-assisted builds.
Partially ready for autonomous agents.
Partially ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
68
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
4515
Total instances: 0 critical, 116 high, 1867 medium, 2532 low
38
Rule groups across 4 pillars: 0 critical, 116 high sev. instances
Executive summary
Your API scored 68.4 out of 100, reflecting significant gaps in standards compliance and documentation readiness for AI. The API functions for AI-assisted builds but only partially supports autonomous agents. The audit identified 116 high findings across 38 rule groups, with 4,515 instances needing attention. To improve your API's performance, prioritize addressing the significant gaps in standards compliance.
Readiness by pillar
Significant gaps
68 / 100
FoundationThe spec itself
61/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
61Significant gaps
Build Time ReadinessAI writes the code
72/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
76Needs work
Runtime ReadinessAgents make the calls
72/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
72Needs work
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the DIDWW Public 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
61 / 100
Elevated risk · Standards compliance
Spec Violations Disrupt API Integrations
You must address five high-severity spec violations that break toolchains and SDK generation, impacting 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
72 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API parameters due to sparse descriptions
The DIDWW Public API lacks sufficient parameter descriptions, leading to incorrect assumptions and potential integration failures.
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
72 / 100
Elevated risk · MCP readiness
Confusing Operations Hinder API Execution
Agents struggle to select and execute operations due to unclear descriptions and missing JSON formats, impacting API performance.
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