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

Returned Markdown: flattened heading hierarchy and two demoted sections

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

Markdownthe whole file · cited lines 34–42, 58–68 and 86 marked


Kirkhollow Analytical Laboratories Ltd


Sample Reception and Handling
Procedure KAL-SP-06 · Revision 4 · Effective 1 March 2026


# Scope


This procedure covers the receipt, identification, storage and disposal of samples submitted to the laboratory for
chemical analysis. It applies to everything received at the Braithe Road reception, including samples delivered
by courier and samples brought in by clients. It does not cover samples taken by our own field staff, which are
dealt with in KAL-SP-11.


# Reception


Samples are received at reception between 08:00 and 17:30 on weekdays and between 09:00 and 12:00 on
Saturdays. Outside those hours clients who hold a key may use the refrigerated drop box at the rear entrance.


# Chain of custody


Every delivery arrives with a completed submission form. Reception staff check that the form is signed, that the
number of containers matches the number listed on it, and that each container carries a legible client reference.
The form is signed and timed on receipt and the top copy is returned to the person making the delivery.


# 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


Chilled samples. Where the submission form specifies chilled transport, the temperature of the transport box is
measured and written on the form. A box above 8 degrees is accepted, marked, and referred to the duty chemist,
who decides whether the analysis can still be reported. A box above 15 degrees is not accepted for
microbiological work at all.


# Container integrity


Containers that are cracked, leaking, or filled above the shoulder are photographed on the reception bench and
set aside, and the client is telephoned the same day. A leaking container is not opened at reception.


# 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


Samples that require frozen storage are held at minus 20 degrees in the chest freezer in room 4. Nothing goes
into the freezer without a completed freezer label, and nothing is stacked above the load line marked inside the
cabinet.


# Retention and disposal


Analysed samples are kept for twenty-eight days after the report is issued and are then disposed of by the route
set out in KAL-SP-19. Samples held longer at a client's request are labelled with the agreed retention date and
reviewed monthly by the laboratory manager.




## Records


Submission forms, condition records and the reception log are kept for six years. The reception log is a bound
book: entries are not erased, and a correction is made by a single line through the original, initialled and dated.


# Responsibilities


The laboratory manager owns this procedure. Reception staff carry it out; the duty chemist decides anything it
refers to them; and the quality manager audits it twice a year against the reception log and the submission forms.


# Reception staff


Reception staff check every delivery against its form, record the condition of each container, book the
submission in, and put the samples into the right storage within thirty minutes of accepting them. They do not
decide whether a sample outside the limits above can be analysed, and they are not asked to.


# The duty chemist


The duty chemist is named on the board in reception for each working day. They decide whether a sample that
arrived outside the limits can be reported and on what terms, record the decision on the submission form and
initial it, and tell the client where the decision changes what the report will say.


# Identification and booking in


# The laboratory number


Numbers run in one sequence for the whole laboratory and are never reused, including where a submission is
rejected after being numbered. The number and the year are written on the container as well as on the form,
because a container that has lost its label is a container nobody can report.


# Splitting a submission


Where determinations on one sample must be done in different sections, the sample is split at reception and each
part carries the laboratory number with a suffix. The split is recorded on the form with the volume in each part.


# Sub-samples for microbiology


A sub-sample for microbiological work is taken first, before any other part is poured, and is taken in the
reception cabinet rather than on the open bench. Where the volume received is too small to allow that, the
microbiological determinations are refused rather than taken second.


# Storage capacity


The reception cold room holds forty racks and the freezer sixty labelled boxes. Where either is full, reception
tells the duty chemist before accepting anything further into it. A sample put into the wrong storage is worse
than a sample refused: the refusal is visible and the wrong storage is not.


# Weekly clearance


Racks are cleared every Friday afternoon against the booking-in record. A sample still in the cold room after its
retention date is disposed of by the route in KAL-SP-19 and the disposal is logged. A sample in the cold room
with no record at all is not disposed of: it goes to the duty chemist, because an unrecorded sample is a failure
somewhere earlier in this procedure.


# Transport boxes and returns


Transport boxes belonging to the laboratory are emptied, wiped and returned on the next round to the client they
came from. Boxes belonging to a client are emptied and returned unwashed unless the client asks otherwise. Ice
packs are refrozen and reused; a leaking ice pack is thrown away rather than refrozen.




## Out-of-hours deliveries


The refrigerated drop box is checked at 08:00 every weekday and at 09:00 on Saturdays. Anything in it is
booked in as arriving at the time of the check and not at the time it was left, and clients are told that is the
practice when a key is issued. The box is not checked on Sundays or public holidays, and clients are asked not to
use it on the day before one.


# Deviations


A deviation from this procedure is recorded on the submission form and in the reception log, with the reason
and the name of whoever authorised it. Deviations are reviewed monthly by the laboratory manager and again at
each audit. A deviation that has happened three times is a sign that the procedure is wrong rather than the staff,
and is raised as such.


# Complaints


A client complaint about the condition or the handling of a sample goes to the laboratory manager on the day it
is received and is acknowledged within one working day. The reception log, the submission form and the
condition record are copied into the complaint file before anything else is done, because they are the only
evidence of what arrived.


# Training


Nobody works reception unsupervised until they have been through this procedure with the laboratory manager,
worked two full days alongside someone who has, and had their first ten submissions checked. Training is
recorded on the individual's file, and the record says who signed each stage off.


# Revision history


Revision 4 adds the drop box and the fifteen-degree limit for microbiological work, and moves the retention
period from twenty-one days to twenty-eight. Revision 3 followed the 2024 audit and rewrote the condition
records. Revisions 1 and 2 are held in the controlled document file and are not in circulation.

Open the Markdown file ↗

API exchange: conversion request, successful response and credit usage

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
}
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