AI Readiness AuditRef. APM-7C4BB5DD · Confidential
Doctly API
An independent assessment of whether the Doctly API specification is ready for AI-assisted integration and autonomous agents, prepared for Doctly.
79/100
Needs work
Functional for AI-assisted builds.
Ready for autonomous agents.
Ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
79
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
230
Total instances: 0 critical, 7 high, 108 medium, 115 low
24
Rule groups across 4 pillars: 0 critical, 7 high sev. instances
Executive summary
Your Doctly API scores 79.3 out of 100, reflecting a mostly ready status with notable strengths in SDK readiness for AI at 88.4 and standards compliance at 81.9. However, documentation readiness for AI shows significant gaps at 62.8, and there are seven high findings among 24 rule groups, totaling 230 instances. While your API is functional for AI-assisted builds and ready for autonomous agents, addressing the documentation gaps is the most urgent action needed to improve overall readiness.
Readiness by pillar
Needs work
79 / 100
FoundationThe spec itself
82/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
82Mostly ready
Build Time ReadinessAI writes the code
76/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
63Significant 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
88AI-ready
Runtime ReadinessAgents make the calls
83/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
83Mostly ready
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Doctly 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
82 / 100
Managed · Standards compliance
Address URL Path Template Conflicts
We found an identical templated path that conflicts with a concrete path, which may disrupt SDK generation and 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
76 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API due to documentation gaps
You risk building on incorrect assumptions as parameter descriptions are missing or too brief, leading to potential data errors.
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 and formats
We see that the schema layer's ambiguity leads to occasional errors in the 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
83 / 100
Managed · MCP readiness
MCP Tools Require Minor Refinements
The Doctly API functions well, but agents struggle with tool names and context budgets. Addressing these issues will improve overall 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