AI Readiness Audit
Ref. APM-BA9E86CA · Confidential

Vendor API

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

Prepared for
Nomba
Subject
Vendor API v1.0.0
Scope
67 operations · 4 pillars · 3 groups
Date
October 2026
46/100
Not ready
Functional for AI-assisted builds.
Ready 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: The definition for path parameter used in the path URL does not exist.. 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
1753
Total instances: 1 critical, 24 high, 546 medium, 1182 low
43
Rule groups across 4 pillars: 1 critical, 24 high sev. instances
Executive summary

Your API contains one blocking violation that prevents any SDK, documentation, or MCP generators from importing it, which is the most critical issue we identified. The overall composite score of 46 out of 100 indicates that your API is not ready, with significant weaknesses in standards compliance at 34.2 and documentation readiness for AI at 46. While the SDK readiness for AI shows some progress at 56.8, the 24 high findings and 43 rule groups with 1,753 instances of issues highlight the need for immediate attention. Fixing the blocking violation is essential to move forward with any development efforts.

Readiness by pillar
Not ready 46 / 100
FoundationThe spec itself
34/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
34Not ready
Build Time ReadinessAI writes the code
51/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
46Not 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
57Significant gaps
Runtime ReadinessAgents make the calls
53/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
53Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
46
Not ready
Phase 1fix criticals
64
Significant gaps
Phase 2+ fix highs
69
Significant gaps
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the Vendor 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 34 / 100
Active risk · Standards compliance
Path Parameter Violations Disrupt Integrations
The API's path parameters lack definitions, breaking toolchains and SDK generation for payments. Unresolved schema issues further complicate 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 51 / 100
Active risk · Documentation readiness for AI
AI Readers Misinterpret Sparse API Documentation
You must improve parameter descriptions; missing or vague details prevent AI readers from accurately understanding your payments API.
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, 183 instances
You must clarify the schema layer to ensure accurate integration with the payments API.
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 53 / 100
Active risk · MCP readiness
Agents misinterpret operation descriptions, causing failures
The operation's description lacks necessary content, preventing agents from safely executing payment API calls.
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