Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

UMB Bank

UMB Bank, National Association is the primary banking subsidiary of UMB Financial Corporation (Nasdaq ticker UMBF), a Kansas City, Missouri financial services holding company. UMB is a commercial bank operating under a national (federal) bank charter supervised by the Office of the Comptroller of the Currency (OCC), with roughly $70 billion in assets following its 2025 acquisition of Heartland Financial and branches across the central United States. It offers personal, commercial, and institutional banking, including asset servicing, corporate trust, and healthcare (HSA) services. UMB runs a partner-facing open-banking and Banking-as-a-Service (BaaS) program through its Institutional & Fintech Banking group, exposing REST APIs across risk & compliance, customer onboarding, accounts, information (statements/check images), and cash management. Access is partner-gated through a consultation and contracting process — there is no public self-serve developer portal, no publicly downloadable OpenAPI/Swagger specification, and no published FDX or CFPB 1033 posture. Consumer-permissioned account data is reached primarily through the Plaid aggregator rather than a first-party public API.

human only

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles UMB Bank the way a machine reads it — 2 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — UMB Bank scores 21.6/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 21.6/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 5.2 / 20
Commercial Clarity 6.8 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 8.0 / 10
Regulatory · Banking & Open Finance 4.6 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile UMB Bank

Each block below is one kind of artifact we hold for UMB Bank. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 1

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

UMB Banking APIs (Open Banking / BaaS)

UMB's partner-facing open-banking and Banking-as-a-Service REST API program, documented across five areas — Risk & Compliance (retrieve questions required for new customer appli...

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Umb Financial Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for UMB Bank — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Access & Security 1

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/umb-financial · machine-readable index on apis.io