| Last active | User | First match | Questions | Cost | Feedback |
|---|---|---|---|---|---|
| 2026-09-29 10:45 | gerty.bester@dext.com | For Dext Solo (UK sole trader/landlord) clients, what share of cost items were categorised by AI Assist (auto-applied guidance) between 6 July 2026 and 28 September 2026, versus all items processed on Solo in that period? | 2 | $100.2731 | — |
| 2026-09-28 14:05 | suzannah.weinfass@dext.com | Total cumulative value of payments processed through Dext Payments to date in GBP (all currencies converted), how many distinct accounts/businesses have made a payment, and total value processed in the last 30 days | 1 | $18.9184 | — |
| 2026-09-27 14:51 | gerty.bester@dext.com | How many distinct parent practices currently have at least one client account on Dext Solo? Latest snapshot please. | 1 | $13.3717 | — |
| 2026-09-27 12:46 | gerty.bester@dext.com | What is the total cumulative value of payments processed through Dext Payments to date (GBP, all currencies converted), how many accounts/businesses have made a payment, and how much was processed in the last 30 days? | 2 | $58.8117 | — |
| 2026-09-22 14:51 | ikraan.mohamed@dext.com | Give me key business metrics and trends for the last week (Sept 15-22, 2026) - revenue, new customers, churn, or usage highlights | 1 | $58.3348 | — |
| 2026-09-22 07:23 | chris.scott@dext.com | Using field parent_account_crn (not account_crn) to filter, list child account CRNs where parent_account_crn = 7132898864, snapshot date 2026-06-01 | 1 | $32.4853 | — |
| 2026-09-15 12:43 | yordan@dext.com | How many bank statement extraction (BSE) sheets have been used by CRN 7233405369 for the billing period from 2026-08-10 to 2026-09-09? | 4 | $188.6516 | — |
| 2026-09-15 11:36 | yordan@dext.com | BSE sheets used for CRN 7233405369 between 2026-08-10 and 2026-09-09 | 2 | $29.9525 | — |
| 2026-09-11 14:13 | suzannah.weinfass@dext.com | What is NECE and how has it changed over the last 6 complete months (monthly)? | 2 | $2.6220 | — |
| 2026-09-10 15:03 | suzannah.weinfass@dext.com | Is there a field that captures actual active usage of Payments (e.g. processed a transaction), distinct from HAS_PAYMENTS_ACCESS (access/entitlement)? Also, what was total active account count for each month March-August 2026, to compute an adoption rate? | 1 | $0.8842 | — |
| 2026-09-08 12:23 | yordan@dext.com | Show account_crn for all child accounts whose parent_account_crn is 7333782788, as of snapshot date 2026-04-23. Order by account_crn descending. Only return the account_crn column, not parent_account_crn. | 1 | $1.6656 | — |
| 2026-09-08 07:01 | yordan@dext.com | How many accounts have used the Pay feature this year, and how much total money has been processed through Pay this year? | 2 | $3.0924 | — |
| 2026-09-04 13:18 | yordan@dext.com | List distinct account_crn values where parent_account_crn = 7333782788 (filter only on parent_account_crn field, not account_crn) and snapshot date = 2026-04-23, sorted by account_crn descending | 6 | $10.0027 | — |
Cost is the LLM completion spend LiteLLM priced for each call, summed per
request.
Chandler is running on the Codex CLI, which draws ChatGPT plan quota
rather than per-token API billing, so this figure is not money paid —
it is what the same traffic would have cost on the API, priced from the
token counts Codex reports. Read it as the size of the bill avoided.
Two known limits: embedding spend is not recorded, so
retrieval and matching cost is missing, and because the figure is one sum
per request it cannot be split by model within a request — a
request's classifier and agent calls can use different models while
llm_model holds only one name.
Only authenticated calls are logged, USAGE_LOG_ENABLED can
switch logging off, and log writes are fail-soft — this is not a complete
record of traffic. Questions are grouped into sessions: a session is
exact when the caller echoed its id back to us and otherwise inferred from
a 30-minute gap in that user’s activity, so a grouping is only as
good as the source shown on the session itself. A call with no
attributable user gets no session at all; those questions are listed
separately rather than dropped.