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

Does Basedash show what people have asked and who asked each question?

Basedash let an admin see what both accounts had asked and identify the askers. Its Chats list contained the five questions sent, with no missing or extra questions.

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.

Usage view across two accountsPassEvidence
What we sent

Input 1 · Admin account: “As of September 2, 2026, what's our total revenue in the last 30 days?”

Input 2 · Admin account: “What's our most common payment method?”

Input 3 · Admin account: “How many complaints have we received on social media this month?”

Input 4 · Member account: “How many customers currently have an active subscription?”

Input 5 · Member account: “What's our net promoter score for last quarter?”

What the tool returned

Chats list in the admin view Chats: Last quarter's net p... / Active subscription... / Social media compl... / Most common pay... / Revenue in the last ... Member attribution: active subscriptions Ayush Ghosh / How many customers currently have an active subscription? Member attribution: net promoter score Ayush Ghosh / What's our net promoter score for last quarter?

Transcribed from Proof 1 · Screen recording at 0:00

Transcribed from Proof 1 · Screen recording at 0:30

Transcribed from Proof 1 · Screen recording at 0:38

Expected vs. Found
✓Expected: Show the five questions sent, attribute each to the account that asked it, and include no extra questions.Found: Five chats appeared for five questions sent. The admin's three questions appeared as its own messages; the member's two showed the member's name.
Supporting proof
Proof 1Screen recording
Screen recording: the admin's five-chat list and attribution inside each chat
Key moments
Open original ↗
Proof 2Screen recording
Screen recording: questions and asker names across the admin and member views
Key moments
Open original ↗
Proof 3Screen recording
Screen recording: the member sees the admin's revenue and payment-method chats
Key moments
Open original ↗
Proof 4Screenshot
Screenshot: Audit logs locked behind an Enterprise upgrade
Open original ↗
Proof 5Screenshot
Screenshot: Billing costs per account for 8–22 October 2026, not question counts
Open original ↗
Why this result

Although the admin's own questions had no name label, their presentation as the admin's own messages identified the asker. The member's questions displayed a name, so the five visible questions remained attributable, as required.

Also observed in this test case

Avatars in the sidebar. In the Chats sidebar, askers are identified by avatars rather than names. The five recent chats appear among the admin's older chats.

Attribution from the member account. In the member's view, the admin's revenue, payment-method and social-media complaint chats display the admin account's name.

Spending and audit access. Billing lists spending by account: $17.74 for the admin, $1.58 for the member and $7.38 for the system. Audit logs require an Enterprise upgrade.

Tested by Ayush Ghosh · evidence dated 15 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
Basedash
Build or version
Not exposed by the hosted product
Plan or tier
Free trial
Surface
Web app
Set up before the run
An admin and a member sent the revenue, payment-method, social-media complaint, active-subscription and net promoter score questions in one workspace, then the admin opened its Chats list.
Accounts
One admin and one member
Workspace
One organisation
Tested
15 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/basedash/user-question-audit · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-17

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 4 · Screenshot ↗image/png · 226 KB
Proof 5 · Screenshot ↗image/png · 281 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screen recordingfca494bafea131d4d197ff40f5ac2dfbb8677331d8c5b81ce115a513d49c0514
Proof 2 · Screen recording980a8f80469fe6f319e26e0207d2ce1b3dd76d3551f47a558317ca78d4a78ce4
Proof 3 · Screen recordingb61901f7b86c77133cfe124a128e0111c28cad5a82c2b5b856a6f9c1217d2711
Proof 4 · Screenshot8b3473f27c3683260e5be85e5b74148a94e8f80f4eb51c71d95152311e186079
Proof 5 · Screenshot779457df1cd983cec03ed0b9e3b9964ebe5c6d2d6fab2d7171059c2fb460b863