AI Readiness AuditRef. APM-41556708 · Confidential
Nova Credit Passport® API
An independent assessment of whether the Nova Credit Passport® API specification is ready for AI-assisted integration and autonomous agents, prepared for Nova Credit.
64/100
Significant gaps
Gaps for AI-assisted builds.
Partially ready for autonomous agents.
Partially ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
64
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
443
Total instances: 0 critical, 40 high, 177 medium, 226 low
31
Rule groups across 4 pillars: 0 critical, 40 high sev. instances
Executive summary
Your Nova Credit Passport® API scored 63.5 out of 100, reflecting significant gaps in standards compliance and documentation readiness for AI. The API received a score of 58.1 for standards compliance and 51.9 for documentation readiness, which are both below acceptable levels. While the SDK readiness for AI scored 80.3, the overall build-time readiness shows gaps for AI-assisted builds. To improve your API's effectiveness, prioritize addressing the documentation readiness issues.
Readiness by pillar
Significant gaps
64 / 100
FoundationThe spec itself
58/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
58Significant gaps
Build Time ReadinessAI writes the code
66/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
52Not 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
80Mostly ready
Runtime ReadinessAgents make the calls
67/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
67Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Nova Credit Passport® 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
Where you’re exposed – and where you’re not
4 failure modes across 3 groups. Some are active risks; others are under control.
Foundation
The spec itself
58 / 100
Elevated risk · Standards compliance
Fix Spec Violations to Prevent Breaks
You must address invalid HTTP status codes and undefined schema properties to prevent toolchain failures in the payments 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
66 / 100
Active risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
The Nova Credit Passport® API lacks sufficient parameter descriptions and operation details, leading to incorrect assumptions.
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 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
67 / 100
Elevated risk · MCP readiness
Agents cannot execute API operations safely
The Nova Credit Passport API lacks essential content in operation descriptions and does not support JSON media types, which confuses agents and risks payment processing.
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