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

Does camelAI state a plain fact or short list directly in its reply?

camelAI stated the single value in its reply, 308 orders in total, with no chart or one-cell table. Its own count query and a separate reference query on the same database both return 308.

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.

Single value stated, not chartedPassEvidence
What we sent

“How many total orders have we ever received?”

What the tool returned

We've received 308 orders in total, counting all records in the orders table. Each has a unique order ID.

Transcribed from Proof 1 · Screenshot

Expected vs. Found
✓Expected: The value is stated in the reply, not returned only as a chart or a one-cell table.Found: The reply states "We've received 308 orders in total", with no chart or table; the reference query also counts 308 orders.
Supporting proof
Proof 1Screenshot
Chat screenshot: the order-count question and camelAI's one-sentence answer
Open original ↗
Proof 2Screenshot
Chat screenshot: the count query camelAI ran and its result of 308
Open original ↗
Proof 3Screenshot
Reference query screenshot: the same order count, 308
Open original ↗
Proof 4Screen recording
Screen recording: walkthrough of the chat and the reference query
Key moments
Open original ↗
Why this result

The test needed the value stated in the reply; returning it only as a chart or a one-cell table would fail. camelAI answered in a sentence, and its 308 matches the reference count.

Also observed in this test case

Checked order ids are unique. In the same query, camelAI also counted distinct order ids, 308, so it checked each order was unique before answering.

Many steps for one number. It took just over a minute and 12 steps to answer a one-number question, most of them reading its bundled data-analysis skill and inspecting the schema.

Tested by Anchal Rana · 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
camelAI
Build or version
Not exposed by the hosted product
Plan or tier
Free
Surface
Web app
Set up before the run
A single-value answer was required.
Tested
27 October 2026 · Anchal Rana

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.

LevelNameScope
BenchmarkAI Database Agents →28 scenarios · 11 tools
CapabilityAnswer Presentation →
ScenarioThe answer is a plain fact or a short list →
ToolcamelAI →

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
16 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/camelai/plain-fact-or-short-list · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-27

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 1 · Screenshot ↗image/png · 216 KB
Proof 2 · Screenshot ↗image/png · 414 KB
Proof 3 · Screenshot ↗image/png · 81 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screenshota6b76f5b77b4d645443466f06bb0771095c27aee044fd3d29fd145a3f46cc3e7
Proof 2 · Screenshotca7b1ebf03393547c20f8f017fa3193ed8cb891ed7ec38b0f67e7c41acba9105
Proof 3 · Screenshot76ec99afa3b7266beadca1e83b34e466c6cfb6fbb70b95a526696a1f1473002f
Proof 4 · Screen recording56c10f2ea1f541ba840a1f10af7193476c60ccced7703ace06ed565f905335c6