AI Readiness AuditRef. APM-D395058C · Confidential
Trulioo Platform API
An independent assessment of whether the Trulioo Platform API specification is ready for AI-assisted integration and autonomous agents, prepared for Trulioo.
63/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
63
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
912
Total instances: 0 critical, 27 high, 275 medium, 610 low
40
Rule groups across 4 pillars: 0 critical, 27 high sev. instances
Executive summary
Your API scores 62.9 out of 100, reflecting significant gaps across multiple areas. Standards compliance scored 64.7, while documentation readiness for AI and SDK readiness for AI scored 58.3 and 63.3, respectively. You have 27 high findings among a total of 40 rule groups and 912 instances, revealing weaknesses that hinder AI-assisted builds and prevent autonomous agents from functioning effectively. Addressing the documentation readiness for AI is the single most important action for improvement.
Readiness by pillar
Significant gaps
63 / 100
FoundationThe spec itself
65/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
65Significant gaps
Build Time ReadinessAI writes the code
61/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
63Significant gaps
Runtime ReadinessAgents make the calls
64/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
64Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Trulioo Platform 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
65 / 100
Elevated risk · Standards compliance
Spec Violations Disrupt Identity Integrations
You must address three high-severity spec violations that break toolchains and SDK generation for the Trulioo Platform 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
61 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API due to documentation gaps
You risk coding assistants building on incorrect assumptions because parameter descriptions are often missing or too brief.
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 must address ambiguous schema definitions to prevent integration failures in identity services.
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
64 / 100
Elevated risk · MCP readiness
Autonomous Agents Fail to Execute API
The Trulioo Platform API's request body schema lacks an object root, preventing agents from safely executing identity operations.
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