AI Readiness Audit
Ref. APM-A4E97D22 · Confidential

Ninja Van API (Order API)

An independent assessment of whether the Ninja Van API (Order API) specification is ready for AI-assisted integration and autonomous agents, prepared for Ninja Van.

Prepared for
Ninja Van
Subject
Ninja Van API (Order API) v4.1.0
Scope
23 operations · 4 pillars · 3 groups
Date
October 2026
32/100
Not ready
Gaps for AI-assisted builds.
Not 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
921
Total instances: 1 critical, 87 high, 340 medium, 493 low
46
Rule groups across 4 pillars: 1 critical, 87 high sev. instances
Executive summary

Your API cannot generate SDKs, documentation, or MCPs due to a blocking violation in the specification. The overall composite score of 32.2 out of 100 indicates significant readiness issues, with standards compliance at 21.1 and documentation readiness at 38.1. We identified 46 rule groups with 921 instances of findings, including one critical and 87 high findings. To move forward, you must address the blocking violation to enable any generation from the API specification.

Readiness by pillar
Not ready 32 / 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
38/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
38Not 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
39Not ready
Runtime ReadinessAgents make the calls
36/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
36Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
32
Not ready
Phase 1fix criticals
48
Not ready
Phase 2+ fix highs
77
Needs work
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the Ninja Van API (Order 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
Path parameter definitions break integrations
The Ninja Van API lacks critical path parameter definitions, causing failures in toolchains and SDK generation before any AI processes the spec.
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 38 / 100
Active risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
The Ninja Van API lacks sufficient parameter descriptions, leading to incorrect assumptions and potential integration failures.
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
The success response for the Ninja Van Order API lacks a body schema, causing integration code to fail.
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 36 / 100
Active risk · MCP readiness
MCP tools cannot execute API safely
Autonomous agents cannot select or call the API due to missing operation identifiers and misleading GET operation semantics.
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