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

Navy Federal Credit Union

Navy Federal Credit Union is a federally chartered credit union headquartered in Vienna, Virginia, and the largest credit union in the world by both assets and membership, serving more than 14 million members across the armed forces, Department of Defense, veterans, and their families. As a not-for-profit, member-owned financial cooperative regulated by the National Credit Union Administration (NCUA), it offers deposit accounts, credit cards, auto and mortgage lending, and investment services. On the open-finance front, Navy Federal operates a genuine first-party developer program — the Navy Federal API Exchange at developer.navyfederal.org — that publishes a consumer- permissioned, open-banking-style API catalog of eight data-access products (account details, holders, statements, transactions, customer accounts, customer details, plus OAuth/API-management and an mTLS gateway-connectivity test). Access is partner-gated behind registration and a signed Data Access Agreement, secured with OAuth member consent and mutual-TLS whitelisting; no OpenAPI/Swagger is publicly downloadable pre-login. Navy Federal also exposes member-permissioned data through aggregators (Plaid, Envestnet | Yodlee via a 2021 data access agreement, Flinks) rather than solely direct first-party integration.

agent aware

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles Navy Federal Credit Union the way a machine reads it — 11 machine-readable artifacts across 8 APIs, 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 — Navy Federal Credit Union scores 31.5/100 (thin), 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 — 31.5/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 8.3 / 20
Commercial Clarity 6.8 / 20
Operational Transparency 1.4 / 13
Governance 0.0 / 12
Discoverability 8.8 / 10
Regulatory · Banking & Open Finance 10.1 / 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 Navy Federal Credit Union

Each block below is one kind of artifact we hold for Navy Federal Credit Union. 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 8

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.

Account Details API

Details and summary information for member accounts, including name, status, activity dates, balances, and more. Part of Navy Federal's consumer- permissioned Open Banking API C...

Account Holders API

Information on account ownership and member relationships for consented member accounts. Part of Navy Federal's consumer-permissioned Open Banking API Catalog.

Account Statements API

Statements for accounts over a given period, including statement names and images with details. Part of Navy Federal's consumer-permissioned Open Banking API Catalog.

Account Transactions API

Transactions for accounts over a given period, including amounts, description, running balance, status, and more. Part of Navy Federal's consumer-permissioned Open Banking API C...

API Management API

Client registration and OAuth authentication management used to onboard third parties and obtain member consent tokens for the Open Banking API Catalog.

Customer Accounts API

Listing of consented member accounts with basic details. Part of Navy Federal's consumer-permissioned Open Banking API Catalog.

Customer Details API

Member information independent of accounts, including name, address, date of birth, IDs, and other personal information. Part of Navy Federal's consumer-permissioned Open Bankin...

Gateway Connectivity API

Connection test to the API platform providing a basic message response, used to prove out a working request over mTLS with whitelisting. Part of Navy Federal's Open Banking API ...

Scroll within the panel for all 8 ·

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.

Navy Federal Credit Union Authentication

oauth2/mutualTLS · 2 schemes

SECURITY

Navy Federal Credit Union Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Navy Federal Credit Union Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Every other property we hold for Navy Federal Credit Union — 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 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Operate 2

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/navy-federal-credit-union · machine-readable index on apis.io