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

Can AskYourDatabase show what people have been asking?

AskYourDatabase showed what people had asked and which account asked each question. Its usage list contained five entries for the five questions asked.

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 · Person 1 (admin): “As of September 2, 2026, what's our total revenue in the last 30 days?”

Input 2 · Person 1 (admin): “What's our most common payment method?”

Input 3 · Person 1 (admin): “How many complaints have we received on social media this month?”

The Person 2 (Member) account was used for this question.

Input 4 · Person 2 (Member): “How many customers currently have an active subscription?”

Input 5 · Person 2 (Member): “What's our net promoter score for last quarter?”

What the tool returned

Response 1 (Revenue calculation status) is a progress message the tool sent for Input 1; it is not part of the answer.

Response 2 (Revenue query) is the query the tool generated for Input 1; it is not part of the answer.

Response 3 answers Input 1.

Response 4 (Payment method check) is a progress message the tool sent for Input 2; it is not part of the answer.

Response 5 (Payment method query) is the query the tool generated for Input 2; it is not part of the answer.

Response 6 answers Input 2.

Response 7 answers Input 3.

Response 8 (Subscription count status) is a progress message the tool sent for Input 4; it is not part of the answer.

Response 9 (Active subscriptions query) is the query the tool generated for Input 4; it is not part of the answer.

Response 10 answers Input 4.

Response 11, the final response, answers Input 5.

I don't have access to any Net Promoter Score (NPS) data in this database. The available tables cover customers, orders, products, subscriptions, returns, tickets, and related operational data — but there's no survey or NPS feedback table. To calculate an NPS, I'd need data like customer survey responses (ratings 0–10) or promoter/detractor classifications, which aren't present here. Could you clarify: Is NPS data stored somewhere I'm not seeing (e.g., a different table or external system)? Or would you like me to look at a related metric I can compute, such as customer satisfaction signals from tickets/returns, or churn from subscription cancellations?

Transcribed from Proof 1 · Screen recording at 0:14

Every message the tool sent, in order (11)
  1. Revenue calculation status

    I'll calculate the total revenue from orders placed in the 30 days before September 2, 2026.

  2. Revenue query · not part of the answer
    SELECT COALESCE(SUM(total_amount), 0) AS total_revenue FROM orders WHERE placed_at >= '2026-08-03' AND placed_at < '2026-09-02' AND status <> 'cancelled'
  3. Revenue answer

    As of September 2, 2026, the total revenue in the last 30 days (August 3 – September 2, 2026) was $8,828.82. This figure excludes cancelled orders.

  4. Payment method check

    I'll check the payment methods used across orders to find the most common one.

  5. Payment method query · not part of the answer
    SELECT payment_method, COUNT(*) AS order_count FROM orders GROUP BY payment_method ORDER BY order_count DESC;
  6. Payment method answer

    Your most common payment method is card, used in 162 orders. Here's the full breakdown: Card 162, PayPal 42, Apple Pay 40, Affirm 27, Google Pay 23, Gift Card 14. Card payments account for more than half of all orders (162 out of 308 total).

  7. Social media complaints answer

    I don't have access to social media data in this database. The database contains tables for customers, orders, products, subscriptions, returns, tickets, and related records — but nothing tracking social media mentions or complaints. If you're looking for customer complaints, the closest match would be the tickets table, which tracks support issues. Would you like me to check how many support tickets were opened this month instead?

  8. Subscription count status

    I'll look up the number of customers with an active subscription.

  9. Active subscriptions query · not part of the answer
    SELECT COUNT(DISTINCT customer_id) AS active_subscription_customers FROM subscriptions WHERE status = 'active';
  10. Active subscriptions answer

    4 customers currently have an active subscription.

  11. Net promoter score answer

    The final response, printed above.

Expected vs. Found
✓Expected: Each question must appear under the account that asked it, with as many entries as questions asked.Found: The Messages page had five rows for five questions: three attributed to the admin account and two to the Member account.
Supporting proof
Proof 1Screen recording
Screen recording: four question-and-answer exchanges and the question list from both accounts
Key moments
Open original ↗
Proof 2Screenshot
Screenshot: five attributed questions and the social-media complaints exchange
Open original ↗
Why this result

The five entries met the requirement for a complete, attributed list. A displayed count was not required, so its absence did not prevent a pass.

Also observed in this test case

Member access to admin questions. A Member with view-and-query access can see the admin's questions with the admin's account identity label.

Unanswered questions look alike. In the Messages list, the social-media complaints and net promoter score questions have no unanswered marker. The admin must open each row to see the response.

Tested by Ayush Ghosh · evidence dated 7 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
AskYourDatabase
Build or version
Not exposed by the hosted product
Surface
Web app
Set up before the run
An admin and a Member account were to ask about revenue, payment methods, social-media complaints, active subscriptions and net promoter score in separate chats on a shared agent, then open its usage view.
Sharing
one shared bot with two accounts
Chat isolation
each question was asked in its own new chat
Account roles
admin and Member
Tested
7 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
10 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/askyourdatabase/user-question-audit · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-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 2 · Screenshot ↗image/png · 239 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screen recording81ccb36e75b2c9a6681bdc6406e154992d582c7430c2583608dc24d75ba3eddf
Proof 2 · Screenshot5a844f04cb894d74c94b75530322bc998d158034c2e133d82460945e4164343e