What is the current MRR (most recent snapshot) for account CRN 9925868674?
Cost was recorded but no model name was. This happens when the answer came from an approved query — that path returns before the model name is stamped — so the cost figure is correct while the model behind it is not identified here. Cost was still priced per call at the right rate.
Basis: Account CRN, Account Name, Finance Account Type +2 more, 2026-09-23. Governed filters applied. Figures as of 18:16 UTC — reused from an earlier identical question, not recomputed just now. Chandler is still young and makes mistakes in his calculations sometimes — reach out to the Data & Analytics team in #analytics-questions-and-alerts if you have questions.
Per-step detail — each LLM call, each Omni request, each rejected draft —
is traced to stdout only and is not stored, so it cannot be shown here.
Query attempts counts run_query executions, not model turns.
WITH booking_snapshot_grain AS (
SELECT DISTINCT
omni_dbt__eds_calendar_day."DATE_DAY" AS "Snapshot Date",
omni_dbt__eds_all_accounts."ACCOUNT_CRN" AS "Account CRN",
omni_dbt__eds_all_accounts."ACCOUNT_NAME" AS "Account Name",
omni_dbt__eds_all_accounts."FINANCE_ACCOUNT_TYPE" AS "Finance Account Type",
omni_dbt__eds_bookings."PRIMARY_KEY" AS "Booking Primary Key",
CASE
WHEN omni_dbt__eds_all_accounts."FINANCE_ACCOUNT_TYPE" = 'Accountant'
THEN omni_dbt__eds_bookings."PREPARE_BOOKINGS_MONTHLY_ACV"
WHEN omni_dbt__eds_all_accounts."FINANCE_ACCOUNT_TYPE" = 'Corporate'
THEN omni_dbt__eds_bookings."PREPARE_BOOKINGS_MRR"
ELSE NULL
END AS "Monthly Revenue"
FROM PROD."EDS_ALL_ACCOUNTS" AS omni_dbt__eds_all_accounts
INNER JOIN PROD."EDS_CALENDAR_DAY" AS omni_dbt__eds_calendar_day
ON omni_dbt__eds_calendar_day."DATE_DAY" >= omni_dbt__eds_all_accounts."VALID_FROM" AND omni_dbt__eds_calendar_day."DATE_DAY" <= omni_dbt__eds_all_accounts."VALID_TO"
LEFT JOIN PROD."EDS_BOOKINGS" AS omni_dbt__eds_bookings
ON omni_dbt__eds_all_accounts."DERIVED_ACCOUNT_ID" = omni_dbt__eds_bookings."DERIVED_ACCOUNT_ID" AND omni_dbt__eds_calendar_day."DATE_DAY" >= omni_dbt__eds_bookings."VALID_FROM" AND omni_dbt__eds_calendar_day."DATE_DAY" <= omni_dbt__eds_bookings."VALID_TO"
WHERE TRY_TO_NUMBER(omni_dbt__eds_all_accounts."ACCOUNT_CRN") = 9925868674
AND omni_dbt__eds_calendar_day."IS_LATEST_AVAILABLE_DATE" = TRUE
AND omni_dbt__eds_all_accounts."FINANCE_ACCOUNT_TYPE" IN ('Accountant', 'Corporate')
AND (omni_dbt__eds_all_accounts."FINANCE_ACCOUNT_TYPE" = 'Accountant'
OR (omni_dbt__eds_all_accounts."FINANCE_ACCOUNT_TYPE" = 'Corporate'
AND omni_dbt__eds_bookings."HAS_PAID_SUBSCRIPTION" = TRUE))
AND COALESCE(omni_dbt__eds_all_accounts."IS_DEXT_DEMO", FALSE) = FALSE
AND omni_dbt__eds_all_accounts."FRANCHISE_NAME" IS NULL
AND (omni_dbt__eds_all_accounts."SALESFORCE_ACCOUNT_TYPE" != 'Reseller'
OR omni_dbt__eds_all_accounts."SALESFORCE_ACCOUNT_TYPE" IS NULL)
)
SELECT
MAX("Snapshot Date") AS "Snapshot Date",
MAX("Account CRN") AS "Account CRN",
MAX("Account Name") AS "Account Name",
MAX("Finance Account Type") AS "Finance Account Type",
SUM("Monthly Revenue") AS "Current Monthly Revenue",
COUNT(DISTINCT "Booking Primary Key") AS "Booking Records"
FROM booking_snapshot_grain
HAVING COUNT(*) > 0
LIMIT 1
No feedback linked to this request.
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.