| Last active | User | First match | Questions | Cost | Feedback |
|---|---|---|---|---|---|
| 2026-09-18 10:54 | yordan@dext.com |
How many active accounts do we have?
1 failed
|
2 | $17.1608 | — |
| 2026-09-17 14:59 | yordan@dext.com | What is our average customer LTV (total MRR over customer lifetime to date)? | 1 | $34.4365 | — |
| 2026-09-17 10:19 | yordan@dext.com | What is NECE in Dext content? | 4 | $1.5321 | — |
| 2026-09-15 13:27 | yordan@dext.com | Partners MRR by month, last 6 months | 2 | $68.7470 | — |
| 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? | 7 | $189.6923 | — |
| 2026-09-15 11:36 | yordan@dext.com |
How many BSE (Bank Statement Extraction) sheets have been used for CRN 7233405369 in the billing period 2026-08-10 to 2026-09-09?
1 failed
|
3 | $37.6174 | — |
| 2026-09-10 12:33 | yordan@dext.com | What is the underlying query (SQL/fields) behind this Omni report: https://dext.omniapp.co/e/3:fEAIbc88/3 | 1 | $0.0185 | — |
| 2026-09-10 10:31 | yordan@dext.com | Which Omni field tracks document extraction usage that counts toward an account's "prepare" plan limit? I'm seeing options like Volume of Receipts, Volume of Items Submitted, and Volume of Items Extracted - which one is the correct field for usage against the prepare limit? | 1 | $0.0275 | — |
| 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 | MRR for the last 12 months, month over month | 3 | $3.7753 | — |
| 2026-09-04 20:01 | yordan@dext.com | ACV for Dext today | 4 | $6.8047 | — |
| 2026-09-04 14:11 | yordan@dext.com | Quarterly gross revenue retention (GRR) for France | 1 | $0.7638 | — |
| 2026-09-04 13:19 | yordan@dext.com | What is our ARR (Annual Recurring Revenue) for the last 12 months, broken down month over month? | 22 |
$21.6506 1 unpriced
|
— |
| 2026-09-01 14:19 | yordan@dext.com | Partner accounts with outstanding invoices including company name, NetSuite account number, company registration number, subsidiary, outstanding debt by age buckets (current 15/7/2026-13/8/2026, 30 days 15/6/2026-14/7/2026, 60 days 16/5/2026-14/6/2026, 90 days before 16/5/2026, overdue over 90 days), total outstanding amount, account manager name, last login date, next invoice date | 25 | $7.5846 | — |
| 2026-09-01 13:08 | yordan@dext.com | Partner accounts with outstanding invoices including company name, NetSuite account number, company registration number, subsidiary, outstanding debt by aging buckets (current 15/7/2026-13/8/2026, 30 days 15/6/2026-14/7/2026, 60 days 16/5/2026-14/6/2026, 90 days before 16/5/2026, overdue over 90 days), total outstanding amount, account manager name, last login date, next invoice date | 2 | $1.2581 | — |
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.