Bank feeds

What the agent would be able to do

• Read balances for accounts named in your profile.
• Read transaction history over a defined date range.
• Read counterparty names and reference fields as the institution supplies them.

Where the credential lives

The credential is issued to you and held by Claude on your own device or in your own cloud tenancy. Skoor never holds it, never proxies the connection, and is not a subprocessor you need to disclose to your clients.

We specify the configuration and verify it from the outside — the same relationship an auditor has to your books.

What lands in the log, and where

Written to the store named in your profile — your SIEM, your log bucket, or your own database. Skoor reads it to compute your Agent Skoor and holds no copy.

Which standards govern this connector

These describe controls, not a compliance opinion. Whether your programme as a whole meets a standard is a judgement for your counsel.

What would trigger a re-score

• The institution changes what a scope grants.
• An account appears that is not named in your profile.
• The audit sink stops accepting writes.

Version and history

This connector has not been certified. Once it is, this section carries the rubric version, the date, and a link to the changelog entry that promoted it — so a claim on this page can always be checked.