AI Readiness Audit
Ref. APM-08970E9C · Confidential

Quote Management (Ethernet)

An independent assessment of whether the Quote Management (Ethernet) specification is ready for AI-assisted integration and autonomous agents, prepared for BT Group.

Prepared for
BT Group
Subject
Quote Management (Ethernet) v0.7
Scope
5 operations · 4 pillars · 3 groups
Date
October 2026
53/100
Not ready
Functional for AI-assisted builds.
Partially ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
Import blocked: SDK, docs, and MCP generators will refuse this spec

The validation engine found 1 blocking violation: While parsing a quoted scalar, an unknown escape character was 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
87
Total instances: 1 critical, 1 high, 20 medium, 65 low
15
Rule groups across 4 pillars: 1 critical, 1 high sev. instances
Executive summary

Your API for Quote Management has a critical blocking violation that prevents any SDK, documentation, or MCP generation, which is the most pressing issue we identified. The overall composite score of 52.8 indicates that your API is not ready, with standards compliance scoring only 40. The documentation and SDK readiness for AI show significant gaps, scoring 62.8 and 61.9 respectively. To move forward, you must address the blocking violation to enable further development and improve your API's readiness.

Readiness by pillar
Not ready 53 / 100
FoundationThe spec itself
40/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
40Not ready
Build Time ReadinessAI writes the code
62/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
63Significant 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
62Significant gaps
Runtime ReadinessAgents make the calls
53/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
53Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
53
Not ready
Phase 1fix criticals
98
AI-ready
Phase 2+ fix highs
99
AI-ready
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the Quote Management (Ethernet) 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 40 / 100
Active risk · Standards compliance
Escape character violations break integrations
You must fix the unknown escape character in quoted scalar values 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 62 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
You must improve documentation clarity and detail to prevent incorrect assumptions in quote management.
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
You should refine the schema layer to ensure accurate integration code and prevent errors.
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 53 / 100
Active risk · MCP readiness
Agents fail to execute API operations
The operation descriptions lack essential content, preventing agents from safely selecting and calling the API.
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