| 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-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 | — |
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.