AI Readiness AuditRef. APM-D7CFB3F2 · Confidential
Unit21 Customer Data Endpoints
An independent assessment of whether the Unit21 Customer Data Endpoints specification is ready for AI-assisted integration and autonomous agents, prepared for Unit21.
76/100
Needs work
Functional for AI-assisted builds.
Broken for autonomous agents.
Broken for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
76
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
826
Total instances: 0 critical, 65 high, 349 medium, 412 low
40
Rule groups across 4 pillars: 0 critical, 65 high sev. instances
Executive summary
Unit21 Customer Data Endpoints scores 75.9/100: Needs work · Grade C. The weakest pillar is MCP readiness at 62; the strongest is Standards compliance at 85. We recorded 826 finding instances: 0 critical, 65 high, 349 medium, and 412 low. Functional for AI-assisted builds. Broken for autonomous agents. Every finding lives in the specification, and the roadmap in this report orders the fixes by impact; resolving them projects the score to 100/100.
Readiness by pillar
Needs work
76 / 100
FoundationThe spec itself
85/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
85Mostly ready
Build Time ReadinessAI writes the code
76/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
75Needs work
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
78Needs work
Runtime ReadinessAgents make the calls
62/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
62Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Unit21 Customer Data Endpoints 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
85 / 100
Managed · Standards compliance
Address Schema Violations in API Spec
You must define the required schema for each media type object to prevent downstream integration issues and confusion.
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
76 / 100
Elevated risk · Documentation readiness for AI
Improve Parameter Descriptions for Clarity
You must provide detailed descriptions for parameter objects to assist coding assistants in accurately interpreting the 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
Elevated risk · SDK readiness for AI
SDKs return incorrect types and formats
You should address the ambiguous schema layer to ensure accurate responses from the Unit21 Customer Data Endpoints.
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
62 / 100
Elevated risk · MCP readiness
Agents misinterpret API operations and requests
The audit team found that agents confuse operation names, lack necessary descriptions, and encounter invalid request body formats. These issues hinder safe execution of identity API calls.
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