AI Readiness AuditRef. APM-1BABE3E0 · Confidential
Domain Public API
An independent assessment of whether the Domain Public API specification is ready for AI-assisted integration and autonomous agents, prepared for Domain Group.
68/100
Significant gaps
Functional for AI-assisted builds.
Partially ready for autonomous agents.
Partially ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
68
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
7605
Total instances: 0 critical, 235 high, 2410 medium, 4960 low
58
Rule groups across 4 pillars: 0 critical, 235 high sev. instances
Executive summary
Your API scored 67.6 out of 100, reflecting significant gaps in several areas. Standards compliance scored 64.4, while documentation readiness for AI received a low score of 58.2. Although SDK readiness for AI is relatively better at 79.5, it still requires work. To improve overall performance, prioritize addressing the 235 high findings identified in the audit.
Readiness by pillar
Significant gaps
68 / 100
FoundationThe spec itself
64/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
64Significant gaps
Build Time ReadinessAI writes the code
69/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
80Needs work
Runtime ReadinessAgents make the calls
70/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
70Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Domain 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
Residual risks to monitor
No active failures, but elevated risks remain. Continued improvement will bring these into the managed band.
Foundation
The spec itself
64 / 100
Elevated risk · Standards compliance
Schema violations disrupt toolchain functionality
You must address invalid schema types and undefined properties to ensure proper SDK generation and integration.
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
69 / 100
Elevated risk · Documentation readiness for AI
AI Readers Misinterpret API Documentation
AI readers struggle to understand the API due to missing or vague parameter descriptions, leading to 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
Elevated risk · SDK readiness for AI
SDKs generate incorrect types and formats
You should address the ambiguous schema layer to ensure accurate integration code and responses.
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
70 / 100
Elevated risk · MCP readiness
Autonomous Agents Misinterpret API Operations
Autonomous agents misinterpret two operations due to confusable names and unclear descriptions, risking incorrect API execution.
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