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

Can LlamaParse return a value that is directly available in the document?

LlamaParse correctly extracted the directly available receipt number as text. It also returned subtotal, tax and total due as $85.00, $5.10 and $90.10, respectively—the same amounts printed on the receipt.

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.

Plainly-labelled scalar fieldPassEvidence
What we sent

We uploaded a one-page service receipt to the LlamaCloud Extract web app and supplied a schema requesting the receipt number, subtotal, tax and total due as required text fields.

Input 1Document (PDF)
Input PDF: the service receipt with its labelled receipt number and amounts
Open the PDF ↗
Input 2File (JSON)
Input schema: four required text fields and their descriptions
JSON
{
  "type": "object",
  "properties": {
    "receipt_number": {
      "type": "string",
      "description": "The receipt's identifying number, labelled 'RECEIPT NO'"
    },
    "subtotal": {
      "type": "string",
      "description": "The subtotal amount before tax"
    },
    "tax": {
      "type": "string",
      "description": "The tax amount"
    },
    "total_due": {
      "type": "string",
      "description": "The total amount due"
    }
  },
  "required": ["receipt_number", "subtotal", "tax", "total_due"]
}
Open the JSON file ↗
What the tool returned
JSON
{"receipt_number": "RHS-70234", "subtotal": "$85.00", "tax": "$5.10", "total_due": "$90.10"}

JSON output: the four extracted values, returned as text.

Copied from Output file (JSON), lines 9–14

Open the JSON file ↗
Expected vs. Found
✓Expected: The receipt number, returned with the correct value and data type.Found: The receipt number was returned as text without label text, with a page-1 citation pointing to the number.
Supporting proof
Proof 1Screenshot
Results screenshot: the uploaded receipt beside four extracted fields
Open original ↗
Why this result

Extract is LlamaParse’s feature for returning named fields, and the receipt and required schema were both supplied. It returned the printed receipt number in the required text type without its label.

Also observed in this test case

Tax confidence warning. The tax field was highlighted in amber at confidence 0.8956, below the 90% threshold.

Tested by Rugved Nichite · evidence dated 29 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
LlamaParse
Build or version
LlamaCloud web app (build v9bc3d1a1); Extract, Agentic tier
Plan or tier
Free plan (20,000 credits)
Surface
Web app
Set up before the run
A service receipt had to show its receipt number once under a plain label, with no competing same-type value nearby. The schema requested receipt number, subtotal, tax and total due; the receipt number was the target value.
Confidence threshold
90%
Tested
29 October 2026 · Rugved Nichite

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
BenchmarkStructured Document Extraction →19 scenarios · 10 tools
CapabilityField Extraction →
ScenarioThe value is directly available →
ToolLlamaParse →

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 publishedStructured Document Extraction 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/structured-document-extraction/results/llamaparse/the-value-is-directly-available · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-02

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.

Input 1 · Document (PDF) ↗application/pdf · 54 KB
Input 2 · File (JSON) ↗application/json · 1 KB
Output file (JSON) ↗text/plain; charset=utf-8 · 3 KB
Proof 1 · Screenshot ↗image/png · 106 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input 1 · Document (PDF)a96bbe1c5b22336e7b54169baf72b85e45eabf1312cd293a1821017b52fa85f7
Input 2 · File (JSON)45bffd9608cec9544f067bb7b8ffe9cf61c7f52a32aed6f5232abb6cf280c152
Output file (JSON)b86827f611bfba06d54dcdaf6aa53a92f1b81084b66f0e4d8231787f14ea7c7d
Proof 1 · Screenshotabcf64c32860fb612b5bd0336b494ee1539cac94ee14e5f217164faad848b39a