AI Readiness AuditRef. APM-E539593C · Confidential
Virtru API
An independent assessment of whether the Virtru API specification is ready for AI-assisted integration and autonomous agents, prepared for Virtru.
67/100
Significant gaps
Gaps for AI-assisted builds.
Not ready for autonomous agents.
Not ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
67
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
215
Total instances: 0 critical, 22 high, 63 medium, 130 low
30
Rule groups across 4 pillars: 0 critical, 22 high sev. instances
Executive summary
Your API received a composite score of 67.3 out of 100, reflecting significant gaps in its readiness. The documentation readiness for AI scored 56.6, revealing substantial weaknesses that hinder effective use. Additionally, the build-time readiness shows gaps for AI-assisted builds, while runtime readiness confirms your API is not ready for autonomous agents. Addressing the documentation deficiencies should be your top priority to improve overall performance.
Readiness by pillar
Significant gaps
67 / 100
FoundationThe spec itself
71/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
71Needs work
Build Time ReadinessAI writes the code
65/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
57Significant 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
72Needs work
Runtime ReadinessAgents make the calls
68/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
68Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Virtru 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
71 / 100
Elevated risk · Standards compliance
Missing version and duplicate titles confuse integrations
You must address the missing `version` property and duplicate schema titles to ensure smooth toolchain operations.
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
65 / 100
Elevated risk · Documentation readiness for AI
AI Readers Misinterpret Sparse Documentation
You must provide detailed descriptions for all parameters; missing information leads to incorrect assumptions in the identity 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 generate incorrect types and formats
You should refine the schema layer to improve the accuracy of 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
68 / 100
Elevated risk · MCP readiness
Autonomous agents cannot execute API calls
The absence of server URLs and inadequate operation descriptions prevent agents from safely interacting with the Virtru 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