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

Can LlamaParse keep code blocks intact in Markdown?

LlamaParse returned both code listings in the document as fenced blocks tagged as Python and shell, and kept the Python body at its three indent levels of 4, 8 and 12 spaces. Two small whitespace differences remain inside the fences: one blank line was dropped, and the shell continuation line sits at four spaces rather than six.

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.

Code block — fenced, structure intactPassEvidence
What we sent

We uploaded the complete three-page PDF in one request to LlamaParse's Parse API v2 and kept the Markdown it returned.

InputDocument (PDF)
Input PDF: the three-page operations note, with a Python and a shell listing on page 2
Open the PDF ↗
What the tool returned

Returned Markdown: the fenced Python and shell listings with their indentation

Copied from Output file (Markdown), lines 36–49

Markdown
```python
from tarnbeck.stations import Export, reload_window

def reload_after_reset(station, reset_at):
    export = Export.open(station)
    window = reload_window(reset_at, margin_minutes=45)

    for block in export.blocks(window):
        if block.checksum_ok():
            continue
        export.requeue(block, reason="gauge reset")

    return export.commit(dry_run=False)
```
Open the Markdown file ↗

Whitespace view of the returned Python block: $ marks each line end, so indents show

Copied from Captured file (text), lines 1–10

Text
def reload_after_reset(station, reset_at):$
    export = Export.open(station)$
    window = reload_window(reset_at, margin_minutes=45)$
$
    for block in export.blocks(window):$
        if block.checksum_ok():$
            continue$
        export.requeue(block, reason="gauge reset")$
$
    return export.commit(dry_run=False)$
Open the text file ↗
Output file (JSON)
API response: the completed job and the same Markdown it returned
Cited values3 values from this file
job › tier
agentic
markdown_full
Tarnbeck Institute of Hydrology · Data Services ## Reloading a station export after a gauge reset Operations note DS/OP/07 · Data services · Reviewed 14 January 2026 *** ### Symptoms The station's daily total is short and the loader's own log says nothing is wrong. In the log the day looks like a clean run: the export was fetched, every block was read, and the summary line reports fewer readings than the station's counter did. The gap is always at the end of the day rather than the beginning, and it is always a whole number of blocks. The other sign is a duplicate warning in the block log, with two entries carrying the same sequence number and different checksums. One warning is normal after a reset. A run of them means the reset happened part way through the day and everything after it is being rejected block by block. ### Why the loader rejects the second block Block sequence numbers come from the station and not from the loader. The loader keeps the highest number it has committed for the day and treats anything at or below it as a repeat, which is the right thing to do on a poor link: a station that retransmits sends the same block twice, and the loader must not count it twice. A reset returns the counter to zero, so the blocks after it carry sequence numbers the loader has already committed. Nothing about them looks new and the loader discards them for exactly the reason it should. The reset time is the only thing that distinguishes a continuation from a repeat, and the loader does not know it unless it is told. ### The fix When a gauge is reset in the field the station's counter returns to zero, and the export for that day contains two blocks carrying the same sequence number. The loader accepts the first and rejects the second. That is the right behaviour for a duplicated transmission and the wrong behaviour here, and the day's record ends up short by however much arrived after the reset. The fix is to requeue the affected blocks with the reset time supplied, so that the loader treats the second block as a continuation rather than a repeat. The function below is the one to call. It lives in `tarnbeck.stations.maintenance` and is safe to run more than once: a block that already carries a good checksum is skipped. DS/OP/07 · Data services Page 1 of 3 --- Tarnbeck Institute of Hydrology · Data Services DS/OP/07 ```python from tarnbeck.stations import Export, reload_window def reload_after_reset(station, reset_at): export = Export.open(station) window = reload_window(reset_at, margin_minutes=45) for block in export.blocks(window): if block.checksum_ok(): continue export.requeue(block, reason="gauge reset") return export.commit(dry_run=False) ``` Run it from the loader host and not from a workstation, and take the reset time from the field log rather than from the station clock, which is the thing that was wrong. The margin defaults to forty-five minutes either side of the reset; widen it only if the field log is vague about the time, because a wide window requeues blocks that were never in doubt. If commit returns a count lower than the number of blocks in the window, stop there and raise it with data services before running anything again. A short count means blocks were rejected for a second reason, and requeuing them repeatedly will not find out what it was. ## Running it Run it from the loader host, in the maintenance environment, with the station code and the reset time as they appear in the field log: ```bash $ ssh loader-01.tarnbeck.example $ tarnbeck-maint reload-after-reset --station VQ1 \ --reset-at '2026-01-29T09:15' --confirm ``` The command prints the window it will use, the number of blocks in it and the number it intends to requeue, and then waits. Read the three numbers before answering. If the window is wider than the field log justifies, stop and narrow it rather than letting it run. Without `--confirm` the command does everything except commit, which is the safe way to see what it would do. The dry run takes a few seconds and there is no reason to skip it. ## Afterwards Check the day's totals against the gauge's own counter before closing the ticket. The loader reports the number of blocks committed and not the number of readings, and a day can come back with the right number of blocks and the wrong number of readings if a block was truncated in the field. Note the reset in the station log, with the time taken from the field log and not the time the reload ran. The next person to look at a gap in the series will look there first, and a reload with nothing written beside it is indistinguishable from a gap nobody has dealt with. DS/OP/07 · Data services Page 2 of 3 --- Tarnbeck Institute of Hydrology · Data Services DS/OP/07 ### If the count is short A short count means blocks were rejected for a second reason and the reload has not found out what it was. Do not run it again: a second pass requeues the same blocks, reports the same count, and fills the log with attempts that bury the original failure. Take the sequence numbers the command reports as rejected and look them up in the block log. A checksum failure on a block truncated in the field cannot be fixed by reloading and needs the station visited. A rejection with no reason recorded is a loader fault, and goes to data services with the run's log attached. ### The block header, for reference Each block in an export begins with a fixed header, which is what the loader reads to decide whether it has seen the block before: ``` SEQ=00184 STATION=VQ1 START=2026-01-29T08:45Z COUNT=0180 INTERVAL=15s CRC=8f2a41d6 ``` SEQ is the station's counter and is the field a reset returns to zero. START is the station clock, which is not to be trusted after a reset - which is why the reset time comes from the field log and not from the export. CRC covers the readings and not the header, so a block with a good checksum and a wrong sequence number is possible and is exactly what a reset produces. Nothing in the header says a reset happened. ### Rolling back A committed reload can be undone within the same day by reverting the station's day to the snapshot the loader takes before it commits. The snapshot is kept for seven days and is named for the run. After seven days the only route back is a fresh fetch of the export from the station, which is possible while the station's own buffer still holds the day - about three weeks - and impossible afterwards. A reload that has committed and cannot be rolled back is an incident and is raised as one, whatever the size of the gap. DS/OP/07 · Data services Page 3 of 3
job › created_at
2026-09-10T13:27:43.140363Z
Show the whole file (16 KB)
JSON
{
  "job": {
    "user_metadata": null,
    "id": "pjb-yy2gywxvjklesmyie200z2pc2w5q",
    "created_at": "2026-09-10T13:27:43.140363Z",
    "updated_at": "2026-09-10T13:27:57.483192Z",
    "project_id": "f2cfef38-e7e3-4955-be62-16148c6f1b96",
    "status": "COMPLETED",
    "error_message": null,
    "name": "operations_note_DS-OP-07.pdf",
    "tier": "agentic",
    "usage": {
      "credits": 30.0
    }
  },
  "result_content_metadata": null,
  "text": null,
  "markdown": {
    "pages": [
      {
        "page_number": 1,
        "markdown": "Tarnbeck Institute of Hydrology \u00b7 Data Services\n\n## Reloading a station export after a gauge reset\n\nOperations note DS/OP/07 \u00b7 Data services \u00b7 Reviewed 14 January 2026\n\n***\n\n### Symptoms\n\nThe station's daily total is short and the loader's own log says nothing is wrong. In the log the day looks like a clean run: the export was fetched, every block was read, and the summary line reports fewer readings than the station's counter did. The gap is always at the end of the day rather than the beginning, and it is always a whole number of blocks.\n\nThe other sign is a duplicate warning in the block log, with two entries carrying the same sequence number and different checksums. One warning is normal after a reset. A run of them means the reset happened part way through the day and everything after it is being rejected block by block.\n\n### Why the loader rejects the second block\n\nBlock sequence numbers come from the station and not from the loader. The loader keeps the highest number it has committed for the day and treats anything at or below it as a repeat, which is the right thing to do on a poor link: a station that retransmits sends the same block twice, and the loader must not count it twice.\n\nA reset returns the counter to zero, so the blocks after it carry sequence numbers the loader has already committed. Nothing about them looks new and the loader discards them for exactly the reason it should. The reset time is the only thing that distinguishes a continuation from a repeat, and the loader does not know it unless it is told.\n\n### The fix\n\nWhen a gauge is reset in the field the station's counter returns to zero, and the export for that day contains two blocks carrying the same sequence number. The loader accepts the first and rejects the second. That is the right behaviour for a duplicated transmission and the wrong behaviour here, and the day's record ends up short by however much arrived after the reset.\n\nThe fix is to requeue the affected blocks with the reset time supplied, so that the loader treats the second block as a continuation rather than a repeat. The function below is the one to call. It lives in `tarnbeck.stations.maintenance` and is safe to run more than once: a block that already carries a good checksum is skipped.",
        "footer": "DS/OP/07 \u00b7 Data services Page 1 of 3",
        "success": true
      },
      {
        "page_number": 2,
        "markdown": "```python\nfrom tarnbeck.stations import Export, reload_window\n\ndef reload_after_reset(station, reset_at):\n    export = Export.open(station)\n    window = reload_window(reset_at, margin_minutes=45)\n\n    for block in export.blocks(window):\n        if block.checksum_ok():\n            continue\n        export.requeue(block, reason=\"gauge reset\")\n\n    return export.commit(dry_run=False)\n```\n\nRun it from the loader host and not from a workstation, and take the reset time from the field log rather than from the station clock, which is the thing that was wrong. The margin defaults to forty-five minutes either side of the reset; widen it only if the field log is vague about the time, because a wide window requeues blocks that were never in doubt.\n\nIf commit returns a count lower than the number of blocks in the window, stop there and raise it with data services before running anything again. A short count means blocks were rejected for a second reason, and requeuing them repeatedly will not find out what it was.\n\n## Running it\n\nRun it from the loader host, in the maintenance environment, with the station code and the reset time as they appear in the field log:\n\n```bash\n$ ssh loader-01.tarnbeck.example\n$ tarnbeck-maint reload-after-reset --station VQ1 \\\n    --reset-at '2026-01-29T09:15' --confirm\n```\n\nThe command prints the window it will use, the number of blocks in it and the number it intends to requeue, and then waits. Read the three numbers before answering. If the window is wider than the field log justifies, stop and narrow it rather than letting it run.\n\nWithout `--confirm` the command does everything except commit, which is the safe way to see what it would do. The dry run takes a few seconds and there is no reason to skip it.\n\n## Afterwards\n\nCheck the day's totals against the gauge's own counter before closing the ticket. The loader reports the number of blocks committed and not the number of readings, and a day can come back with the right number of blocks and the wrong number of readings if a block was truncated in the field.\n\nNote the reset in the station log, with the time taken from the field log and not the time the reload ran. The next person to look at a gap in the series will look there first, and a reload with nothing written beside it is indistinguishable from a gap nobody has dealt with.",
        "header": "Tarnbeck Institute of Hydrology \u00b7 Data Services DS/OP/07",
        "footer": "DS/OP/07 \u00b7 Data services Page 2 of 3",
        "success": true
      },
      {
        "page_number": 3,
        "markdown": "### If the count is short\n\nA short count means blocks were rejected for a second reason and the reload has not found out what it was. Do not run it again: a second pass requeues the same blocks, reports the same count, and fills the log with attempts that bury the original failure.\n\nTake the sequence numbers the command reports as rejected and look them up in the block log. A checksum failure on a block truncated in the field cannot be fixed by reloading and needs the station visited. A rejection with no reason recorded is a loader fault, and goes to data services with the run's log attached.\n\n### The block header, for reference\n\nEach block in an export begins with a fixed header, which is what the loader reads to decide whether it has seen the block before:\n\n```\nSEQ=00184 STATION=VQ1 START=2026-01-29T08:45Z\nCOUNT=0180 INTERVAL=15s CRC=8f2a41d6\n```\n\nSEQ is the station's counter and is the field a reset returns to zero. START is the station clock, which is not to be trusted after a reset - which is why the reset time comes from the field log and not from the export.\n\nCRC covers the readings and not the header, so a block with a good checksum and a wrong sequence number is possible and is exactly what a reset produces. Nothing in the header says a reset happened.\n\n### Rolling back\n\nA committed reload can be undone within the same day by reverting the station's day to the snapshot the loader takes before it commits. The snapshot is kept for seven days and is named for the run.\n\nAfter seven days the only route back is a fresh fetch of the export from the station, which is possible while the station's own buffer still holds the day - about three weeks - and impossible afterwards. A reload that has committed and cannot be rolled back is an incident and is raised as one, whatever the size of the gap.",
        "header": "Tarnbeck Institute of Hydrology \u00b7 Data Services DS/OP/07",
        "footer": "DS/OP/07 \u00b7 Data services Page 3 of 3",
        "success": true
      }
    ]
  },
  "items": null,
  "metadata": {
    "pages": [
      {
        "page_number": 1,
        "confidence": 0.998,
        "original_orientation_angle": 0,
        "cost_optimized": false,
        "triggered_auto_mode": false
      },
      {
        "page_number": 2,
        "confidence": 0.988,
        "original_orientation_angle": 0,
        "cost_optimized": false,
        "triggered_auto_mode": false
      },
      {
        "page_number": 3,
        "confidence": 0.994,
        "original_orientation_angle": 0,
        "cost_optimized": false,
        "triggered_auto_mode": false
      }
    ],
    "document": {}
  },
  "forms": null,
  "markdown_full": "Tarnbeck Institute of Hydrology \u00b7 Data Services\n\n## Reloading a station export after a gauge reset\n\nOperations note DS/OP/07 \u00b7 Data services \u00b7 Reviewed 14 January 2026\n\n***\n\n### Symptoms\n\nThe station's daily total is short and the loader's own log says nothing is wrong. In the log the day looks like a clean run: the export was fetched, every block was read, and the summary line reports fewer readings than the station's counter did. The gap is always at the end of the day rather than the beginning, and it is always a whole number of blocks.\n\nThe other sign is a duplicate warning in the block log, with two entries carrying the same sequence number and different checksums. One warning is normal after a reset. A run of them means the reset happened part way through the day and everything after it is being rejected block by block.\n\n### Why the loader rejects the second block\n\nBlock sequence numbers come from the station and not from the loader. The loader keeps the highest number it has committed for the day and treats anything at or below it as a repeat, which is the right thing to do on a poor link: a station that retransmits sends the same block twice, and the loader must not count it twice.\n\nA reset returns the counter to zero, so the blocks after it carry sequence numbers the loader has already committed. Nothing about them looks new and the loader discards them for exactly the reason it should. The reset time is the only thing that distinguishes a continuation from a repeat, and the loader does not know it unless it is told.\n\n### The fix\n\nWhen a gauge is reset in the field the station's counter returns to zero, and the export for that day contains two blocks carrying the same sequence number. The loader accepts the first and rejects the second. That is the right behaviour for a duplicated transmission and the wrong behaviour here, and the day's record ends up short by however much arrived after the reset.\n\nThe fix is to requeue the affected blocks with the reset time supplied, so that the loader treats the second block as a continuation rather than a repeat. The function below is the one to call. It lives in `tarnbeck.stations.maintenance` and is safe to run more than once: a block that already carries a good checksum is skipped.\n\nDS/OP/07 \u00b7 Data services Page 1 of 3\n\n\n---\n\n\n\nTarnbeck Institute of Hydrology \u00b7 Data Services DS/OP/07\n\n```python\nfrom tarnbeck.stations import Export, reload_window\n\ndef reload_after_reset(station, reset_at):\n    export = Export.open(station)\n    window = reload_window(reset_at, margin_minutes=45)\n\n    for block in export.blocks(window):\n        if block.checksum_ok():\n            continue\n        export.requeue(block, reason=\"gauge reset\")\n\n    return export.commit(dry_run=False)\n```\n\nRun it from the loader host and not from a workstation, and take the reset time from the field log rather than from the station clock, which is the thing that was wrong. The margin defaults to forty-five minutes either side of the reset; widen it only if the field log is vague about the time, because a wide window requeues blocks that were never in doubt.\n\nIf commit returns a count lower than the number of blocks in the window, stop there and raise it with data services before running anything again. A short count means blocks were rejected for a second reason, and requeuing them repeatedly will not find out what it was.\n\n## Running it\n\nRun it from the loader host, in the maintenance environment, with the station code and the reset time as they appear in the field log:\n\n```bash\n$ ssh loader-01.tarnbeck.example\n$ tarnbeck-maint reload-after-reset --station VQ1 \\\n    --reset-at '2026-01-29T09:15' --confirm\n```\n\nThe command prints the window it will use, the number of blocks in it and the number it intends to requeue, and then waits. Read the three numbers before answering. If the window is wider than the field log justifies, stop and narrow it rather than letting it run.\n\nWithout `--confirm` the command does everything except commit, which is the safe way to see what it would do. The dry run takes a few seconds and there is no reason to skip it.\n\n## Afterwards\n\nCheck the day's totals against the gauge's own counter before closing the ticket. The loader reports the number of blocks committed and not the number of readings, and a day can come back with the right number of blocks and the wrong number of readings if a block was truncated in the field.\n\nNote the reset in the station log, with the time taken from the field log and not the time the reload ran. The next person to look at a gap in the series will look there first, and a reload with nothing written beside it is indistinguishable from a gap nobody has dealt with.\n\nDS/OP/07 \u00b7 Data services Page 2 of 3\n\n\n---\n\n\n\nTarnbeck Institute of Hydrology \u00b7 Data Services DS/OP/07\n\n### If the count is short\n\nA short count means blocks were rejected for a second reason and the reload has not found out what it was. Do not run it again: a second pass requeues the same blocks, reports the same count, and fills the log with attempts that bury the original failure.\n\nTake the sequence numbers the command reports as rejected and look them up in the block log. A checksum failure on a block truncated in the field cannot be fixed by reloading and needs the station visited. A rejection with no reason recorded is a loader fault, and goes to data services with the run's log attached.\n\n### The block header, for reference\n\nEach block in an export begins with a fixed header, which is what the loader reads to decide whether it has seen the block before:\n\n```\nSEQ=00184 STATION=VQ1 START=2026-01-29T08:45Z\nCOUNT=0180 INTERVAL=15s CRC=8f2a41d6\n```\n\nSEQ is the station's counter and is the field a reset returns to zero. START is the station clock, which is not to be trusted after a reset - which is why the reset time comes from the field log and not from the export.\n\nCRC covers the readings and not the header, so a block with a good checksum and a wrong sequence number is possible and is exactly what a reset produces. Nothing in the header says a reset happened.\n\n### Rolling back\n\nA committed reload can be undone within the same day by reverting the station's day to the snapshot the loader takes before it commits. The snapshot is kept for seven days and is named for the run.\n\nAfter seven days the only route back is a fresh fetch of the export from the station, which is possible while the station's own buffer still holds the day - about three weeks - and impossible afterwards. A reload that has committed and cannot be rolled back is an incident and is raised as one, whatever the size of the gap.\n\nDS/OP/07 \u00b7 Data services Page 3 of 3\n",
  "text_full": null,
  "images_content_metadata": {
    "total_count": 0,
    "images": []
  },
  "job_metadata": {
    "state_transitions": {
      "pending_at": "2026-09-10T13:27:43.133828Z",
      "throttled_at": "2026-09-10T13:27:43.302040Z",
      "running_at": "2026-09-10T13:27:43.460361Z",
      "completed_at": "2026-09-10T13:27:57.485693Z",
      "failed_at": null,
      "cancelled_at": null
    },
    "quarantine": null,
    "pdf-pages": 3,
    "pdf-real-pages": 3,
    "pdf-rawTextLength": 6671,
    "pdf-mdLength": 6683,
    "pdf-time": 7797,
    "pdf-ocrTime": 0,
    "pdf-image-convertTime": 0,
    "pdf-pdfToHTMLTime": 0,
    "pdf-llmTime": 6393,
    "pdf-inputTokens": 55579,
    "pdf-outputTokens": 1981,
    "pdf-image-ocr-count": 0,
    "pdf-image-ocr-failed-count": 0,
    "pdf-image-ocr-success-count": 3,
    "pdf-image-ocr-empty-count": 3,
    "pdf-image-ocr-hadText-count": 0,
    "pdf-image-ocr-pixels": 21724800,
    "pdf-multimodal-time": 0,
    "pdf-multimodal-pdf2Image": 0,
    "pdf-high-res-ocr": 3
  },
  "raw_parameters": null,
  "debug": null
}
Open the JSON file ↗
Expected vs. Found
✓Expected: The code comes back as a fenced or preformatted block, with its line breaks and indentation intact.Found: Both listings were fenced and tagged as Python and shell, with the Python body at 4, 8 and 12 spaces as in the source. One blank line was dropped; the shell continuation sits at four spaces, not six.
Supporting proof
Proof 1Screenshot
Run card: the complete PDF sent in one request on the default pipeline
Open original ↗
Why this result

It is a Pass because both listings come back fenced with their line breaks, and the Python body keeps its 4, 8 and 12-space indentation. The returned Markdown and the whitespace view show this. The dropped blank line and shorter shell indent sit inside intact fenced blocks, so the blocks remain structured.

Also observed in this test case

Heading levels vary. Headings styled the same in the source came back at different levels: three page-1 headings as third-level headings, and page 2's 'Running it' and 'Afterwards' as second-level headings.

Tested by Chandresh Bisht · evidence dated 10 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
LlamaParse
Build or version
Parse API v2, tier agentic, version latest (build not exposed)
Plan or tier
free tier
Surface
API
Set up before the run
The complete three-page operations note was sent in one request. Its second page holds a Python listing indented at three levels and a shell listing with an indented continuation line. LlamaParse ran its default pipeline in one pass.
Tested
10 September 2026 · Chandresh Bisht

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
17 November 2026First publishedConverting a complex PDF into clean Markdown with a hosted API 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/pdf-to-markdown-apis/results/llamaparse/a-document-containing-a-code-block · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-30

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 · Document (PDF) ↗application/pdf · 78 KB
Output file (Markdown) ↗text/markdown; charset=utf-8 · 7 KB
Captured file (text) ↗text/plain; charset=utf-8 · 0 KB
Output file (JSON) ↗application/json · 16 KB
Proof 1 · Screenshot ↗image/png · 90 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)cd27d1e77ec9818ff769bde1b49d95e711373888507af4b007054c27b7a52db8
Output file (Markdown)4b8e9cf2aa75d966cc282cf82adfa36eede373443748b472ae487860675e24d9
Captured file (text)308e267e097d07a7ff597bbf92907a7e3d52ee2b5fa1a46b479b932627539caa
Output file (JSON)081d9cb3fd524fca5df06c0ab6de559b5d53b2b66ecee0b893424548cb276e42
Proof 1 · Screenshotd0af7ae182260a8552c95539c6e4c09d732ee7ddd7a46d91e6a28e599b95acf1