Niches · Bank data & open banking

Keep a budget or ledger in step with the bank

Two or three companies' docs show a full fit.

3companies, full fit
12companies, fit with a limit
16companies carry the tag
26share of the category's work
14first-hand accounts

What counts as done

Every booked transaction in the window arrives once, with a stable id, amount, date and payee, and pending items are marked as pending; a repeat sync adds only new or changed items through a cursor or date window.

Measured, for our own tests: the synced balance equals the bank's booked balance after one sync. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: sync my bank transactions into my budget, pull last month's transactions into the spreadsheet, import my bank feed every night, backfill a year of history

Does the job 3

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
MX Platform API B
MX Technologies, Inc.
List transactions filters by from_updated_at and to_updated_at for delta sync, pages up to 1,000 records, carries status and a stable guid, and extend_history reaches 24 months where the institution allows; ranges are capped at six months per call. source
Powens E
Powens SAS
Transactions list filters by last_update for changes since the last sync, marks pending items with coming, keeps removed ones with a deleted timestamp, and pages up to 1,000 with explicit pagination. source
Tink C
Tink AB
/data/v2/transactions filters by bookedDateGte, bookedDateLte, statusIn and accountIdIn, pages by token at up to 100, and each transaction has an id, providerTransactionId and BOOKED or PENDING status; account-transactions:modified webhooks give the changed date range. source

Does the job, with a limit 12

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Akoya D
Akoya LLC
Transactions take startTime and endTime (default 15 days), offset and limit, and carry status (AUTHORIZATION, MEMO, PENDING, POSTED). There is no cursor or change feed, and acc-14 reports duplicates and missing transactions from Chase via Akoya. source
BankMCP BB
noskillish (open-source project)
get_transactions takes from/to and follows continuation; ids are entry_reference or a stable fingerprint (issue 10) with booked or pending status. Open issue 18: a bank 429 marks the consent EXPIRED, so repeat syncs can send the person to re-login. source
Basiq B
Basiq Pty Ltd
Transactions filter by transaction.postDate and status (pending or posted), page at 500, and posted ids survive a refresh. Pending transactions get new ids on every refresh, and CDR connections carry no running balance. source
Belvo B
Belvo Tecnologias Ltda.
Recurrent links refresh weekly by default and fire new_transactions_available and transactions_deleted webhooks; transactions filter by value_date and accounting_date ranges. Brazil Open Finance POST retrievals count against monthly per-CPF limits, and refresh-rate changes are priced by sales. source
Enable Banking D
Enable Banking Oy
Transactions take date_from, date_to and continuation_key, with BOOK or PDNG status; entry_reference is immutable but transaction_id may change on refetch. Background reads hit the banks' four-a-day cap (wait 6 hours), and acc-18 saw a Revolut transaction skipped silently. source
Flinks C
Flinks Technology Inc.
/GetAccountsDetail returns Days90 or Days365 of transactions with TransactionId, Date, Debit, Credit and Description, but in one unpaginated payload with no cursor; nightly refresh works only where the bank needs no MFA, and the docs say to plan for partial coverage. source
GoCardless Bank Account Data D
GoCardless Ltd
Transactions come split into booked and pending with date_from and date_to and a last_updated field, but transactionId is optional and bank-set. Accounts show reissued ids duplicating every row (acc-17), unusable pending items (acc-20) and a 4-a-day cap stalling backfill (acc-27). source
Plaid B
Plaid Inc.
/transactions/sync returns added, modified and removed through a cursor, with pending items replaced via pending_transaction_id. History defaults to 90 days unless days_requested is set (acc-32), refreshes bill per call on top of per-Item fees (acc-31), and Chase duplicates are reported (acc-14). source
Salt Edge Account Information C
Salt Edge Limited
Transactions list by account with from_id paging, posted or pending status, a duplicated flag and possible_duplicate in extra. Pending items are removed on every refresh and may return with new ids, and acc-26 hit 403 on connect-session creation for Firefly III. source
TrueLayer B
TrueLayer Limited
Settled and pending transactions are separate endpoints with from and to dates; normalised_provider_transaction_id is stable across requests and running_balance is returned. No cursor, X-PSU-IP is needed to pass the 4-a-day cap, and a 365-day Santander backfill got 403 access_denied (acc-33). source
Yapily C
Yapily Ltd
Transactions take from, before, limit, sort, offset and cursor, with BOOKED or PENDING status and a transaction hash where the bank gives no id. Background reads are capped at four a day, and history past 90 days is often only available in the first five minutes. source
Yodlee Core API E
Yodlee, Inc.
GET /transactions takes fromDate and toDate (30-day default, two years at most) with skip and top paging; each transaction has a unique id and status (POSTED, PENDING and others). There is no cursor, and change detection needs DATA_UPDATES webhooks or /dataExtracts/events in 60-minute windows. source

Couldn't check 1

The docs were closed to us, or silent. These carry no mark either way.

ListingWhy
Teller F
Teller, Inc.
Docs not fetched (robots.txt bars Anthropic agents). acc-36 syncs Chase statements to a sheet, but one 2024 account doesn't establish ids, pending handling or a sync window. source

What stops agents finishing

  • bank reissues transaction ids so duplicates arrive
  • four unattended reads a day per account under PSD2
  • a backfill window the bank refuses with 403, read as lost consent
  • per-refresh billing on top of per-connection fees

Around it

Before: banking-data.connect-consent. After: spreadsheets.append-rows, accounting.import-bank-feed, personal-finance.categorise.

Where this comes from

Weight 26 of 100 in Bank data & open banking: 14 of 41 accounts, the most common job: Actual Budget, Firefly III, Sure, Leggen and spreadsheet syncs on HN and GitHub

The same as data: /api/v1/use-cases/banking-data.sync-ledger.json, or the MCP tool get_use_case with id banking-data.sync-ledger. Other jobs in this category: /api/v1/niches?category=banking-data.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.