AI Readiness Audit
Ref. APM-220A2048 · Confidential

Zadarma API

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

Prepared for
Zadarma
Subject
Zadarma API v1.2.0
Scope
113 operations · 4 pillars · 3 groups
Date
October 2026
50/100
Not ready
Functional for AI-assisted builds.
Ready for autonomous agents.
Reach Mostly ready by Phase 1; resolve all findings → 100 · AI-ready
Import blocked: SDK, docs, and MCP generators will refuse this spec

The validation engine found 1 blocking violation: Unregistered HTTP security scheme detected.. 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.

1
Critical blocker stopping entire operation groups for agents
2660
Total instances: 1 critical, 44 high, 1442 medium, 1173 low
36
Rule groups across 4 pillars: 1 critical, 44 high sev. instances
Executive summary

Your API contains one blocking violation that prevents SDK, documentation, and MCP generators from importing it, which caps your scores and limits functionality. The overall composite score is 49.7 out of 100, with significant weaknesses in standards compliance and documentation readiness for AI. While your API is functional for AI-assisted builds, it has 44 high findings and a total of 2,660 instances across 36 rule groups that need addressing. Fixing the blocking violation is the single most important action to take for improvement.

Readiness by pillar
Not ready 50 / 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
53/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
50Not 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
56Significant gaps
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
50
Not ready
Phase 1fix criticals
81
Mostly ready
Phase 2+ fix highs
86
AI-ready
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the Zadarma 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
Unregistered Security Scheme Breaks Integrations
The Zadarma API lacks a registered HTTP security scheme, which disrupts toolchains and prevents secure 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 53 / 100
Active risk · Documentation readiness for AI
AI Readers Misinterpret Sparse Documentation
You must provide detailed descriptions for parameters; missing information leads to incorrect assumptions and flawed API interactions.
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 must clarify the schema layer to prevent integration issues and improve SDK readiness.
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 misidentify operations due to confusion
The Zadarma API has operations with similar names, unclear descriptions, and missing JSON formats, which disrupts safe execution.
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