Query audit
Wrong date range
ROAS for one week reported as the quarter
Wrong attribution, time zone or currency
Last-click on a data-driven account; a date range off by one in the account's time zone; spend summed across currencies
Emet shows you what your agent did, and whether what it said is true — it asks your data the same question and re-derives every number in code, with the math.
QUERY AUDIT / Q2 ROAS
Your agent answers your user
The finished turn is exported, after the answer is sent
AFTER THE ANSWER IS SENT · TURN → EMETEmet re-runs the query on your data (read-only)
Every number re-derived in code
Every sentence checked against the result
Accuracy Report + Slack alert
Never in the request path
Read-only access you control
No model grades its own output
Emet reads the finished turn your agent exports: every tool call, the arguments it was called with, and the raw result that came back.
Emet reads the finished turn your agent exports: every tool call, the arguments it was called with, and the raw result that came back.
A perfectly grounded answer built on a wrong query is still wrong. Emet checks the question your agent asked of the data, not just the number it got back.
Emet holds its own read-only access to your data and asks your warehouse the same question, correctly scoped. It never asks the AI what the data said.
Every factual claim gets a verdict and a reason. Code decides the numbers. Then the wording of each claim is checked on its own by an independent model from a different AI provider than the one that wrote the answer — it never scores the answer as a whole, and it can't overrule the math.
Your user gets the answer at full speed. Moments later the Accuracy Report lands — and if a number was wrong, the owner gets the fix in Slack before it reaches a deck.
The AI said strongest quarter yet. Your data said down 50%.
See a full Accuracy Report →| The error | Example | How Emet catches it |
|---|---|---|
| Wrong date range | ROAS for one week reported as the quarter | Query audit |
| Wrong attribution, time zone or currency | Last-click on a data-driven account; a date range off by one in the account's time zone; spend summed across currencies | Query audit |
| Wrong number | "Campaigns were ~26.8% of email volume." Actual: 98.7%. | Re-derivation |
| Bad math | A period-over-period change computed against the wrong prior period | Re-derivation |
| Overgeneralized | "Email was over 96% of revenue in August and YTD." True for August only. | Claim check |
| Invented cause | "The $13,867 gap is due to a 5-day attribution window." Nothing in the data says why. | Claim check |
ROAS for one week reported as the quarter
Last-click on a data-driven account; a date range off by one in the account's time zone; spend summed across currencies
"Campaigns were ~26.8% of email volume." Actual: 98.7%.
A period-over-period change computed against the wrong prior period
"Email was over 96% of revenue in August and YTD." True for August only.
"The $13,867 gap is due to a 5-day attribution window." Nothing in the data says why.
Examples from a one-week client case study at a multi-brand retailer.
Interpretive claims — opinions and recommendations — are deliberately not scored.
Eval tools check faithfulness to context. Emet checks truth against the source.
| LLM evaluation tools | Emet | |
|---|---|---|
| Checks the answer against | The context the model saw, or a test set you maintain | Your live source data, re-queried with its own read-only access |
| How | An LLM judge, or a scorer you write yourself | Deterministic re-derivation built in, per data source; an independent model checks the wording |
| Checks the query | Only if you write that check | Built in: dates, windows, time zones, currency, attribution |
| Output | A score per response or per test | A verdict and a reason per claim, with the math |
LLM evaluation tools: The context the model saw, or a test set you maintain
Emet: Your live source data, re-queried with its own read-only access
LLM evaluation tools: An LLM judge, or a scorer you write yourself
Emet: Deterministic re-derivation built in, per data source; an independent model checks the wording
LLM evaluation tools: Only if you write that check
Emet: Built in: dates, windows, time zones, currency, attribution
LLM evaluation tools: A score per response or per test
Emet: A verdict and a reason per claim, with the math
Keep your tracing. Langfuse, Arize Phoenix, LangSmith and Logfire keep working, and Emet runs alongside them.
See integrations →At onboarding we confirm every data source is connected and Emet can query each one, so it knows exactly what it's checking against.
ROAS, pipeline, margin — as your business defines them, not a generic default.
Fiscal quarters, attribution windows, time zones and currencies, mapped once.
Scroll → to read the full definitions
Example Slack alert · actions shown for reference
Slack — one alert per issue, not per report
Emet Observability Dashboard — every report, plus accuracy, usage and cost by team and model
Export — CSV
Read-only, scoped by you, revocable at once
Never in the request path — exports run after your user has the answer
Stores the trace, the claims, the verdicts and the query results behind them — never a copy of your tables.
Emet delivers deterministic verification for enterprise AI data analysis — in seconds, with a receipt.