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

Can Draxlr find matches when users use different words for stored values?

Draxlr did not bridge the wording gap for the gift voucher request. It searched for those literal words and presented an empty result as the answer.

1 of 1 test case failed

Every test case in this scenario has a result.

Pass rate0%0 of 1 gradable
Coverage1 of 1test case with a result
0PassNo test case passed.
1FailMissed at least one thing it was expected to do; the reason and proof are with each test case below.
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.

Category asked by the user's synonymFailEvidence
What we sent

“Show me all orders paid with a gift voucher.”

What the tool returned

No orders matched payments with gift voucher. Try broadening the payment method search or checking a wider set of filters. This covers all time.

Transcribed from Proof 1 · Screenshot

Everything the tool returned, in order (3)
  1. Final response

    The final response, printed above.

  2. Generated query for the orders result · not part of the answer
    SELECT id, order_number, customer_id, placed_at, status, payment_method, currency, total_amount, discount_total, shipping_cost, city, state FROM public.orders WHERE payment_method ILIKE '%gift%voucher%' ORDER BY placed_at DESC
  3. SQL explanation panel · not part of the answer

    This returns all orders whose payment_method contains “gift voucher,” ordered from newest to oldest. This covers all time.

Expected vs. Found
✗Expected: Return orders matching the user's synonym for the stored payment method, rather than an empty result.Found: It returned no rows and told the user no orders matched the gift voucher request.
Supporting proof
Proof 1Screenshot
Screenshot: the gift voucher question, empty result, and literal payment-method filter
Open original ↗
Why this result

With no synonym mapping supplied, the literal gift voucher filter could not match the stored gift card payment method. The query ran successfully; presenting its empty result as the answer, rather than returning matching orders, is the failure here.

Also observed in this test case

Suggestion without a broader search. The chat reply suggested broadening the payment-method search, but Draxlr did not do so or suggest gift card as a candidate.

Tested by Ayush Ghosh · evidence dated 22 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
Stored value: the payment method had to be stored as gift card, with nothing mapping gift voucher to it.
AI customization
No fine-tuning or training context supplied
Tested
22 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
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/draxlr/the-users-wording-doesnt-match-how-the-values-are-stored · 0 pass · 1 fail · coverage 1/1 · graded 2026-10-22

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 · 89 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screenshot187cb8e08a352497952100c725c65cd0f5d2bb825d58d075025349b281ee88c9