AI Readiness AuditRef. APM-AB76B2DC · Confidential
RDE UI API
An independent assessment of whether the RDE UI API specification is ready for AI-assisted integration and autonomous agents, prepared for Fundbox.
75/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
75
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
352
Total instances: 0 critical, 63 high, 157 medium, 132 low
27
Rule groups across 4 pillars: 0 critical, 63 high sev. instances
Executive summary
Your RDE UI API for payments scores 74.7 out of 100, reflecting solid standards compliance at 90.2 but significant gaps in documentation readiness for AI at 67.7 and MCP readiness at 59.1. Agents encounter 63 high findings across 27 rule groups, with a total of 352 instances needing attention. AI-assisted builds face gaps, and autonomous agents cannot effectively make calls. Addressing the documentation and MCP readiness will improve your API's overall functionality.
Readiness by pillar
Needs work
75 / 100
FoundationThe spec itself
90/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
90AI-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
68Significant 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
74Needs work
Runtime ReadinessAgents make the calls
59/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
59Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the RDE UI 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
90 / 100
Managed · Standards compliance
Missing operation IDs affect integrations
You should address the missing `operationId` in the operation object to prevent downstream integration issues.
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
Sparse and generic documentation leads to incorrect assumptions in the payments API, risking functionality.
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 return incorrect types and formats
You should clarify the success response schema to ensure accurate integration with the payments API.
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
59 / 100
Elevated risk · MCP readiness
MCP Tools Fail to Execute Properly
Autonomous agents cannot select or call the RDE UI API due to missing operation identifiers and server URLs, risking 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