get_usage

What the account SPENDS: one call, three answers, and they must never be mixed up. (1) THIS MONTH, a FORECAST: this_month_forecast gives total_minor for the month in progress, which is spent_minor (already debited) plus remaining_minor (what the active trackers and monitored corroborations will still run before month end, counted as real occurrences and recomputed from their configuration). Report it as a forecast, never as spend, and say the month. (2) PER MONTH, actual: by_month[] gives, for each of the last 12 months, month (YYYY-MM), spent_minor, and the same amount by project and by tracker. This is what the wallet was really debited. months_total says how many months have spend, so you can tell whether 12 covered everything. (3) OVER THE WINDOW, actual: total_spent_minor with by_project[] and by_tracker[] (biggest spender first) is a cumulative total over period (from and to, the first and last debit counted), never a monthly figure: quote the period alongside the amount. entries[] carries the ledger itself. Spend is broken down by COST LINE everywhere, in lines and by_category: survey (the checks themselves), ai_analyst (the supplement of the AI analysts grafted onto them), competitor_scan (a one-off scan of a basket of competitors, run from the app on the same check grid, which carries its own line and stays out of by_tracker), corroboration_check (monitored corroborations, one debit per check run) and other for a line the tool does not name yet, which stays visible rather than dropping out of a total. Amounts are in minor units of the wallet currency. Filter a single month with month (YYYY-MM), and the entries alone with type (in for top-ups, out for spend). Every tracker line carries tracker_id, ready for get_results or get_responses, and listed says whether that tracker is still in the account list. Each entry is stamped with created_at, the exact instant it was posted (RFC 3339, to the second, with the fraction the ledger recorded): an active account posts dozens of entries a day, so quote the time along with the date and let it order the entries of one day. On a check debit, on_demand says where the check came from: true for one asked for with survey_now, false for one the tracker cadence ran, null on an entry that is not a check debit. Separate the two when reporting spend, since one is a decision the account made and the other is the schedule running. Entries are paginated and page is CLAMPED: stop on page >= pages. get_credits gives what is left to spend.