AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
superseded result

This is the result as it was published on 17 November 2026. A newer result replaced it on 18 November 2026; this page is kept so that anything that cited it still resolves. Read the current result →

Graded 9 November 2026

Does Nutrient.io preserve styled headings and their nesting in Markdown?

Nutrient.io’s default Build API converted styled headings into Markdown headings without preserving their hierarchy. Subsections appeared at the same level as their parent sections, and two full-size sections were demoted.

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.

Styled headings — hierarchy preservedFailEvidence
What we sent
InputDocument (PDF)
Input PDF: laboratory sample-reception procedure with styled sections and smaller subsections
Open the PDF ↗
What the tool returned

Copied from Output file (Markdown), lines 34–42

Markdown
# Condition on arrival


Reception staff record the condition of each container on the submission form before it leaves the reception
bench. Anything recorded there that falls outside the limits below goes to the duty chemist before the sample is
booked in.


# Temperature

Copied from Output file (Markdown), lines 58–68

Markdown
# Storage


# Refrigerated storage


Samples for chemical analysis are held at 4 degrees in the reception cold room and are racked by the day of
receipt, not by client. Racks are cleared every Friday afternoon.


# Frozen storage

Copied from Output file (Markdown), line 86

Markdown
## Records

Copied from Captured file (JSON), response

JSON
{
  "status_code": 200,
  "headers": {
    "date": "Wed, 09 Sep 2026 08:51:57 GMT",
    "content-type": "text/markdown",
    "content-length": "7693",
    "content-disposition": "attachment; filename=\"result.md\"",
    "server": "Cowboy",
    "x-pspdfkit-remaining-credits": "47",
    "x-pspdfkit-request-cost": "1",
    "x-request-id": "GNObA4Z5kpAMVskAAKCy"
  },
  "content_type": "text/markdown",
  "body_bytes": 7693,
  "delivery": "raw markdown body (content-type text/markdown)",
  "markdown_chars": 7691,
  "zip_members": null,
  "asset_names": null
}

Returned Markdown: flattened heading hierarchy and two demoted sections

Open the Markdown file ↗

API exchange: conversion request, successful response and credit usage

Open the whole JSON file ↗
Expected vs. Found
✗Expected: Styled headings and subheadings must become Markdown headings with their original hierarchy preserved, rather than plain or bold text.Found: The source’s three tiers lost their nesting: of 26 Markdown headings, 24 were level 1, two level 2, none level 3.
Supporting proof
Proof 1Screenshot
Run summary card: complete PDF input and default conversion settings
Open original ↗
Cited values1 value from this file
request
{ "method": "POST", "url": "https://api.nutrient.io/build", "multipart_fields": ["instructions", "file"], "instructions": { "parts": [ { "file": "file" } ], "output": { "type": "markdown" } }, "input_file": "procedure_KAL-SP-06_sample_reception.pdf", "input_bytes": 43662 }
Why this result

The default Build API completed a supported conversion, but real Markdown headings alone did not satisfy the required nesting. Nutrient.io documents a separate PDF-to-Markdown API for preserving headings; a separate test of that API merged a section with its subsection.

Also observed in this test case

Body text retained. The body prose beneath every heading in the input PDF is present in the returned Markdown.

Credit usage. The PDF conversion used one credit, leaving 47 credits on the account.

Tested by Chandresh Bisht · evidence dated 9 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
Nutrient.io
Build or version
Not exposed by the hosted product
Plan or tier
free tier
Surface
API
Set up before the run
The laboratory sample-reception procedure PDF, with styled headings and subheadings over body text, had to be converted in full to Markdown using the default pipeline, one pass and no tool-specific tuning.
Pipeline
Markdown output · no extra processing steps
Tested
9 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
18 November 2026Updated — retested
The result is unchanged: 0 pass · 1 fail. The earlier result stays readable. Read the earlier result →

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/nutrient-io/a-document-with-styled-headings-and-subheadings · 0 pass · 1 fail · coverage 1/1 · graded 2026-11-09

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 · 43 KB
Output file (Markdown) ↗text/markdown · 8 KB
Captured file (JSON) ↗application/json · 1 KB
Proof 1 · Screenshot ↗image/png · 86 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)1d53151023b44fca82503e6e748e2a1bed0b2374f54d2dc2d10279009401f34d
Output file (Markdown)2f96d116e40aafbbbf2ff1e958d3b121d61c10916b93b8ac4e3e96bbb34fc06e
Captured file (JSON)829b409f82fc0cb9f9426e1b20d4807bfd546e8aea82dafbcec36077866f1758
Proof 1 · Screenshotfa21f70d9a41b777c72b689301b1c7d53175989d3da460fe161f672a8d5335ac