AI Readiness AuditRef. APM-9AE5C6F0 · Confidential
AIS Data API Reference
An independent assessment of whether the AIS Data API Reference specification is ready for AI-assisted integration and autonomous agents, prepared for MarineTraffic.
74/100
Needs work
Ready for AI-assisted builds.
Not ready for autonomous agents.
Not ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
74
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
11
Critical blockers stopping entire operation groups for agents
2843
Total instances: 11 critical, 83 high, 816 medium, 1933 low
40
Rule groups across 4 pillars: 11 critical, 83 high sev. instances
Executive summary
Your API demonstrates readiness for AI-assisted builds with a composite score of 73.8 out of 100, but it falls short for autonomous agents. The SDK readiness for AI stands strong at 89.9, while the MCP readiness is critically low at 49. The documentation readiness for AI needs work, scoring 71.3, and the audit identified 11 critical findings and 83 high findings across 40 rule groups. To improve your API's overall performance, prioritize addressing the MCP readiness issues.
Readiness by pillar
Needs work
74 / 100
FoundationThe spec itself
81/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
81Mostly ready
Build Time ReadinessAI writes the code
81/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
71Needs work
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
90AI-ready
Runtime ReadinessAgents make the calls
49/100
MCP Readinesscapped · open criticals
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
49Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix criticals
Phase 2+ fix highs
Phase 3+ fix mediums & lows
About this report. We evaluated the AIS Data API Reference 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
Where you’re exposed – and where you’re not
4 failure modes across 3 groups. Some are active risks; others are under control.
Foundation
The spec itself
81 / 100
Managed · Standards compliance
Duplicate schema titles cause confusion
You should address the 65 instances of duplicate schema titles to prevent conflicts in 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
81 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
You should refine descriptions and examples to improve understanding and accuracy for coding assistants.
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
Managed · SDK readiness for AI
Refine Schema Layer for Clarity
We found that the schema layer contains ambiguities, leading to incorrect types and formats in generated SDKs and integration code.
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
49 / 100
Active risk · MCP readiness
Autonomous agents cannot execute API safely
The operationId collisions and confusable operations prevent agents from reliably selecting and calling the API, risking critical 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