Finicity Open Finance
65
AI ReadinessAI-Aware (B)65/100
Official vendor OpenAPI document · agent-readyFinanceBankingapiKey148 EndpointsREST
For 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.
Use for: I need to retrieve a customer's bank account transactions, Add a new customer to aggregate their accounts, Generate a Data Connect URL for account linking, Get a customer's account balances
Not supported: Does not handle card issuing, lending decisions, or merchant checkout. Use for bank account aggregation, transactions, and verification reports only.
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.
Install Jentic One Beta
Connect the Open Finance to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Open Finance, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffinicity.com%2Ffinicity" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffinicity.com%2Ffinicity" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Open Finance API.
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
Patterns agents use Open Finance API for, with concrete tasks.
★ 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.
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.
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.
Generate a Verification of Assets report for a customer and confirm the report is produced
Key Endpoints
148 endpoints — the finicity open finance api aggregates us bank, loan, and investment account data and the financial verifications built on top of it.
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
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
Jentic AI Readiness Score
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.
O
Open Finance
- AI-Aware (B)65/100
74
Foundational Compliance77
Developer Experience & Jentic Compatibility60
AI-Readiness & Agent Experience68
Agent Usability50
Security71
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
82%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
14%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
77
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
67%
Example Density
How richly the API is illustrated with examples.
91%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
60
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: B-Signals: 4
73%
Description Coverage
Coverage of descriptions across API elements.
65%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
80%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
22%
Summary Coverage
Coverage of summaries across operations/tags/info.
68
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: B+Signals: 1
68%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
71
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
71%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Open Finance API through Jentic.
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.
GET STARTED