AI Readiness AuditRef. APM-D8F5E739 · Confidential
Comarch IoT Platform REST API
An independent assessment of whether the Comarch IoT Platform REST API specification is ready for AI-assisted integration and autonomous agents, prepared for Comarch.
62/100
Significant gaps
Gaps 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
62
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
3214
Total instances: 0 critical, 333 high, 1464 medium, 1417 low
62
Rule groups across 4 pillars: 0 critical, 333 high sev. instances
Executive summary
Your API scored 61.6 out of 100, reflecting significant gaps in multiple areas. Standards compliance received a score of 65.3, while documentation readiness for AI fell to 57.8. SDK readiness for AI scored 63.1, and MCP readiness reached only 58.4. You must prioritize addressing the 333 high findings to improve your API's readiness for AI-assisted builds and autonomous agents.
Readiness by pillar
Significant gaps
62 / 100
FoundationThe spec itself
65/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
65Significant gaps
Build Time ReadinessAI writes the code
61/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
58Significant 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
63Significant gaps
Runtime ReadinessAgents make the calls
58/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
58Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Comarch IoT Platform REST 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
Residual risks to monitor
No active failures, but elevated risks remain. Continued improvement will bring these into the managed band.
Foundation
The spec itself
65 / 100
Elevated risk · Standards compliance
Specification violations disrupt integrations and SDKs
You must address invalid property types and $ref paths to prevent toolchain failures.
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
61 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API due to documentation gaps
You must provide detailed parameter descriptions to prevent coding assistants from building on incorrect assumptions.
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
The success response lacks a body schema, causing integration code to misinterpret data structures.
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
58 / 100
Elevated risk · MCP readiness
MCP Tools Fail to Execute API Safely
The autonomous agents cannot select or call the API due to missing operation identifiers and confusing tool names, risking operational 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