{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/banking-data.spending-summary/",
    "json": "https://www.anchorterminal.com/niches/banking-data.spending-summary/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/banking-data.spending-summary/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/banking-data.spending-summary/index.min.md"
  },
  "markdown": "One company's docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 1 | 11 | 16 | 14 | 6 |\n\n## What counts as done\n\nTotals per category and per month that match the sum of the transactions, with internal transfers excluded and each transaction carrying a category from a documented taxonomy; the whole range is read without the agent losing rows to truncation.\n\nHow agents ask for it: how much did I spend on food last month; what are my top spending categories this year; which months did I spend most; give me a 12-month spending overview\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Yodlee Core API (Yodlee, Inc.)**: Transactions carry a category and categoryType (TRANSFER, INCOME, EXPENSE and others) from GET /transactions/categories, and /derived/transactionSummary returns totals by category per month, week or year server-side.\n\n## Does the job, with a limit\n\nIt 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.\n\n- **BankMCP (noskillish (open-source project))**: monthly_summary returns in and out per month with own-account transfers excluded and a checked list flagging incomplete reads, fixing the clipping in issue 13. No category field beyond the bank's merchant_category_code, so the agent must classify.\n- **Basiq (Basiq Pty Ltd)**: Each transaction has a class from a fixed enum (payment, transfer, bank-fee, refund and others) and Enrich adds merchant detail, but class is too coarse for spending categories and there is no per-month aggregate outside the paid reports.\n- **Belvo (Belvo Tecnologias Ltda.)**: Transactions carry a category from a documented enum including Transfers, but categorisation must be switched on by contacting Belvo, and there is no per-month aggregate.\n- **Flinks (Flinks Technology Inc.)**: Enrich assigns a Category and SubCategory from a documented list (including Transfers) retrievable from /Categories, but Enrich is a separate paid product and no per-month aggregate was found.\n- **MX Platform API (MX Technologies, Inc.)**: Each transaction carries category and top_level_category from MX's taxonomy and the list filters server-side by category guid, but there is no per-month spending total; monthly_account_balances covers balances only.\n- **Plaid (Plaid Inc.)**: Each transaction carries personal_finance_category from a published taxonomy CSV, stated 95 per cent fill, including transfer categories. No aggregate endpoint, and acc-01 needed an LLM pass to correct Plaid's categories.\n- **Powens (Powens SAS)**: The old categories endpoint is marked obsolete and the current Categorization feature is framed for lending; no per-month spending aggregate was found. Transactions do carry a type and counterparty.\n- **Salt Edge Account Information (Salt Edge Limited)**: Each transaction has a category with categorization_confidence, and the reference lists categories plus expense and income category reports; categorisation can be disabled per client and its availability by plan was not read.\n- **Tink (Tink AB)**: Transactions carry categories and the Finance Management statistics endpoint returns monthly expenses by category, but that sits in the Money Manager product with its own scope; whether transfers are excluded was not read.\n- **TrueLayer (TrueLayer Limited)**: Each transaction has transaction_category (including TRANSFER) and a documented transaction_classification taxonomy, but some get no classification, CREDIT is never classified, and there is no aggregate endpoint.\n- **Yapily (Yapily Ltd)**: Data Plus categorisation returns a documented tier1-tier2-tier3 taxonomy for UK and EU consumer and business accounts, but it is in beta, runs as an async job, and there is no aggregate endpoint.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **Teller (Teller, Inc.)**: Not read: teller.io's robots.txt disallows ClaudeBot, Claude-Web and anthropic-ai, so the docs were not fetched.\n\n- not this job: Akoya (Akoya LLC): Transaction category is the bank's MCC or SIC where supplied, not a spending taxonomy, and there are no aggregates or transfer flags.\n- not this job: Enable Banking (Enable Banking Oy): The FAQ says Enable Banking gives no categorisation; transactions carry only the bank's optional ISO 18245 merchant_category_code and there are no aggregate endpoints.\n- not this job: GoCardless Bank Account Data (GoCardless Ltd): Raw Berlin Group transactions only: an optional merchantCategoryCode, no category taxonomy and no aggregate endpoint.\n\n## What stops agents finishing\n\n- categories wrong enough that the agent must re-classify\n- a response too long for the agent to read whole, so rows are dropped\n- transfers between own accounts not marked\n\n## Around it\n\nBefore: banking-data.connect-consent, banking-data.sync-ledger. After: spreadsheets.chart, personal-finance.budget.\n\n## Where this comes from\n\nWeight 14 of 100 in Bank data \u0026 open banking: 6 of 41 accounts (Driggsby, Muse, Lunch Money, Tiller, the BankMCP eval, the CSV workaround); the job assistants are sold for\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/banking-data.spending-summary.json, or the MCP tool get_use_case with id banking-data.spending-summary. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Summarise spending by category and month",
        "url": ""
      }
    ],
    "description": "Summarise spending by category and month: 1 companies fully do it, 11 with a limit, 16 carry the tag. Every listing in Bank data \u0026 open banking with the reason and a source.",
    "facts": null,
    "h1": "Summarise spending by category and month",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/banking-data.spending-summary/",
    "published": "",
    "section": "agents",
    "title": "Summarise spending by category and month | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/banking-data.spending-summary/"
  },
  "tokens": {
    "markdown": 1550,
    "slim": 330
  },
  "version": 1
}
