Register as a data recipient with the financial institution (FI) or data access network (e.g. Akoya, Finicity) that has adopted the FDX API standard; obtain OAuth 2.0 client credentials
Initiate the consent flow: construct an authorization request per the FDX consent model, specifying the requested data clusters (e.g. ACCOUNT_BASIC, ACCOUNT_DETAILED, TRANSACTIONS) and consent duration
Complete the OAuth 2.0 PKCE flow: redirect the user to the FI's authorization server, handle the callback, and exchange the code for tokens at the FI's token endpoint
Call the FDX-standardized endpoints: GET /fdx/v5/accounts for account list, GET /fdx/v5/accounts/{accountId} for details, and GET /fdx/v5/accounts/{accountId}/transactions with pagination parameters (offset, limit, startTime, endTime)
Honor consent lifecycle: respect the consentId returned during authorization, check consent status via GET /fdx/v5/consents/{consentId}, and cease data access when consent is revoked or expired
Known gotchas
FDX API versions vary by institution; some FIs implement FDX v4 while others implement v5 — check the FI's documentation for the supported version and schema differences before integrating
The US lacks a single central open banking mandate (as of mid-2026, CFPB Section 1033 rulemaking is ongoing); FDX adoption is voluntary and coverage across FIs is uneven
Data recipient certification and data use agreements differ by access network or FI; ensure your legal agreements permit your intended use case before building on a specific provider's FDX implementation
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp