AI Readiness Audit
Ref. APM-AE91BE8A · Confidential

Kasko Event API

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

Prepared for
Kasko
Subject
Kasko Event API v1.0.0
Scope
1 operations · 4 pillars · 3 groups
Date
October 2026
43/100
Not ready
Functional for AI-assisted builds.
Broken for autonomous agents.
Reach AI-ready by Phase 2; resolve all findings → 100 · AI-ready
Import blocked: SDK, docs, and MCP generators will refuse this spec

The validation engine found 1 blocking violation: Invalid callback key found.. 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
60
Total instances: 1 critical, 8 high, 14 medium, 37 low
27
Rule groups across 4 pillars: 1 critical, 8 high sev. instances
Executive summary

Your Kasko Event API cannot generate SDKs, documentation, or MCPs due to one blocking violation in the spec. The overall composite score of 42.8 reflects significant weaknesses, particularly in standards compliance at 36.1 and MCP readiness at 38.2. While the API is functional for AI-assisted builds, it is broken for autonomous agents, which limits its usability. Fixing the blocking violation is the most critical action needed to move forward.

Readiness by pillar
Not ready 43 / 100
FoundationThe spec itself
36/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
36Not ready
Build Time ReadinessAI writes the code
50/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
48Not 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
52Not ready
Runtime ReadinessAgents make the calls
38/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
38Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
43
Not ready
Phase 1fix criticals
65
Significant gaps
Phase 2+ fix highs
89
AI-ready
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the Kasko Event 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 36 / 100
Active risk · Standards compliance
Invalid specifications break integrations and tools
You must address invalid callback keys and missing operation IDs to prevent downstream 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 50 / 100
Active risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
Sparse and generic documentation prevents coding assistants from accurately understanding the Kasko Event 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
Active risk · SDK readiness for AI
SDKs generate incorrect types and formats
The Kasko Event API's 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 38 / 100
Active risk · MCP readiness
MCP Tools Cannot Execute API Safely
Autonomous agents cannot select or call the Kasko Event API due to missing operation identifiers and unclear descriptions, 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

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