AI Readiness Audit
Ref. APM-111716B7 · Confidential

Harmonic.ai Public API

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

Prepared for
Harmonic.ai
Subject
Harmonic.ai Public API v0.0.1
Scope
94 operations · 4 pillars · 3 groups
Date
October 2026
35/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: 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.

7
Critical blockers stopping entire operation groups for agents
7577
Total instances: 7 critical, 946 high, 3411 medium, 3213 low
54
Rule groups across 4 pillars: 7 critical, 946 high sev. instances
Executive summary

Your API currently has a blocking violation that prevents any SDK, documentation, or MCP generators from importing it, which is the most critical issue to address. The overall composite score of 35.2 out of 100 indicates that your API is not ready, with particularly low scores in standards compliance at 24 and documentation readiness for AI at 34.8. While the API is functional for AI-assisted builds, it is broken for autonomous agents, and the audit identified 946 high findings among a total of 7,577 instances across 54 rule groups. Prioritizing the resolution of the blocking violation is essential for moving forward.

Readiness by pillar
Not ready 35 / 100
FoundationThe spec itself
24/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
24Not ready
Build Time ReadinessAI writes the code
44/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
35Not 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
35/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
35Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
35
Not ready
Phase 1fix criticals
52
Not ready
Phase 2+ fix highs
95
AI-ready
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the Harmonic.ai Public 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 24 / 100
Active risk · Standards compliance
Path parameter definitions are missing
You must define all path parameters in the Operation Objects to prevent toolchain failures and integration issues.
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 44 / 100
Active risk · Documentation readiness for AI
AI readers misinterpret API due to documentation gaps
You must provide detailed parameter descriptions 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
Active risk · SDK readiness for AI
SDKs generate incorrect types and formats
You must clarify the schema layer to ensure accurate AI-generated 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 35 / 100
Active risk · MCP readiness
Autonomous agents cannot execute API calls
The operationId collisions and confusable operations prevent agents from safely selecting and executing tasks, risking data integrity.
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