AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 16 November 2026

Can Draxlr help an operator find and inspect an exchange after a user reports a bad answer?

Draxlr let the admin find and inspect the reported exchange in saved chats. The opened conversation exposed the original question and response, with the SQL query and its explanation available alongside them.

1 of 1 test case passed

Every test case in this scenario has a result.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

The test case

Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.

Find a complained-about exchangePassEvidence
What we sent

We typed the complaint’s topic word into Search chats in the saved-chat sidebar.

What the tool returned

We've received 0 social media complaints this month.

Transcribed from Proof 1 · Screen recording at 0:13

Expected vs. Found
✓Expected: The reported exchange can be located and inspected, including the original question and response.Found: The social-media complaints conversation opened with its original question, stored response, result card, SQL query and explanation.
Supporting proof
Proof 1Screen recording
Screen recording: searching saved chats and inspecting the social-media complaints exchange
Key moments
Open original ↗
Proof 2Screenshot
Screenshot: workspace members and the current account’s admin access
Open original ↗
Why this result

The admin’s topic-word search narrowed saved chats to the right conversation, exposing the question, asker on hover, answer and SQL. This met the requirement to find and inspect the exchange. It was the admin’s own exchange; access to another member’s chats is not shown.

Also observed in this test case

Conversation title matching. Search matched the title of the social-media complaints conversation.

No asker in search results. For the social-media complaints exchange, the asker’s name was absent from the search results and sidebar list.

Tested by Ayush Ghosh · evidence dated 27 October 2026

Configuration and setup

How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.

Software that produced the output
Draxlr
Build or version
Not exposed by the hosted product
Plan or tier
Premium
Model
gpt-5.5-1
Surface
Web app
Set up before the run
The exchange had to be found from a rough clue, here the topic of the complaint. The target was the admin’s earlier question about this month’s social-media complaints.
Signed-in role
Admin Access
Tested
27 October 2026 · Ayush Ghosh

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.

The rules
  • Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
  • Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
  • Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.

Where this sits in the benchmark

This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.

History of this result

What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.

from the publication record
18 November 2026First publishedAI Database Agents v1

Act on this result

Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/ai-database-agents/results/draxlr/find-reported-bad-answer · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-16

The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.

Verify the proof files

These files support this result. Open a file to inspect the original evidence.

Proof 2 · Screenshot ↗image/png · 99 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screen recording7dfe93544602c0b3105d9771019a51e29079965bb06dd80277a34cc4c33e07ee
Proof 2 · Screenshot9312d727587a97c90934f4da3f60c13efaef222a34cb9b3d560e70955f76e902