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.
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
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?”
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: 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. |
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.
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.
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.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
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.
- 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.
| Level | Name | Scope |
|---|---|---|
| Benchmark | AI Database Agents → | 28 scenarios · 11 tools |
| Capability | Analytics & Observability → | |
| Scenario | Someone needs to see what people have been asking → | |
| Tool | Basedash → |
Global scenario definition → · Global capability definition → · Basedash product page →
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.
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.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →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.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.