AI Readiness AuditRef. APM-C6F07037 · Confidential
Account and Transaction API Specification
An independent assessment of whether the Account and Transaction API Specification specification is ready for AI-assisted integration and autonomous agents, prepared for Capital on Tap.
75/100
Needs work
Functional for AI-assisted builds.
Ready for autonomous agents.
Ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
F
D
C
B
A
75
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
37223
Total instances: 0 critical, 6212 high, 4256 medium, 26755 low
32
Rule groups across 4 pillars: 0 critical, 6212 high sev. instances
Executive summary
Account and Transaction API Specification scores 74.9/100: Needs work · Grade C. The weakest pillar is Documentation readiness for AI at 61; the strongest is SDK readiness for AI at 88. We recorded 37223 finding instances: 0 critical, 6212 high, 4256 medium, and 26755 low. Functional for AI-assisted builds. Ready for autonomous agents. Every finding lives in the specification, and the roadmap in this report orders the fixes by impact; resolving them projects the score to 100/100.
Readiness by pillar
Needs work
75 / 100
FoundationThe spec itself
73/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
73Needs work
Build Time ReadinessAI writes the code
74/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
61Significant 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
88AI-ready
Runtime ReadinessAgents make the calls
79/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
79Needs work
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the Account and Transaction API Specification 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
73 / 100
Elevated risk · Standards compliance
Your spec breaks before code is even written
1 critical/high finding group(s) in this area. Score: 73/100.
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
74 / 100
Elevated risk · Documentation readiness for AI
AI readers can't learn the truth of your API
1 critical/high finding group(s) in this area. Score: 61/100.
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
Your schemas support trustworthy generated code
No critical or high findings; 3 medium finding group(s) remain. Score: 88/100.
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
79 / 100
Elevated risk · MCP readiness
Autonomous agents can't safely operate your API
1 critical/high finding group(s) in this area. Score: 79/100.
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