Niches · Bank data & open banking
Watch accounts and alert on new or unusual transactions
Four or more companies' docs show a full fit.
What counts as done
A webhook or scheduled check reports a new matching transaction to the channel, and states when the account was last refreshed.
Measured, for our own tests: the alert arrives within the provider's stated refresh interval. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: tell me when a big charge lands
, alert me if my balance drops below 500
, watch for my salary
, notify me about new transactions
Does the job 5
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| BankMCP BB noskillish (open-source project) | create_watch rules (balance threshold, large debit, payee match, missing payment) post to a webhook; watches store last_checked and a consent_expiring event fires 7 days ahead. Checks run at most four times a day. source |
| MX Platform API B MX Technologies, Inc. | The webhook index lists Transactions webhooks for created, updated or deleted transactions and Aggregation webhooks with counts of new data; members carry aggregated_at. Default aggregation is about every three hours. source |
| Plaid B Plaid Inc. | SYNC_UPDATES_AVAILABLE fires when new transactions arrive, checks run one to four times a day by institution, and /item/get reports last_successful_update for freshness. source |
| Powens E Powens SAS | CONNECTION_SYNCED and USER_SYNCED webhooks deliver new data after each synchronisation for permanent users, and accounts carry last_update for freshness. source |
| Tink C Tink AB | account-booked-transactions:modified and account-transactions:modified webhooks fire on new, updated or deleted transactions with the earliest and latest modified dates, and refresh:finished marks each refresh. source |
Does the job, with a limit 4
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 |
|---|---|
| Belvo B Belvo Tecnologias Ltda. | new_transactions_available fires after each recurrent refresh, but the default refresh is every seven days, so alerts lag by up to a week unless a faster rate is bought. source |
| Flinks C Flinks Technology Inc. | Webhooks deliver data after a refresh, but nightly refresh is at most daily and fails for banks needing MFA, so watches go quiet for part of the base. source |
| Salt Edge Account Information C Salt Edge Limited | Success callbacks fire whenever a connection's data changes and background_refresh exists, but the callback names the connection, not the transaction, so the agent re-reads to find what is new. source |
| Yodlee Core API E Yodlee, Inc. | Notification events can be subscribed for data updates and refreshes, and accounts carry lastUpdated, but the event payload signals that data changed, not which transaction, so the agent must re-read. source |
Couldn't check 2
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| Basiq B Basiq Pty Ltd | Webhooks cover users and consents 'to name a few'; the event-type list is served by an authenticated API call, so whether a new-transaction event exists was not established. source |
| 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 5
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Akoya D Akoya LLC | Webhooks carry only maintenance and consent events; there is no transaction event, so the agent polls. source |
| Enable Banking D Enable Banking Oy | Webhooks cover payment status only; account data must be polled by the agent, at most four times a day in the background. source |
| GoCardless Bank Account Data D GoCardless Ltd | The Bank Account Data endpoints and guides show no data webhooks; the agent must poll under bank caps as low as four calls a day per endpoint. source |
| TrueLayer B TrueLayer Limited | Data API webhooks only signal that an async request finished; there is no new-transaction event, so the agent polls under bank caps. source |
| Yapily C Yapily Ltd | Webhook categories cover payment status, async processing and categorisation completion; none fires on a new account transaction, so the agent polls under the four-a-day cap. source |
What stops agents finishing
- four unattended reads a day, so alerts lag
- consent lapses with no event, so the watch goes quiet
Around it
Before: banking-data.connect-consent. After: notifications.push, messaging.send.
Where this comes from
Weight 7 of 100 in Bank data & open banking: 3 of 41 accounts (Leggen alerts, Driggsby big-charge detection, Tiller anomaly finding); BankMCP and Plaid document watches and webhooks
The same as data: /api/v1/use-cases/banking-data.watch-alert.json, or the MCP tool get_use_case with id banking-data.watch-alert. 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.