Financial Data Exchange (FDX)
Financial Data Exchange (FDX) is a non-profit industry standards body operating in the US and Canada that produces the FDX API, a royalty-free REST standard for consumer-permissioned financial data sharing. The FDX API defines interoperable endpoints covering deposit accounts, loan accounts, investment accounts, insurance policies, tax data, payroll data, reward programs, and consent management, enabling data providers (financial institutions), data access platforms (aggregators), and data recipients (fintechs) to exchange consumer financial data without exposing user credentials. As of early 2026 over 130 million consumer accounts are connected via the FDX API across 200+ member organizations including Bank of America, Chase, Citi, Wells Fargo, Plaid, and MX. FDX API v6.5 is the current stable release.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Financial Data Exchange (FDX) the way a machine reads it — 105 machine-readable artifacts across 12 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 — Financial Data Exchange (FDX) scores 57.1/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Financial Data Exchange (FDX)
Each block below is one kind of artifact we hold for Financial Data Exchange (FDX). 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 12
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.
FDX Transactions API
RESTful endpoints for retrieving consumer transaction histories including pending and posted transactions, transaction categorization, merchant data, and transaction amounts acr...
FDX Investment API
RESTful endpoints for retrieving investment account data including holdings, positions, investment transactions, cost basis, and portfolio composition. Covers brokerage, retirem...
FDX Insurance API
RESTful endpoints for retrieving insurance policy information including policy coverage details, premium schedules, claims history, and beneficiary data under the FDX insurance ...
FDX Tax API
RESTful endpoints for retrieving consumer tax data including tax document metadata and structured tax form data (1099s, W-2s, and related forms) as defined by the FDX US Tax Dat...
FDX Payroll API
RESTful endpoints introduced in FDX API v6.0 for retrieving permissioned payroll data including employment records, pay stubs, income verification, and direct deposit details, s...
FDX Consent API
RESTful endpoints implementing the FDX Consent API Behavioral Specification for managing user permissions and consent events. Enables data recipients to initiate consent, query ...
Financial Data Exchange (FDX) Account Information API
Search and view customer accounts
Financial Data Exchange (FDX) Account Statements API
Search and retrieve account statements
Financial Data Exchange (FDX) Account Transactions API
Search and view account transactions
Financial Data Exchange (FDX) Asset Transfer Networks Information API
Search and view asset transfer networks networks
Financial Data Exchange (FDX) Payment Networks Information API
Search and view account payment networks
Financial Data Exchange (FDX) Personal Information API
Search and view customer or customers
Scroll within the panel for all 12 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Fdx Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Fdx Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Fdx Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Fdx Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 83
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Account Category type
JSON SCHEMAAccount Contact entity
JSON SCHEMAAccount Descriptor entity
JSON SCHEMAAccount Holder entity
JSON SCHEMAAccount Holder Relationship
JSON SCHEMAPayment Networks entity
JSON SCHEMAAccounts entity
JSON SCHEMAAccount Status
JSON SCHEMAAccount entity
JSON SCHEMAAccount With Details entity
JSON SCHEMAAddress
JSON SCHEMAAnnuityAccountDescriptor
JSON SCHEMAAnnuityAccountType
JSON SCHEMAAsset Transfer Network
JSON SCHEMAAsset Transfer Networks
JSON SCHEMAAsset Transfer Type
JSON SCHEMACommercialAccountDescriptor
JSON SCHEMACommercialAccountType
JSON SCHEMAContent Types
JSON SCHEMACurrency entity
JSON SCHEMACustomer entity.
JSON SCHEMACustomer Name entity
JSON SCHEMACustomer entity
JSON SCHEMADate String
JSON SCHEMADebitCreditMemo
JSON SCHEMADelivery Address
JSON SCHEMADelivery Address Type
JSON SCHEMADeposit Account Details entity
JSON SCHEMADepositAccountDescriptor
JSON SCHEMADepositAccountType
JSON SCHEMADeposit Transaction entity
JSON SCHEMADigitalWalletDescriptor
JSON SCHEMADigitalWalletType
JSON SCHEMAFI Attribute entity
JSON SCHEMAHATEOAS Link
JSON SCHEMAHATEOAS links array
JSON SCHEMAHolding entity
JSON SCHEMAHolding SubType
JSON SCHEMAHolding Type
JSON SCHEMAHTTP action type
JSON SCHEMAIdentifier
JSON SCHEMAIndividual name
JSON SCHEMAInsuranceAccountDescriptor
JSON SCHEMAInsuranceAccountType
JSON SCHEMAInterest Rate Type
JSON SCHEMAInvestmentAccount
JSON SCHEMAInvestmentAccountDescriptor
JSON SCHEMAInvestmentAccountType
JSON SCHEMAInvestment Transaction entity
JSON SCHEMAInvestment Transaction Type
JSON SCHEMAISO 3166 Country Code
JSON SCHEMAISO 4217 Code
JSON SCHEMALineOfCreditAccount
JSON SCHEMALineOfCreditAccountDescriptor
JSON SCHEMALineOfCreditAccountType
JSON SCHEMALine-Of-Credit Transaction entity
JSON SCHEMALine-Of-Credit Transaction Type
JSON SCHEMALoan Account entity
JSON SCHEMALoanAccountDescriptor
JSON SCHEMALoanAccountType
JSON SCHEMALoan Transaction entity
JSON SCHEMALoan Transaction Type
JSON SCHEMAPage Metadata
JSON SCHEMAPaginated Array
JSON SCHEMAPayment Network Supported by Account
JSON SCHEMAPayment Network Identifier Type
JSON SCHEMAPayment Network Type
JSON SCHEMASecurity ID entity
JSON SCHEMASecurity ID Type
JSON SCHEMASecurity Type
JSON SCHEMAStatement entity
JSON SCHEMAStatement PDF
JSON SCHEMAStatements entity
JSON SCHEMAString 255
JSON SCHEMAString 64
JSON SCHEMATelephone Network
JSON SCHEMATelephone Number
JSON SCHEMATelephone Number Purpose
JSON SCHEMATimestamp
JSON SCHEMATransaction
JSON SCHEMATransactions entity
JSON SCHEMATransaction Status
JSON SCHEMAUnit Type
JSON SCHEMAScroll within the panel for all 83 ·
Security Posture 2
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Financial Data Exchange (FDX) — 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 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/fdx · machine-readable index on apis.io