ChatGPT DotsNo income or savings amount disclosed in the source.Public · Free

Link accounts across institutions and ask in plain language for spending, APR and due dates

r/mintuit 讨论串用户(原帖不可读,未取得用户名)Reddit · Date not disclosed

Read original

Saved text / editorial summary

采集站 agentusecases.ai 的编辑摘要(原帖 Reddit 线程在本次采集时不可读,以下为转述而非引文):用户通过 ChatGPT 的财务账户关联流程,连接了一张 Robinhood 卡、一张 AmEx 卡、一个 Wells Fargo 支票账户和券商账户,然后等待近期交易同步。他用大白话提问,比较账户与卡片,ChatGPT 返回了分类与商户拆解,以及交易笔数、平均客单价、余额、APR、到期日、还款与入账(在可得的情况下)。结果:对逐卡分析和大白话复盘很有用,但最初只有约 30 天历史,且不会编造更长的趋势;用户的应对是安排在每月 15 号和最后一天各跑一次快照报告,为将来的对比保留摘要。

Business model

A user connected a checking account, credit cards and brokerage accounts to ChatGPT's finance tools, waited for recent transactions to sync, then asked plain-English questions and got category and merchant breakdowns, transaction counts, average ticket size, balances, APR, due dates, payments and credits. What is worth copying is not the numbers but how they handled a real limitation: only about 30 days of history at first, and the assistant would not invent a longer trend. So they scheduled snapshot reports on the 15th and last day of each month to build their own comparison baseline over time. No income figures.

The transferable move is building your own baseline with scheduled snapshots. It converts an uncontrollable limitation (short history) into a compounding asset you own. Per-card-then-aggregate keeps the units aligned, which is where most personal finance summaries quietly go wrong.

Workflow

  1. Confirm what you are authorising and which accounts to link, and keep the scope to what you actually want to see together.
  2. Wait for transactions to finish syncing before asking anything, or you will read a partial distribution as if it were the full picture.
  3. Start card by card: transaction count, total spend, average ticket, top merchants, balance, APR, due date. Align the per-card view before aggregating.
  4. Require the assistant to state the covered time range and what it could not retrieve.
  5. Schedule snapshot reports twice a month so you accumulate your own baseline instead of depending on the tool's history depth.
  6. Spot-check one transaction against the official statement to confirm the link and categorisation are not misaligned.

Adaptation plan

The thread gives no amounts, no cost of the setup, and no subscription tier. Whether APR and due dates are reliably available per card is not stated. The original text could not be read at collection time (Reddit returned HTTP 403 on every public endpoint; no Wayback snapshot). The workflow, prompt and pitfalls here are AgentFlow proposals, untested against real accounts.

Starter prompt

Written by AgentFlow; not the original author’s prompt. Not independently deployed in Muse or Grok.

You are my assistant for a personal accounts health check. Query and summarise only. No investment advice, no tax or legal conclusions.

[INPUT]
Linked accounts: [list accounts and cards]
Period: [e.g. last 30 days]
My three concerns: [e.g. where the money goes, true cost per card, upcoming due dates]

[EXECUTION STEPS]
1) First state the period you can actually cover, which accounts are included, and what you could not retrieve. Write "not available" rather than estimating.
2) Per card: transaction count, total spend, average ticket, top five merchants with share.
3) Aggregated category breakdown (dining, transport, shopping, subscriptions, housing, etc.), flagging changes only when a comparable previous-period baseline is supplied; otherwise write "not available".
4) For each card: current balance, APR, due date this cycle, minimum payment. Mark anything you cannot retrieve.
5) Flag anomalies: duplicate charges, merchants with a sudden jump, possible overlooked subscriptions.
6) Finish with up to three evidence-supported suggestions for cutting cost or avoiding interest, each tied to a specific figure above, no generalities.

[OUTPUT REQUIREMENTS]
- Every number carries its source account and period.
- If the period is too short, say so explicitly: "only N days of data, not enough to judge a trend". Never extrapolate.
- Close with a reminder that APR, due dates and minimum payments follow the institution's official statement.
- No investment advice, no product recommendations.

[HUMAN CONFIRMATION POINTS]
- I decide which accounts to authorise and can revoke at any time.
- Cancelling a direct debit, arranging a payment or any card action is mine to do in the institution's own app; you only flag it.
- I verify any rate or due-date conclusion against the official statement before acting on it.

[COMPLETE SMALL SYNTHETIC INPUT AND OUTPUT — not real business data; no model execution]
The JSON contains all demo inputs and a manually authored reference output. Do not invent facts from files not supplied. This reference covers only this minimal input and is not a business reproduction.
{
  "input": {
    "period": "2026-09-01/2026-09-30",
    "currency": "USD",
    "accounts": [
      {
        "id": "card-A",
        "coverage": "2026-09-01/2026-09-30",
        "balance": 120,
        "apr": null,
        "due_date": "2026-10-18"
      }
    ],
    "transactions": [
      {
        "id": "T1",
        "account": "card-A",
        "merchant": "Cafe",
        "category": "dining",
        "amount": 40
      },
      {
        "id": "T2",
        "account": "card-A",
        "merchant": "Stream",
        "category": "subscription",
        "amount": 20
      },
      {
        "id": "T3",
        "account": "card-A",
        "merchant": "Stream",
        "category": "subscription",
        "amount": 20
      }
    ],
    "previous_period": null
  },
  "expected_output": {
    "transaction_count": 3,
    "spending_total": 80,
    "average_ticket": 26.67,
    "category_totals": {
      "dining": 40,
      "subscription": 40
    },
    "category_share_pct": {
      "dining": 50,
      "subscription": 50
    },
    "possible_duplicate": [
      "T2",
      "T3"
    ],
    "duplicate_confirmed": false,
    "previous_period_change": "not available",
    "card_balance": 120,
    "apr": "not available",
    "due_date": "2026-10-18; verify against official statement",
    "transactions_modified": false
  },
  "mode": "synthetic_read_only_reference_not_model_execution"
}

Running costs and pitfalls

The thread gives no amounts, no cost of the setup, and no subscription tier. Whether APR and due dates are reliably available per card is not stated. The original text could not be read at collection time (Reddit returned HTTP 403 on every public endpoint; no Wayback snapshot). The workflow, prompt and pitfalls here are AgentFlow proposals, untested against real accounts. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.

Author-reported results are not independently audited.

The breakdown and starter prompt are AgentFlow’s analysis and adaptation; results are not guaranteed.

Original text and media remain attributed to their authors.