Niches · Bank data & open banking
Find particular transactions or subscriptions
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
The matching transactions, with date, amount, payee and account, returned by a filtered query or a server-side search rather than by reading every transaction; recurring charges are grouped by payee.
How agents ask for it: find every Netflix charge
, list my recurring subscriptions
, did the landlord's payment arrive
, find the invoice payment to Acme
Does the job, with a limit 9
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.
| Listing | Why |
|---|---|
| BankMCP BB noskillish (open-source project) | search_transactions matches counterparty or description server-side across all accounts, with account, date, amount and totals. Recurring charges are not grouped by payee; a subscription-audit prompt leaves that to the agent. source |
| Basiq B Basiq Pty Ltd | Server-side filters cover account, connection, institution, postDate, status, direction and class, but not payee or description text, and recurring charges are not grouped. source |
| Belvo B Belvo Tecnologias Ltda. | List transactions filters server-side by description, reference, amount ranges, category and dates, so a payee search needs no full read; recurring charges are not grouped in what was read. source |
| MX Platform API B MX Technologies, Inc. | Transactions carry is_recurring and is_subscription, and an insights repeating_transactions endpoint groups them; the list filters by date and category but has no payee or text search. source |
| Plaid B Plaid Inc. | /transactions/recurring/get groups recurring inflow and outflow streams by merchant (an add-on), and acc-03 used it for subscription reviews. /transactions/get filters only by date and account, so a payee search pages everything. source |
| Powens E Powens SAS | Server-side wording, search, value and min_value/max_value filters return matching transactions without a full read, but recurring charges are not grouped by payee. source |
| Tink C Tink AB | The transactions list has no payee or text filter; the Finance Management guides retrieve expenses by brands and subscriptions, which needs the Money Manager product. source |
| Yapily C Yapily Ltd | No payee or text filter on transactions; Data Plus enrichment adds merchant and a recurring flag, so the agent can group subscriptions after reading the range. source |
| Yodlee Core API E Yodlee, Inc. | The keyword parameter does a server-side contains search on descriptions, with category and account filters and a count endpoint. Merchant names only in the US, Canada, UK and India, and no recurring grouping was found. source |
Couldn't check 1
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| Teller F Teller, Inc. | Not read: teller.io's robots.txt disallows ClaudeBot, Claude-Web and anthropic-ai, so the docs were not fetched. |
Doesn't do this job 6
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Akoya D Akoya LLC | The transactions endpoint filters by time window only, with offset and limit paging; no payee, amount or text filter. source |
| Enable Banking D Enable Banking Oy | The transactions endpoint filters by date range and status only; no payee, amount or text filter, so the agent pages the full history. source |
| Flinks C Flinks Technology Inc. | /GetAccountsDetail takes only the history window; there is no payee, amount or text filter, so the agent reads the whole payload. source |
| GoCardless Bank Account Data D GoCardless Ltd | The transactions endpoint takes date_from and date_to only; no payee, amount or text filter and no recurring grouping. source |
| Salt Edge Account Information C Salt Edge Limited | GET /transactions filters by connection, account, pending and duplicated only; no payee, amount or text filter. source |
| TrueLayer B TrueLayer Limited | Get account transactions takes only from, to, async and webhook_uri; no payee or text filter and no recurring grouping. source |
What stops agents finishing
- no payee filter, so the agent pages the whole history
- payee strings that differ from what the person sees in online banking
Around it
Before: banking-data.connect-consent. After: email.draft-cancellation, messaging.send.
Where this comes from
Weight 9 of 100 in Bank data & open banking: 4 of 41 accounts (subscription hunting in Driggsby, Muse and Tiller threads; BankMCP eval issue 12 on 356 rows read to find 12 charges)
The same as data: /api/v1/use-cases/banking-data.find-transactions.json, or the MCP tool get_use_case with id banking-data.find-transactions. Other jobs in this category: /api/v1/niches?category=banking-data.
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.