AI Readiness Audit
Ref. APM-DC381848 · Confidential

AeroAPI v4

An independent assessment of whether the AeroAPI v4 specification is ready for AI-assisted integration and autonomous agents, prepared for FlightAware.

Prepared for
FlightAware
Subject
AeroAPI v4 v4.17.1
Scope
58 operations · 4 pillars · 3 groups
Date
October 2026
37/100
Not ready
Functional for AI-assisted builds.
Partially ready 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
3891
Total instances: 1 critical, 221 high, 968 medium, 2701 low
40
Rule groups across 4 pillars: 1 critical, 221 high sev. instances
Executive summary

Your API, AeroAPI v4, cannot generate SDKs, documentation, or MCPs due to one blocking violation in the specification. The overall composite score of 36.6 out of 100 indicates significant weaknesses, particularly in standards compliance at 22.9 and documentation readiness for AI at 40.8. While the API is functional for AI-assisted builds, it is only partially ready for autonomous agents, with 221 high findings and a total of 3,891 issues across 40 rule groups. Fixing the blocking violation is the most critical action needed to move forward.

Readiness by pillar
Not ready 37 / 100
FoundationThe spec itself
23/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
23Not 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
41Not 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
46Not ready
Runtime ReadinessAgents make the calls
43/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
43Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
37
Not ready
Phase 1fix criticals
55
Significant gaps
Phase 2+ fix highs
95
AI-ready
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the AeroAPI v4 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 23 / 100
Active risk · Standards compliance
Spec Violations Disrupt API Functionality
You must address critical spec violations that break toolchains and SDK generation, impacting downstream integrations before AI processes the spec.
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 gaps
The Parameter Object lacks a description, causing AI tools to build 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
Active risk · SDK readiness for AI
SDKs generate incorrect types and formats
The success response for AeroAPI v4 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 43 / 100
Active risk · MCP readiness
Agents misidentify operations due to confusion
The AeroAPI v4 contains two confusable operations and insufficient descriptions, which prevent agents from executing tasks safely.
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