AI Readiness AuditRef. APM-EB699C24 · Confidential
Resistant Documents API
An independent assessment of whether the Resistant Documents API specification is ready for AI-assisted integration and autonomous agents, prepared for Resistant AI.
52/100
Not ready
Functional for AI-assisted builds.
Not ready for autonomous agents.
Not ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
52
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
1049
Total instances: 0 critical, 113 high, 405 medium, 531 low
42
Rule groups across 4 pillars: 0 critical, 113 high sev. instances
Executive summary
Your Resistant Documents API scores 52.2 out of 100, which reflects a grade of F and indicates that your API is not ready for full deployment. The API shows significant weaknesses in standards compliance with a score of 35, and documentation readiness for AI at 48.5, both of which require immediate attention. While SDK readiness for AI is relatively better at 76.6, it still needs work, and your API is not ready for autonomous agents in runtime scenarios. Prioritizing improvements in standards compliance will be essential for advancing your API's readiness.
Readiness by pillar
Not ready
52 / 100
FoundationThe spec itself
35/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
35Not ready
Build Time ReadinessAI writes the code
63/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
49Not 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
77Needs work
Runtime ReadinessAgents make the calls
58/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
58Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Resistant Documents 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
35 / 100
Active risk · Standards compliance
Fix Spec Violations to Prevent Breaks
You must address four high-risk spec violations that disrupt toolchains and SDK generation for the Resistant Documents API.
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
63 / 100
Active risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
The Resistant Documents API lacks essential parameter descriptions, leading to incorrect assumptions in payment processing.
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
58 / 100
Elevated risk · MCP readiness
Agents misinterpret operation descriptions in API
The operation description lacks essential content, preventing agents from safely executing payment processes.
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