AI Readiness AuditRef. APM-44C9867A · Confidential
Verified Inc. API
An independent assessment of whether the Verified Inc. API specification is ready for AI-assisted integration and autonomous agents, prepared for Verified.
73/100
Needs work
Gaps 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
73
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
2079
Total instances: 0 critical, 22 high, 1122 medium, 935 low
37
Rule groups across 4 pillars: 0 critical, 22 high sev. instances
Executive summary
Your API scored 72.6 out of 100, reflecting a need for improvement. The API meets standards compliance with a score of 86, but documentation readiness for AI shows significant gaps at 61.7. SDK readiness is mostly ready at 80.1, while MCP readiness falls short at 56.1. Focus on addressing the documentation and MCP gaps to improve AI-assisted builds and restore functionality for autonomous agents.
Readiness by pillar
Needs work
73 / 100
FoundationThe spec itself
86/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
86AI-ready
Build Time ReadinessAI writes the code
71/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
62Significant 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
80Mostly ready
Runtime ReadinessAgents make the calls
56/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
56Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Verified Inc. 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
86 / 100
Managed · Standards compliance
Address Undefined Variables in Server URL
We found undefined variables in the server URL, which can disrupt SDK generation and downstream integrations. You should define all variables to ensure compliance and functionality.
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
71 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
The missing parameter object descriptions lead to incorrect assumptions, risking payment processing errors.
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
Managed · 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
56 / 100
Elevated risk · MCP readiness
Autonomous agents struggle with API execution
The lack of labeled sandbox servers and confusable operations prevents agents from safely executing payment transactions.
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