adjust_balance
ChatGPTState what the project's balance in one currency actually is; the signed difference is recorded as an adjustment row, so the ledger still explains the number. Needs accounts.manage (the balances permission). Refused when the balance already matches.
attach_receipt
ChatGPTAttach an image (JPEG, PNG, HEIC, WebP, GIF) or PDF to a transaction, sent as base64 (a data: URL prefix is fine). Needs txn.write. Up to 3 files per transaction; files up to about 3MB (the request has to fit 4.5MB once encoded). The bytes are sniffed: the declared type is ignored. If you can run a command or an HTTP request yourself, prefer request_attachment_upload: no base64 to write out. When the file is on disk, also send size_bytes and sha256 of the original: a copy that does not match, or an image that arrives cut short, is refused instead of stored. The answer gives the stored file's sha256, width and height to check against.
complete_attachment_upload
ChatGPTStep 2 of 2: after the PUT to the upload_url from request_attachment_upload, attach that file to the transaction. Needs txn.write. Same checks as attach_receipt: the bytes are sniffed (images or PDF only), an image that does not decode is refused, and with sha256 a file that is not the one you sent is refused. The upload is discarded either way; on a refusal ask for a new upload_url and send it again. The answer gives the stored file's sha256, width and height.
create_category
ChatGPTAdd an expense or income category, optionally as a subcategory of a top-level one of the same type (two levels max). Needs categories.manage.
create_exchange
ChatGPTMove money from one of the project's currencies to another: give what leaves (amount, currency) and what arrives (to_amount, to_currency); the rate is whatever the two amounts say. Needs txn.write. Two linked rows are written, one per ledger. Never invent a rate: both amounts come from the person.
create_project
ChatGPTCreate a new project owned by the person, within their plan's project limit. Before calling, call project_options and ask the person: (1) the name; (2) which template fits (personal = one person's everyday spending; household = a shared home: bills, groceries, children, pets; business = a small venture: revenue, supplies, costs; blank = start almost empty and build the categories yourself), or whether to copy the categories of one of their connected projects instead; (3) which currencies they use, each its own ledger; (4) optionally an icon and a colour (otherwise the template's). Do not call until the person has answered (1) to (3). The new project joins this connection: use its project_id on the next calls.
create_recurring_rule
ChatGPTSchedule a transaction that repeats weekly, monthly or yearly from next_run, optionally for a fixed number of instalments. Needs budgets.manage. Occurrences are written as pending by the daily materializer, not immediately.
create_transaction
ChatGPTLog one expense or income in one of the project's currencies. Needs txn.write. Never guess an amount: ask the person if it is missing. For many rows at once use create_transactions.
create_transactions
ChatGPTLog up to 50 expenses/incomes in one call (a statement, a list the person dictated). Needs txn.write. Every item is validated before anything is written; if one is invalid nothing is saved and the reply names the item. Items are then written in order; should one fail midway the reply lists what was saved.
delete_attachment
ChatGPTRemove one attachment from a transaction (ids from get_transaction). Needs txn.write. Irreversible.
delete_budget
ChatGPTRemove one budget row by id (from list_budgets). Needs budgets.manage.
delete_category
ChatGPTDelete a category and its subcategories. Needs categories.manage. Its transactions move to move_to_category_id (same type), or to the project's Other when omitted. The per-type Other cannot be deleted. Irreversible: tell the person how many transactions move and confirm first.
delete_recurring_rule
ChatGPTStop a rule for good. Needs budgets.manage. Movements that already happened stay; its scheduled next occurrence (written ahead, not yet due) is removed with it, and the answer says how many. To stop temporarily use update_recurring_rule with active=false.
delete_transaction
ChatGPTDelete a transaction (and its exchange counterpart if it is an exchange leg). Needs txn.write. Irreversible: confirm with the person first.
get_project
ChatGPTOne project in detail: name, enabled currencies, number format, the member's role and exact capabilities.
get_transaction
ChatGPTA single transaction with every field, its category name, and its attachments.
list_balances
ChatGPTThe project's balance in each enabled currency (current, and projected when pending rows exist). There are no accounts: each currency is its own ledger and this is the whole picture.
list_budgets
ChatGPTBudgets of one month with limit, spent so far and percent, per currency. Budgets are per currency: a UYU cap only counts pesos spent.
list_categories
ChatGPTExpense and income categories with ids, display labels in the member's language, and parent ids for subcategories. Use the id in other tools.
list_projects
ChatGPTEvery project this connection covers, with its enabled currencies (each its own ledger, nothing converted between them), the member's role and capabilities there, today's date and the member's language. Call this first. When several projects are listed, pass project_id on every other call; if the person has not said which project they mean, ask them before writing anything.
list_recurring_rules
ChatGPTRules that write a transaction on a cadence (rent, salary, instalments): cadence, next run, template, active flag, instalments done/total.
list_transactions
ChatGPTTransactions newest first, filtered in the database. Filter by an inclusive date range (YYYY-MM-DD) or days back from today; by category (its subcategories included), currency, type, status, or a case-insensitive text search over description and merchant. Page with limit/offset; total_matching is the full count. Amounts are in major units of each row's own currency.
project_options
ChatGPTWhat a new project can be: the templates (what each is for and the categories it starts with, in the person's language), the icons and colours to choose from, the connected projects whose categories could be copied, and how many more projects the person's plan lets them own. Call this before create_project and use it to ASK the person; never pick for them.
request_attachment_upload
ChatGPTStep 1 of 2 to attach a file without base64, for an agent that can make an HTTP request itself (curl, fetch). Needs txn.write. Give the transaction and the file's exact size in bytes (up to 10MB); the answer has an upload_url valid for 15 minutes. PUT the raw bytes there with the headers it lists (Content-Type application/octet-stream; the size must match exactly, the URL is signed for it), e.g. curl -X PUT -H "Content-Type: application/octet-stream" --data-binary @receipt.jpg "<upload_url>". Then call complete_attachment_upload with the upload_id. Nothing is attached until that second call. Up to 3 files per transaction.
set_budget
ChatGPTCreate or replace a monthly cap for an expense category (or the month's overall cap when category_id is omitted) in one currency. Needs budgets.manage. Upsert: setting the same category+month+currency again replaces the amount.
spending_summary
ChatGPTIncome, expenses, net and pending for a window, one block per currency (every currency is its own ledger; nothing is converted or added across currencies), plus the expense breakdown by category with shares, per currency. expense is a positive magnitude (money out); net = income - expense; pending is the signed sum of pending rows. Default window: the last 30 days.
update_category
ChatGPTRename a category or change its icon/colour. Needs categories.manage. Seeded categories keep their stable id; the new label is shown to every member as typed (never translated).
update_recurring_rule
ChatGPTChange a rule: pause or resume it (active), move its next run, change the cadence interval or instalment count, or change what it writes (amount, currency, category, description). Needs budgets.manage. Occurrences that already happened stay as they are. Pausing also removes its scheduled next occurrence (not yet due); resuming writes it again, or starts from the next date due today or later if that one already passed, so paused months are never charged after the fact.
update_transaction
ChatGPTChange one or more fields of an existing expense or income. Needs txn.write. Exchange legs cannot be edited (delete the pair with delete_transaction and re-enter it with create_exchange).