canonical: https://jentic.com/apis/finicity.com/finicity # Finicity Open Finance The Finicity Open Finance API aggregates US bank, loan, and investment account data and the financial verifications built on top of it. It onboards customers, links their accounts through a Data Connect flow, and returns account details, balances, and historical and recent transactions. It also produces Verification of Assets, Income, and Employment reports and looks up certified financial institutions. Open Finance is provided by Finicity, a Mastercard company. ## For AI agents Aggregate US bank accounts, balances, and transactions, generate account-linking Data Connect URLs, and produce Verification of Assets, Income, and Employment reports. Open Finance from Finicity, a Mastercard company. ## Scope Does not handle card issuing, lending decisions, or merchant checkout. Use for bank account aggregation, transactions, and verification reports only. ## Capabilities - Onboard customers whose financial accounts you aggregate - Retrieve a customer's bank accounts, balances, and account details - Pull historical and recent transactions for a customer account - Generate a Data Connect URL so a customer can link their accounts - Produce Verification of Assets, Income, and Employment reports - Look up certified financial institutions by name or routing number ## Use cases ### Agent-Driven Account Linking An AI agent connected through Jentic onboards a customer and generates a Data Connect URL so the customer can link their bank accounts, then reads back the linked accounts once the flow completes. This turns the multi-step aggregation setup into a guided sequence the agent runs for each new customer. Example prompt: Add a customer, generate a Data Connect URL for them, and list the accounts linked to that customer once connected ### Transaction Retrieval A personal-finance or underwriting workflow pulls a customer's historical and recent transactions for a linked account to build a spending or cash-flow picture. The transactions come straight from the aggregated accounts, so the workflow reads a consistent record rather than scraping statements. Example prompt: Retrieve recent transactions for a customer account and summarize income and spending over the period ### Income and Asset Verification A lending workflow generates a Verification of Assets or Verification of Income and Employment report from a customer's linked accounts to support a credit decision. The decisioning endpoints produce the report directly from the aggregated data, so the workflow does not assemble it from raw transactions by hand. Example prompt: Generate a Verification of Assets report for a customer and confirm the report is produced ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/aggregation/v2/customers/active` | Add a customer | | GET | `/aggregation/v1/customers` | List customers | | GET | `/aggregation/v2/customers/{customerId}/accounts/{accountId}` | Get a customer account | | GET | `/aggregation/v3/customers/{customerId}/transactions` | Get customer transactions | | POST | `/connect/v2/generate` | Generate a Data Connect URL | | POST | `/decisioning/v2/customers/{customerId}/voa` | Generate a Verification of Assets report | | POST | `/aggregation/v2/partners/authentication` | Create an access token | ## Key resources - **Customers** — Add, list, and read the customers whose accounts you aggregate - **Accounts and Transactions** — Read account details, balances, and historical and recent transactions - **Connect** — Generate Data Connect URLs for customers to link their accounts - **Decisioning Reports** — Produce Verification of Assets, Income, and Employment reports ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 65 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 74 / 100 - Developer Experience & Jentic Compatibility: 77 / 100 - AI-Readiness & Agent Experience: 60 / 100 - Agent Usability: 68 / 100 - Security: 50 / 100 - AI Discoverability: 71 / 100 - **View full report:** https://jentic.com/apis/finicity.com/finicity/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Finicity Open Finance API by hand means sending both the Finicity-App-Key and Finicity-App-Token headers, minting the app token through the partner authentication endpoint and refreshing it, and generating a Data Connect URL for each customer link. Through Jentic you install once, import Finicity from the API Directory, store the credentials once, and your agent calls it. - **Permission scoping:** Finicity puts the customer id in the URL path (`/aggregation/v1/customers/{customerId}/...`), so a rule can pin your agent to one customer and the operations you pick, such as reading accounts and transactions. You choose the operations it may call, so deleting a customer's account access is not included unless you add it. - **Credential handling:** Your Finicity app key and app token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get a customer's transactions' or 'generate an account-linking URL', and Jentic returns the matching Finicity operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Plaid API** — A competing US account-aggregation and open-finance platform with a similar link-and-read model to Finicity. - **MX API** — Another financial data aggregation and enrichment platform covering accounts and transactions. - **TrueLayer API** — Open banking data and payments focused on the UK and Europe, where Finicity centers on the US. ## FAQ ### What authentication does the Finicity Open Finance API use? The Finicity Open Finance API authenticates with two header credentials per its OpenAPI spec: a Finicity-App-Key and a Finicity-App-Token, where the app token is minted through the partner authentication endpoint. Through Jentic both are stored encrypted by your own Jentic One instance and injected at call time, so they never reach the agent's context. ### Can I retrieve a customer's transactions with the Finicity Open Finance API? Yes. Once a customer links their accounts through Data Connect, you can read historical and recent transactions for a linked account, along with account details and balances. The transactions come directly from the aggregated account rather than from scraped statements. ### Can I limit what my agent is allowed to do with the Finicity Open Finance API? Yes. Finicity puts the customer id in the URL path, so write a rule that allows only the read operations for the customers you pick, such as reading accounts and transactions, so your agent cannot delete account access or move money, and every call it makes is logged. Add the Data Connect and report operations when you want the agent to onboard customers or run verifications. ### What are the rate limits for the Finicity Open Finance API? The OpenAPI spec does not state numeric rate limits for the Finicity Open Finance API. Check the Finicity developer documentation for the limits that apply to your partner account. ### How do I get a customer's bank transactions with the Finicity Open Finance API through Jentic? Search Jentic for 'get a customer's bank transactions' and it returns the transactions operation with its input schema; your agent supplies the customer id and reads back the transactions once the accounts are linked. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Is there a Finicity MCP server? You don't need an MCP server to give your agent the Finicity Open Finance API. Jentic connects it directly from the API Directory: import it, store your credentials once, and your agent calls the aggregation, transaction, and verification operations with scoping and credential isolation applied.