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
Alkami website screenshot

Alkami

Alkami Technology (NASDAQ: ALKT) is a Plano, Texas based cloud digital banking platform for U.S. banks and credit unions. Through its "Alkami Foundry" developer program it exposes RESTful APIs and an extensible SDK — spanning authentication, money movement, data access, and real-time and batch workflows — that financial institutions and fintech partners use to embed and extend digital-banking experiences. The APIs are grouped into D2C (embed fintech experiences), B2B (automate backend workflows), and Open Banking (third-party connections such as Plaid) surfaces, are built on OpenID Connect, and are delivered through a gated DevPortal rather than an open public API. Alkami was surfaced as a portfolio company of D1 Capital and enriched by the API Evangelist pipeline from its public developer, security, and legal surfaces.

agent aware

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 Alkami the way a machine reads it — 4 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 — Alkami scores 24.5/100 (emerging), with a separate agent-readiness read of 16/100 (agent aware). 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 — 24.5/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 7.0 / 20
Commercial Clarity 2.1 / 20
Operational Transparency 2.1 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Regulatory · Banking & Open Finance 7.2 / 15
Agent readiness — 16/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 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 4 / 4
Consent & Bot Identity 3 / 3

How we profile Alkami

Each block below is one kind of artifact we hold for Alkami. 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.

Alkami Digital Banking API

Alkami's RESTful digital-banking APIs (D2C, B2B, and Open Banking) plus the Alkami SDK, built on OpenID Connect and documented in the gated Alkami DevPortal.

Security Posture 3

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.

Alkami Authentication

openIdConnect · 1 scheme

SECURITY

Alkami Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Alkami Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Resources

Every other property we hold for Alkami — 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 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Build 1

SDKs, sample code, and the tooling you integrate with

Operate 1

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

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