Best of · Domain data
Best open banking and bank data APIs for AI agents
The 10 highest-scoring of 15 open banking and bank data APIs on the Anchor benchmark, with a pick for each need and where each one falls short. Scores come from public evidence, re-checked as vendors change.
- 15 ranked
- 0 agent-ready
- 13 hosted endpoints
- Updated 9 October 2026
Top three
Picks by need
Worked out from the scores, prices and facts, so they change when the research does.
The shortlist
| # | Tool | Grade | Best for | Price | Where |
|---|---|---|---|---|---|
| 1 | Plaid Plaid |
B 69.8 | US and Canadian account, transaction, identity and income data, with Transfer for payments. | Paid | hosted and local |
| 2 | Belvo Belvo |
B 63.5 | Lenders and fintechs that need consented bank data in Brazil, employment or tax records in Mexico, or Pix and direct debit collection, and can sign a contract. | $1000 / mo | hosted |
| 3 | MX Platform API MX Technologies, Inc. |
B 62.5 | A US or Canadian bank, credit union or fintech with a signed MX contract that wants aggregation, verification and categorised transactions plus embeddable finance widgets. | Paid | hosted |
| 4 | Tink Tink AB (Visa) |
B 62.5 | A company with a contract that needs account, balance and transaction data or bank payments across European markets under Tink's own licences. | Paid | hosted |
| 5 | TrueLayer TrueLayer |
B 62.1 | UK data and payments from one licensed vendor, with EEA coverage through the Irish entity on Data v1. | Paid | hosted |
| 6 | Basiq Basiq Pty Ltd (Cuscal Limited) |
C 60.4 | Consented bank data for Australia and New Zealand, with income and affordability reports for lenders. | Paid | hosted |
| 7 | Yapily Yapily |
C 57.6 | UK and EEA data and payments from one API, for builders who want docs an agent can read in one fetch. | Paid | hosted |
| 8 | Flinks Flinks Technology Inc. (National Bank of Canada) |
D 52.7 | A lender or fintech with steady volume that needs Canadian bank data, income and lending attributes, PDF statements or Canadian bank payments. | Paid | local |
| 9 | Akoya Akoya LLC |
D 48.3 | A US fintech that wants consumer-permissioned data over direct institution APIs in FDX format and can pass a security review. | Paid | hosted |
| 10 | Enable Banking Enable Banking |
D 47.1 | EU account data and payments for builders who want live data before signing anything, or agents that read their operator's own accounts. | Paid | hosted |
5 more are ranked in the full table.
How to choose
- Country and bank coverageCheck which countries and institutions the connection covers, since an agent serving a market the service does not reach will have no accounts to read.
- Consent flow and revocationCheck how consent is granted and what revocation does to stored data, since an agent must stop reading an account when the person withdraws access.
- Data freshness and categoriesCheck how often transactions refresh and how well they are categorised, since an agent summarising spending depends on both being current and accurate.
- Price per connectionCompare the price per connection and what counts as one, since an agent that reconnects a user often can cost far more than the headline rate suggests.
How the benchmark tests this category. A sandbox user connects an account, the agent reads balances and categorised transactions, and the consent is revoked. We check coverage, the consent flow, data quality and what revocation does.
Each one in detail
Plaid
B 69.8/100Bank data aggregation platform covering the US, Canada, the UK and parts of Europe.
Verdict Public OpenAPI file, llms.txt with about 250 entries and a Markdown twin of every docs page. No prices before a Production application, and Transactions, Liabilities and Investments bill per Item each month until removed.
Choose it for US and Canadian account, transaction, identity and income data, with Transfer for payments.
Strengths
- Public OpenAPI file, llms.txt with about 250 entries and a Markdown twin of every docs page
- Rate limits per endpoint, per Item and per client, published as JSON
- Error bodies carry error_code, documentation_url and suggested_action
Weaknesses
- No prices before a Production application, and Transactions, Liabilities and Investments bill per Item each month until removed
- Four plaid-node major versions between 23 July and 1 September 2026, each with breaking changes
- No Retry-After on 429 and no list of which error codes are safe to retry
Price PaidAuth OAuth or keyx402 nohosted and local
Belvo
B 63.5/100Belvo is an open finance API for Latin America. It reads bank accounts, transactions and investments in Brazil, employment records in Brazil and Mexico and tax data in Mexico, and starts Pix payments in Brazil and direct debits in Mexico.
Verdict Belvo publishes a 146-operation OpenAPI file, an llms.txt with a Markdown twin of each docs page, and list endpoints with field selection and pages of up to 1,000. Production access needs a sales meeting, a certification call and a paid plan from 1,000 USD a month, and no changelog or maintained SDK was found.
Choose it for Lenders and fintechs that need consented bank data in Brazil, employment or tax records in Mexico, or Pix and direct debit collection, and can sign a contract.
Strengths
- Public OpenAPI 3.0.2 file, version 1.223.0, with 146 operations on 83 paths, and a separate specification for Direct Debit in Mexico
- llms.txt lists a Markdown twin of every docs page in English, Spanish and Portuguese
- List endpoints take
fields,omit,page_sizeup to 1,000 and range filters on dates and amounts
Weaknesses
- Production keys follow a sales meeting, a certification call with a Belvo engineer and a paid plan from 1,000 USD a month
- One
secretIdandsecretPasswordpair per environment over HTTP Basic, with no scopes or read-only keys found - No changelog was found, and the Python, Node and Ruby packages were last published in 2023 with their GitHub repositories returning 404
Price $1000 / moAuth API keyx402 nohosted
MX Platform API
B 62.5/100MX Technologies' Platform API connects US and Canadian bank accounts for account aggregation, balance checks, account and owner verification and up to 24 months of categorised transactions, through REST endpoints or the embedded Connect Widget.
Verdict Three public OpenAPI files, llms.txt, Markdown docs and a written version policy with 18 months of support and Deprecation and Sunset response headers. No price, client agreement or SLA is published, production keys need MX's approval, every calling IP address must be allowlisted, and the status page records three platform-wide error incidents since 10 July 2026.
Choose it for A US or Canadian bank, credit union or fintech with a signed MX contract that wants aggregation, verification and categorised transactions plus embeddable finance widgets.
Strengths
- OpenAPI files for all three Platform API versions, an llms.txt index and a Markdown twin of every docs page
- Each version is supported for at least 18 months, then deprecated for 12, and deprecated endpoints send
Deprecation,SunsetandLinkheaders - Rate limits are published per method, 2,000 GET and 750 POST requests a second in production
Weaknesses
- No public price, SLA or client agreement. Production keys are requested from MX in the Client Dashboard
- Three platform-wide incidents of elevated errors since 10 July 2026 (42, 89 and 37 minutes), marked critical or major
- One
client_idandapi_keypair reaches every endpoint, with no scopes and no read-only key
Price PaidAuth API keyx402 nohosted
Tink
B 62.5/100Tink is a European open banking platform owned by Visa. Its REST API and hosted Tink Link flow read accounts, balances and transactions with the account holder's consent, and start bank payments.
Verdict OAuth client credentials with per-endpoint scopes, token-paged data endpoints and a published MSA, DPA, SLA and sub-processor list. No price is public, live access needs a sales contract, and the API reference has no downloadable spec or published rate-limit numbers.
Choose it for A company with a contract that needs account, balance and transaction data or bank payments across European markets under Tink's own licences.
Strengths
- OAuth 2.0 client credentials with named scopes per endpoint, 30-minute client tokens and two-hour user tokens
- Master Service Agreement, DPA, four SLA documents and a sub-processor list with processing locations are public PDFs
- Data v2 list endpoints page with
pageSizeandpageToken, with date, account and status filters on transactions
Weaknesses
- No public prices. The pricing page lists Standard as Contact us and Enterprise as Custom pricing, and the FAQ says there is no pay-per-use option
- The API reference is a JavaScript app with the Swagger definitions inside its bundle. No downloadable spec was found
- Rate limits are per app with no published numbers, and a 429 carries no documented Retry-After
Price PaidAuth OAuthx402 nohosted
TrueLayer
B 62.1/100UK and EU open banking, regulated by the FCA and the Central Bank of Ireland.
Verdict FCA and Central Bank of Ireland authorised, holding the AISP and PISP licences itself. No public pricing anywhere on the site or in the docs.
Choose it for UK data and payments from one licensed vendor, with EEA coverage through the Irish entity on Data v1.
Strengths
- FCA and Central Bank of Ireland authorised, holding the AISP and PISP licences itself
- Data API errors list 23 codes, each marked retryable or not
- Markdown twin of every docs page, llms.txt with about 280 entries and per-API OpenAPI files
Weaknesses
- No public pricing anywhere on the site or in the docs
- Data API v3 is UK only; Europe runs on Data API v1 with a different flow
- security.txt expired on 6 May 2026 and hadn't been renewed by 1 October
Price PaidAuth OAuthx402 nohosted
Basiq
C 60.4/100Basiq is an Australian open banking platform owned by Cuscal Limited. Its REST API reads accounts, transactions and identity details from Australian and New Zealand institutions with the holder's consent, and builds income, expense and affordability reports.
Verdict Ten public OpenAPI files, an llms.txt index with Markdown twins and a free self-serve sandbox let an agent start on test data. Live access needs a 12-month plan with an unpublished platform access fee, no SLA or security.txt was found, and the privacy policy says collected content may be kept indefinitely.
Choose it for Consented bank data for Australia and New Zealand, with income and affordability reports for lenders.
Strengths
- Ten OpenAPI 3.0 files are public in the
basiqio-oss/Basiq-docsrepository, 73 operations in all, and every reference page has a Markdown twin listed in llms.txt - The sandbox is free and self-serve from the dashboard, with a test bank named Hooli and an Open Banking flow that covers authorise, extend, refresh and revoke
- API keys are created, named and revoked in the dashboard, permission sets limit a key to chosen endpoints, and access tokens expire after 60 minutes
Weaknesses
- Live data needs a plan with a 12-month minimum and a platform access fee whose amount is not published
- No SLA was found, and the Terms of Service say Basiq does not warrant uninterrupted service
- The privacy policy says collected content may be retained indefinitely after an account ends, while the docs security page says data is deleted at once
Price PaidAuth API keyx402 nohosted
Yapily
C 57.6/100UK and EU open banking API with account information and payments across 2,000-plus banks, licensed in the UK (FCA) and Lithuania.
Verdict llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file. No public pricing; live access starts with a sales form.
Choose it for UK and EEA data and payments from one API, for builders who want docs an agent can read in one fetch.
Strengths
- llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file
- Error bodies carry a source of USER, INSTITUTION or YAPILY and a tracingId
- Changelog with ten dated entries from July to September 2026, breaking changes flagged
Weaknesses
- No public pricing; live access starts with a sales form
- No security.txt, security page, disclosure policy or certification found
- Consent revocation only at the bank, so the API may keep reporting
AUTHORIZED
Price PaidAuth API keyx402 nohosted
Flinks
D 52.7/100Flinks is a Canadian bank-data aggregator owned by National Bank of Canada. Its REST API and Flinks Connect widget read accounts, balances, transactions and holder details from Canadian and US institutions with the holder's consent, and start Canadian bank payments.
Verdict Ten public OpenAPI files, an llms.txt index with Markdown twins and published sandbox keys let an agent start without a signup. Live access needs a one-year contract from $500 a month, keys never expire, no rate-limit numbers are published, and the status page logged 77 incidents in 90 days.
Choose it for A lender or fintech with steady volume that needs Canadian bank data, income and lending attributes, PDF statements or Canadian bank payments.
Strengths
- Ten OpenAPI 3.0 files are public at docs.flinks.com, 85 operations in all, with the main Connect and Enrich file holding 34
- Shared sandbox keys for the Toolbox instance are published in the docs, so test calls need no account
- llms.txt lists 216 pages with Markdown twins, and the docs add a skill file and a read-only documentation MCP server
Weaknesses
- Live access needs a contract with a monthly minimum and a one-year term. The pricing page says there is no pay-as-you-go plan or self-serve trial
- The secret key,
x-api-keyand HMAC secret do not expire, and no scopes or rotation steps were found for the Connect API - No rate-limit numbers are published, and
TOO_MANY_REQUESTSis documented under HTTP 401 with no Retry-After
Price PaidAuth API keyx402 nolocal
Akoya
D 48.3/100Akoya runs a US data access network through which consumers permit apps to read their bank and brokerage accounts. Data recipients call FDX-based REST APIs for accounts, balances, transactions, customer details, statements and consent, after an OAuth consent flow.
Verdict Six OpenAPI 3.1 specifications, a free self-service sandbox and read-only data endpoints behind per-consumer OAuth tokens make the API straightforward to test. Production needs a security review and a signed agreement, no price is published, and no public status page, SLA, SDK or llms.txt was found.
Choose it for A US fintech that wants consumer-permissioned data over direct institution APIs in FDX format and can pass a security review.
Strengths
- Data APIs are read-only GET endpoints, and each token covers one consumer, one app and the accounts that consumer selected
- OpenAPI 3.1 specifications are published for the Token, Service Token, data, Apps Management, Notifications and Consent APIs
- Free self-service sandbox with a test institution (
mikomo), scripted test users and a public Postman workspace
Weaknesses
- No price is published. Standard (under 10,000 monthly connections) and Enterprise are named without figures, and a set-up fee may apply
- Production access needs an onboarding questionnaire, a security review (SOC 2 report or questionnaire) and an agreement signed by Docusign
- No public status page, SLA or numeric rate limit for the data APIs was found. Availability figures sit inside the Data Recipient Hub
Price PaidAuth OAuthx402 nohosted
Enable Banking
D 47.1/100Finnish open banking API (FIN-FSA registered AISP) covering 2,700-plus banks in about 30 European countries, with account information and payment initiation under Enable Banking's licence or your own eIDAS certificates.
Verdict Restricted mode gives live data for your own whitelisted accounts before any contract. No public prices and a minimum monthly invoice.
Choose it for EU account data and payments for builders who want live data before signing anything, or agents that read their operator's own accounts.
Strengths
- Restricted mode gives live data for your own whitelisted accounts before any contract
- Private-key JWT auth, at most 24 hours, with no shared secret on the wire
- continuation_key pagination with date and status filters on transactions
Weaknesses
- No public prices and a minimum monthly invoice
- No public status page; bank disruptions sit behind the Control Panel login
- No OpenAPI file, llms.txt or official SDK, only samples
Price PaidAuth OAuth or keyx402 nohosted
Head to head
- Belvo vs Plaid B 63.5 vs B 69.8
- MX Platform API vs Plaid B 62.5 vs B 69.8
- Plaid vs Tink B 69.8 vs B 62.5
- Plaid vs TrueLayer B 69.8 vs B 62.1
- Belvo vs MX Platform API B 63.5 vs B 62.5
- Belvo vs Tink B 63.5 vs B 62.5
- Belvo vs TrueLayer B 63.5 vs B 62.1
- MX Platform API vs Tink B 62.5 vs B 62.5
- MX Platform API vs TrueLayer B 62.5 vs B 62.1
- Tink vs TrueLayer B 62.5 vs B 62.1
Questions
What are the highest-rated open banking and bank data APIs for AI agents?
Plaid has the highest benchmark score of the 15 ranked open banking and bank data APIs, 69.8 (B). Belvo is second with 63.5 (B).
How many open banking and bank data APIs are agent-ready?
0 of the 15 ranked here grade BB or better, the bar for agent-ready on the Anchor benchmark.
Which open banking and bank data APIs accept x402 payments?
None of the ranked listings here accepts x402 for its main call yet.
How is this list ranked?
By the Anchor benchmark score out of 100, a weighted mean of the scored categories minus deductions for negative events, from public evidence re-checked as vendors change. Listings cannot pay for a place. The latest assessment behind this page is from 9 October 2026.
How this list is made
The order is the Anchor benchmark score, the same number as on each listing and in the top list. Each listing is graded from public evidence against the benchmark checklist, and the picks above are worked out from those grades, prices and facts. No listing pays for its place, and paid audits or listing help never change a score.
Full ranked table · 105 head-to-head comparisons · Best tools in every category