AI Readiness Audit
Ref. APM-4D24E95F · Confidential

Starling Bank API

An independent assessment of whether the Starling Bank API specification is ready for AI-assisted integration and autonomous agents, prepared for Starling Bank.

Prepared for
Starling Bank
Subject
Starling Bank API v1.0.0
Scope
87 operations · 4 pillars · 3 groups
Date
October 2026
47/100
Not ready
Functional for AI-assisted builds.
Broken for autonomous agents.
Reach AI-ready by Phase 2; resolve all findings → 100 · AI-ready
Import blocked: SDK, docs, and MCP generators will refuse this spec

The validation engine found 1 blocking violation: Unregistered HTTP security scheme detected.. Import tools reject the specification outright until it is fixed, so nothing downstream can be generated regardless of the other pillar scores. While this gate is open, the Standards Compliance score is capped at 40 and every AI pillar weights standards at 60% (normally 30%). Fixing the blocker in Phase 1 lifts the caps; the score projection below shows what that unlocks.

1
Critical blocker stopping entire operation groups for agents
2157
Total instances: 1 critical, 509 high, 783 medium, 864 low
46
Rule groups across 4 pillars: 1 critical, 509 high sev. instances
Executive summary

Your API cannot generate SDKs, documentation, or MCPs due to one blocking violation that must be resolved first. The overall composite score of 46.7 out of 100 indicates significant weaknesses, particularly in standards compliance at 40 and documentation readiness for AI at 46. While the API is functional for AI-assisted builds, it is broken for autonomous agents, with 509 high findings and 2,157 total instances across 46 rule groups. Prioritizing the resolution of the blocking violation is essential to improve your API's readiness.

Readiness by pillar
Not ready 47 / 100
FoundationThe spec itself
40/100
Standards Compliancecapped · import blocked
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
40Not ready
Build Time ReadinessAI writes the code
52/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
46Not 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
59Significant gaps
Runtime ReadinessAgents make the calls
45/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
45Not ready
Score projection · what fixing each phase unlocks
Todaycurrent score
47
Not ready
Phase 1fix criticals
62
Significant gaps
Phase 2+ fix highs
93
AI-ready
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the Starling Bank 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 40 / 100
Active risk · Standards compliance
Spec Violations Disrupt Payments API Functionality
You must address unregistered HTTP security schemes and invalid status codes to prevent toolchain failures and 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 52 / 100
Active risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
The Starling Bank API lacks sufficient parameter descriptions, leading to incorrect assumptions in payment processing.
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
The Starling Bank API's ambiguous schema leads to integration code shipping wrong types, risking payment processing errors.
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 45 / 100
Active risk · MCP readiness
Autonomous agents struggle with API execution
Autonomous agents cannot select or call the Starling Bank API due to confusing operation names and missing server URLs. This leads to significant execution failures and safety risks.
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

What's inside the full report

Unlock the full report

Book a free call to view the full report and the roadmap our team recommends to upgrade your developer and agentic experience.

Book a free call to view the full report