AI Readiness Audit
Ref. APM-693C8690 · Confidential

Zeepay Company Limited API

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

Prepared for
Zeepay Company Limited
Subject
Zeepay Company Limited API v1.0.0
Scope
19 operations · 4 pillars · 3 groups
Date
October 2026
33/100
Not ready
Functional for AI-assisted builds.
Broken for autonomous agents.
Resolve all findings (through Phase 3) → score reaches 100 · AI-ready
Import blocked: SDK, docs, and MCP generators will refuse this spec

The validation engine found 1 blocking violation: Reference could not be resolved.. 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
583
Total instances: 1 critical, 44 high, 342 medium, 196 low
40
Rule groups across 4 pillars: 1 critical, 44 high sev. instances
Executive summary

Your API contains one blocking violation that prevents any SDK, documentation, or MCP generation. The overall composite score is 32.5 out of 100, reflecting significant weaknesses in standards compliance at 21.1, documentation readiness for AI at 34.8, and MCP readiness at 31.8. While the API is functional for AI-assisted builds, it is broken for autonomous agents, with 583 instances of findings across 40 rule groups. Fixing the blocking violation is the single most important action needed to move forward.

Readiness by pillar
Not ready 33 / 100
FoundationThe spec itself
21/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
21Not ready
Build Time ReadinessAI writes the code
41/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
35Not 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
48Not ready
Runtime ReadinessAgents make the calls
32/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
32Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
33
Not ready
Phase 1fix criticals
50
Not ready
Phase 2+ fix highs
77
Needs work
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the Zeepay Company Limited 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 21 / 100
Active risk · Standards compliance
Spec Violations Disrupt Payments API Functionality
You must resolve reference paths and include unique operation IDs to prevent toolchain failures and integration issues.
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 41 / 100
Active risk · Documentation readiness for AI
AI readers misinterpret Zeepay API details
Sparse and generic documentation leads to incorrect assumptions, risking payment processing accuracy.
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
Active risk · SDK readiness for AI
SDKs generate incorrect types and formats
You must clarify the schema layer to prevent integration failures in payment processing.
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 32 / 100
Active risk · MCP readiness
Autonomous Agents Cannot Execute API Safely
The Zeepay Company Limited API lacks essential operation identifiers and safety semantics, risking incorrect agent actions during payment processing.
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