# Find particular transactions or subscriptions

> Find particular transactions or subscriptions: 0 companies fully do it, 9 with a limit, 16 carry the tag. Every listing in Bank data & open banking with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/banking-data.find-transactions/
- Markdown: https://www.anchorterminal.com/niches/banking-data.find-transactions/index.md (~1,400 tokens)
- Slim: https://www.anchorterminal.com/niches/banking-data.find-transactions/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/banking-data.find-transactions/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 9 | 16 | 9 | 4 |

## 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

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.

- **BankMCP (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.
- **Basiq (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.
- **Belvo (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.
- **MX Platform API (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.
- **Plaid (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.
- **Powens (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.
- **Tink (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.
- **Yapily (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.
- **Yodlee Core API (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.

## Couldn't check

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

- **Teller (Teller, Inc.)**: Not read: teller.io's robots.txt disallows ClaudeBot, Claude-Web and anthropic-ai, so the docs were not fetched.

- not this job: Akoya (Akoya LLC): The transactions endpoint filters by time window only, with offset and limit paging; no payee, amount or text filter.
- not this job: Enable Banking (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.
- not this job: Flinks (Flinks Technology Inc.): /GetAccountsDetail takes only the history window; there is no payee, amount or text filter, so the agent reads the whole payload.
- not this job: GoCardless Bank Account Data (GoCardless Ltd): The transactions endpoint takes date_from and date_to only; no payee, amount or text filter and no recurring grouping.
- not this job: Salt Edge Account Information (Salt Edge Limited): GET /transactions filters by connection, account, pending and duplicated only; no payee, amount or text filter.
- not this job: TrueLayer (TrueLayer Limited): Get account transactions takes only from, to, async and webhook_uri; no payee or text filter and no recurring grouping.

## 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)

As data: https://www.anchorterminal.com/api/v1/use-cases/banking-data.find-transactions.json, or the MCP tool get_use_case with id banking-data.find-transactions. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
