| Last active | User | First match | Questions | Cost | Feedback |
|---|---|---|---|---|---|
| 2026-09-28 14:32 | 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 | 8 | $80.4582 | — |
| 2026-09-24 08:40 | suzannah.weinfass@dext.com | What user session or sessionization data is available? What tables/fields define a session, and what session-level metrics do we track? | 1 | $0.3143 | — |
| 2026-09-22 10:58 | suzannah.weinfass@dext.com | AI Assist paid licence sales: total net paid AI Assist licences sold as of 18 September 2026, broken down by region (UK, NA including Canada and US, APAC, France, South Africa), split by partner vs direct, plus licences ended since 23 April | 3 | $101.0706 | — |
| 2026-09-11 14:37 | suzannah.weinfass@dext.com | What does the metric NECE mean? | 7 | $5.2099 | Negative ×2 |
| 2026-09-10 15:32 | 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? | 4 | $8.2905 | — |
| 2026-09-10 08:56 | suzannah.weinfass@dext.com | partner MRR by month for the last 6 months | 3 | $1.3831 | Negative |
| 2026-07-23 15:07 | suzannah.weinfass@dext.com | What is project Chandler? | 1 | $0.0156 | — |
| 2026-07-23 13:12 | suzannah.weinfass@dext.com | UK Partner churn month over month from July 2025 to now | 1 | $0.8002 | — |
| 2026-07-17 15:10 | suzannah.weinfass@dext.com | overall Dext Partner GRR value | 5 | $1.6100 | — |
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.