AI Readiness Audit
Ref. APM-9619FF5D · Confidential

EvidentID API Documentation

An independent assessment of whether the EvidentID API Documentation specification is ready for AI-assisted integration and autonomous agents, prepared for Evident.

Prepared for
Evident
Subject
EvidentID API Documentation v1.4.0-1
Scope
35 operations · 4 pillars · 3 groups
Date
October 2026
34/100
Not ready
Gaps for AI-assisted builds.
Not ready for autonomous agents.
Resolve all findings (through Phase 3) → score reaches 100 · AI-ready
Import blocked: SDK, docs, and MCP generators will refuse this spec

The validation engine found 1 blocking violation: Invalid callback key 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.

4
Critical blockers stopping entire operation groups for agents
1718
Total instances: 4 critical, 51 high, 774 medium, 889 low
62
Rule groups across 4 pillars: 4 critical, 51 high sev. instances
Executive summary

Your API documentation contains a critical blocking violation that prevents any SDK, documentation, or MCP generators from importing the spec, which is the most pressing issue we identified. The overall composite score of 34.2 out of 100 indicates that your API is not ready, with particularly low scores in standards compliance at 23.5 and documentation readiness for AI at 38.7. We found 62 rule groups with 1718 instances of findings, including 4 critical and 51 high severity issues. To move forward, addressing the blocking violation is essential for enabling any further development or automation.

Readiness by pillar
Not ready 34 / 100
FoundationThe spec itself
24/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
24Not ready
Build Time ReadinessAI writes the code
41/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
39Not ready
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
43Not ready
Runtime ReadinessAgents make the calls
38/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
38Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
34
Not ready
Phase 1fix criticals
58
Significant gaps
Phase 2+ fix highs
79
Needs work
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the EvidentID API Documentation 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 24 / 100
Active risk · Standards compliance
Spec Violations Disrupt Identity API Tools
We found critical spec violations that break toolchains and SDK generation, impacting all downstream integrations for the EvidentID API.
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 41 / 100
Active risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
The EvidentID API documentation lacks specific descriptions and examples, 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
Active risk · SDK readiness for AI
SDKs generate incorrect types and formats
The EvidentID API's ambiguous schema leads to integration code errors, risking identity verification failures.
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 38 / 100
Active risk · MCP readiness
Autonomous agents cannot execute API calls
The EvidentID API lacks essential operation identifiers and clear descriptions, preventing agents from safely executing tasks.
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