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

Can Nanonets aggregate a value across multiple documents?

Nanonets combined the amounts due from all three documents into the expected total of 474.93. The calculation left out no document and added no value from outside the set.

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.

Total across every documentPassEvidence
What we sent

“What is the total of total_due summed across all three documents? Return the result as JSON.”

Input 1Document (PDF)
Input PDF: boiler-inspection receipt with a total of $90.10
Open the PDF ↗
Input 2Document (PDF)
Input PDF: refrigerator-repair invoice with an amount due of $227.33
Open the PDF ↗
Input 3Document (PDF)
Input PDF: drain-service receipt with a total due of USD 157.50
Open the PDF ↗
What the tool returned

Nothing further is required for the original request: the summed total_due was already calculated and returned as JSON. If continuing, the next step would only be to confirm or reuse the result {"total_total_due":474.93}. المصدر

Transcribed from Proof 1 · Screenshot

Output file (JSON)
Returned JSON: the combined total of 474.93
Cited values1 value from this file
total_total_due
474.93
Show the whole file (1 KB)
JSON
{
  "total_total_due": 474.93
}
Open the JSON file ↗
Expected vs. Found
✓Expected: A total of 474.93 from the product’s extracted amounts across all three documents, with none omitted and no outside values added.Found: It returned 474.93; the reference sum of its extracted amounts was 474.93. It did not refuse the request.
Supporting proof
Proof 1Screenshot
Screenshot: the three uploaded documents, the sum request and Nanonets’ chat answer
Open original ↗
Why this result

The task chat returned a total equal to the sum of Nanonets’ own extractions across the three intended documents. The boiler-inspection receipt’s 90.10 contribution is accounted for by subtraction; the screenshot does not show its extracted amount.

Also observed in this test case

Extra word after JSON. The final chat answer appended a stray Arabic word after the JSON; the returned value was unchanged.

Tested by Rugved Nichite · evidence dated 11 September 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
Nanonets
Build or version
Not exposed by the hosted product
Surface
Web app
Set up before the run
The boiler-inspection receipt, refrigerator-repair invoice and drain-service receipt had to supply extracted amounts due; the reference total had to be calculated from Nanonets’ returned values, not the original documents.
Tested
11 September 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
CapabilityQuerying →
ScenarioAggregate across documents →
ToolNanonets →

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
17 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/nanonets/aggregate-across-documents · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-16

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 · 7 KB
Input 2 · Document (PDF) ↗application/pdf · 8 KB
Input 3 · Document (PDF) ↗application/pdf · 7 KB
Output file (JSON) ↗application/json · 0 KB
Proof 1 · Screenshot ↗image/png · 226 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input 1 · Document (PDF)1f464ae863aadb1682805b8ee3fdd8b368a2ddd4e0f602e1cb194640b9253302
Input 2 · Document (PDF)4a0b1754da9f52ce35a783d58f8e8a1b5e1353b5b992d5553122886f1cd4a638
Input 3 · Document (PDF)0276d246d69482340b53797f4eaa21831977cede22c8c8f14fc48dbf84757660
Output file (JSON)30ac2b38ea0209c905bc7eeef40bb17599c33cdd768409f8b2c7393dee09fa4c
Proof 1 · Screenshot92aed0ce842016e59cd490dc65251537bf0ced81e50133bc65d1ce94965095d7