AI Readiness AuditRef. APM-A1507F56 · Confidential
FutureBank.Web.Bff Api
An independent assessment of whether the FutureBank.Web.Bff Api specification is ready for AI-assisted integration and autonomous agents, prepared for FutureBank.
59/100
Significant gaps
Functional 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
59
055708085100
F · Not readyD · Significant gapsC · Needs workB · Mostly readyA · AI-ready
0
Critical blockers : no findings stop an operation group outright
2446
Total instances: 0 critical, 516 high, 851 medium, 1079 low
50
Rule groups across 4 pillars: 0 critical, 516 high sev. instances
Executive summary
Your API, FutureBank.Web.Bff Api, scores 58.5 out of 100, reflecting significant gaps across several areas. Standards compliance and documentation readiness for AI both fall short, with scores of 56.7 and 51.7 respectively, while SDK readiness for AI stands at 80.3, showing it is mostly ready. Agents cannot make autonomous calls, as runtime readiness is broken, which requires immediate attention. Addressing the documentation readiness will be the most impactful step to improve your API's overall performance.
Readiness by pillar
Significant gaps
59 / 100
FoundationThe spec itself
57/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
57Significant 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
46/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
46Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
Phase 1fix highs
Phase 2+ fix mediums & lows
About this report. We evaluated the FutureBank.Web.Bff 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
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
57 / 100
Elevated risk · Standards compliance
Fix Specification Violations to Prevent Breaks
You must address multiple specification violations that disrupt toolchains, SDK generation, and downstream integrations in payments.
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
You must provide detailed descriptions for parameters and operations; otherwise, AI readers build on 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
We found that the success response lacks a body schema, which may lead to integration issues.
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
46 / 100
Active risk · MCP readiness
Autonomous agents cannot execute API calls
The FutureBank.Web.Bff API lacks essential identifiers and clear server URLs, preventing safe operation execution.
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