AI Readiness AuditRef. APM-A9B98279 · Confidential
TM-Shippers: Load API
An independent assessment of whether the TM-Shippers: Load API specification is ready for AI-assisted integration and autonomous agents, prepared for E2open (SwaggerHub Logistics).
57/100
Significant gaps
Gaps for AI-assisted builds.
Broken for autonomous agents.
Broken for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
57
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
954
Total instances: 0 critical, 71 high, 445 medium, 438 low
31
Rule groups across 4 pillars: 0 critical, 71 high sev. instances
Executive summary
Your Load API scores 57.3 out of 100, reflecting significant gaps in readiness. Standards compliance scored 54.2, while documentation readiness for AI reached 56. SDK readiness for AI showed some promise at 70.4, but MCP readiness fell to 50.1. The audit identified 71 high findings across 31 rule groups, with 954 instances needing attention. The most pressing action is to address the gaps for AI-assisted builds and fix the issues preventing autonomous agents from functioning effectively.
Readiness by pillar
Significant gaps
57 / 100
FoundationThe spec itself
54/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
54Not 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
56Significant gaps
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
70Needs work
Runtime ReadinessAgents make the calls
50/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
50Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the TM-Shippers: Load 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
54 / 100
Active risk · Standards compliance
Toolchain Breaks Due to Spec Violations
You must address missing operation IDs and incorrect parameter types to prevent failures in SDK generation and 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
63 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
You must improve documentation clarity and detail to prevent incorrect assumptions during builds.
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 return incorrect types and formats
You should refine the success response to include a body schema to improve integration accuracy.
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
50 / 100
Active risk · MCP readiness
MCP Tools Cannot Execute API Safely
Autonomous agents cannot select or call the Load API due to missing operation identifiers and improper request formats, risking runtime failures.
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